Problem clicking the button that needs scripting

[Russ_Thomas]

Hi @devalex88

I’m not entirely sure what you’re asking me. The script is pretty much what I used in the browser console, i.e., javascript

Get a property (href) of a dom element:

x = myelement.href;

Get an attribute (href) of a dom element

x = myelement.getAttribute("href");

Setters:

myelement.href = "something";
myelement.setAttribute("href", "something");

I don’t know that your selenium core provides for this - but I see no issue with you using JavaScript directly (i.e. via the core of executeJavaScript API).

My overriding wish is that you provide a new, newly named API set that truly reflects the published DOM API set. I laid it out for you below, with backward compatibility taken care of:

Fix Poorly Named/Broken APIs

getAttribute This API will return a property when asked to retrieve the content of the value attribute. It will do this even when the value attribute is undefined! This is wrong, because… An element property is not the same as an element attribute. Note: Perhaps it always returns properties, I did not test that. Because there is existing test code reliant on the current behavior, the documentation should make clear this API is deprecated in favor of two new APIs which do the correct thin…