-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Selenium's "getText" atom returns wrong capitalized text when underscores are used since PR 8736 #13779
Comments
@whimboo, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@whimboo would you like to send a PR? I can review it and merge it. |
Sadly I don't have the time at the moment. If someone else can provide a patch and test it would be great. |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
What happened?
For any HTML element that uses a text-transform of
capitalize
thegetText
atom fails to return the correct text if underscores are used. Instead ofTest_text
it returnsTest_Text
.How can we reproduce the issue?
You can take the following example:
Here the atom returns
Test_Text
instead ofTest_text
.Applying the following change makes it work:
That means that the change from PR #8736 triggered this regression.
@k7z45 could you please take a look?
Relevant log output
Here an excerpt from the log when using this atom in Firefox:
Operating System
All
Selenium version
All
What are the browser(s) and version(s) where you see this issue?
All
What are the browser driver(s) and version(s) where you see this issue?
All
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: