You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Text (key text) is currently extracted via nodeValue (see getText), i.e., the node's actual text value. The problem is that the text might be displayed differently, for example, if a certain text-transform is applied. So when a node's text is "foo", this could be displayed as "Foo", "FOO", …
Let rendered text be the result of performing implementation-specific steps whose result is exactly the same as the result of a Call(bot.dom.getVisibleText, null, element).
We might want to consider to do this is as well, but:
Is dom.js available in the browser? If yes, in any browser? If no, do we have to bundle the script since we don't want to reimplement the functionality?
What do we do with redundant information such as text-transform, which is then reflected in the rendered text?
How can this be properly tested?
The text was updated successfully, but these errors were encountered:
Text (key
text
) is currently extracted vianodeValue
(seegetText
), i.e., the node's actual text value. The problem is that the text might be displayed differently, for example, if a certaintext-transform
is applied. So when a node's text is "foo", this could be displayed as "Foo", "FOO", …The WebDriver link text locator retrieves the rendered text via the Get Element Text command:
We might want to consider to do this is as well, but:
dom.js
available in the browser? If yes, in any browser? If no, do we have to bundle the script since we don't want to reimplement the functionality?text-transform
, which is then reflected in the rendered text?The text was updated successfully, but these errors were encountered: