- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Jul 2014 20:48:01 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26278
Bug ID: 26278
Summary: getElementText - no info about U+200E, U+200F
Product: Browser Test/Tools WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebDriver
Assignee: public-browser-tools-testing@w3.org
Reporter: botalov.andrey@gmail.com
QA Contact: public-browser-tools-testing@w3.org
CC: mike@w3.org
Blocks: 20860
Atoms contain some treatment for those characters -
https://github.com/SeleniumHQ/selenium/blob/master/javascript/atoms/dom.js#L1208
This change seems to be done in August, 2013 after the algorithm for Webdriver
W3C spec was written. So I think README.md of Webdriver project should have a
not that when someone makes changes to API of remote end he should also file a
bug against Webdriver spec (or even file a bug against Webdriver spec prior to
making a change) so Webdriver spec and Selenium won't become out-of-sync.
P.S.: Also I haven't noticed in lines near L1208 code that removes \f, \v
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 7 July 2014 20:48:03 UTC