"WebDriver:GetElementText" fails to correctly capitalize text containing accent characters ("ó")
Categories
(Remote Protocol :: Marionette, defect, P3)
Tracking
(firefox-esr115 unaffected, firefox-esr128 wontfix, firefox-esr140 fix-optional, firefox142 wontfix, firefox143 wontfix, firefox144 wontfix, firefox145 wontfix, firefox146 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | wontfix |
| firefox-esr140 | --- | fix-optional |
| firefox142 | --- | wontfix |
| firefox143 | --- | wontfix |
| firefox144 | --- | wontfix |
| firefox145 | --- | wontfix |
| firefox146 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [webdriver:m18], [wptsync upstream])
Attachments
(2 files)
With the changes from bug 1888004 another bug in the bot.dom.getVisibleText() Selenium atom was revealed. This time for accent characters. The issue was filed as https://github.com/SeleniumHQ/selenium/issues/14271 and now got fixed in Selenium. Here a HTML testcase that we could use in a wdspec test:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Bug Test</title>
<style>
h1 {
text-transform: capitalize;
}
</style>
</head>
<body>
<h1>Fecha de expiración</h1>
</body>
</html>
The output should be Fecha De Expiración but it ends-up with Fecha De ExpiraciÓN.
We should agree on updating the bot.dom.getVisibleText() Selenium atom in the WebDriver classic specification to https://github.com/SeleniumHQ/selenium/commit/775cfb33b193eb8832cd5488f298006f45254685 and ensure that nothing else is broken.
|
Assignee | |
Comment 1•1 month ago
|
||
The last time we updated the Selenium atoms was on May 8th, 2024 via https://github.com/w3c/webdriver/pull/1811.
Landed changes for the dom.js atom:
https://github.com/SeleniumHQ/selenium/commits/775cfb33b193eb8832cd5488f298006f45254685/javascript/atoms/dom.js?since=2024-04-10&until=2025-09-02
|
||
Updated•1 month ago
|
|
|
Assignee | |
Updated•1 month ago
|
|
|
Assignee | |
Updated•1 month ago
|
|
|
Assignee | |
Comment 2•1 month ago
|
||
I tried to build the Selenium atoms but it's currently failing due to https://github.com/SeleniumHQ/selenium/issues/16358.
|
|
Assignee | |
Comment 3•28 days ago
|
||
I was able to solve the problems with building the atoms. I'll take a look today or when I'm back.
|
|
Assignee | |
Comment 4•9 days ago
|
||
|
||
Updated•9 days ago
|
|
|
Assignee | |
Comment 5•9 days ago
|
||
|
|
Assignee | |
Comment 6•9 days ago
|
||
It looks to be all fine locally for me. No regression seen when updating the Selenium atoms. But to be sure I've triggered a try build:
https://treeherder.mozilla.org/jobs?repo=try&revision=0cd224d56e638d6fe31bbe203600880d068b2356
I'm going to file a WebDriver classic issue now to update to the 775cfb33b193eb8832cd5488f298006f45254685 revision of Selenium atoms.
|
|
Assignee | |
Comment 7•9 days ago
|
||
The WebDriver classic spec PR can be found at https://github.com/w3c/webdriver/pull/1932.
|
||
Comment 10•2 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/717ca8bc5afe
https://hg.mozilla.org/mozilla-central/rev/cf6771047c21
|
||
Comment 11•2 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
|
|
Assignee | |
Comment 12•2 days ago
|
||
We are late in the beta cycle and the merge to release will happen soon. As such I don't think that we should uplift this change but give it a full nightly cycle to bake. If it's stable we could think about an uplift to esr140 at a later point. I'll check back once 146 is on release.
Description
•