getElementByTagName doesn't find elements with some non-ASCII characters |
||
Issue description
Chrome Version: ToT
OS: All but iOS
What steps will reproduce the problem?
(1) Run the following expressions in the DevTools console
document.body.appendChild(document.createElement("a\xC7"));
document.getElementsByTagName("A\xC7");
What is the expected result?
document.getElementsByTagName() returns a non-empty array.
What happens instead?
It returns an empty array.
Please use labels and text to provide additional information.
This is a regression by r454059.
,
Mar 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc commit 2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc Author: Kent Tamura <tkent@chromium.org> Date: Thu Mar 02 01:49:53 2017 DOM: Fix a getElementsByTagName regression by r454059. r454059 introduced an inconsistency of Document::convertLocalName() and HTMLTagCollection constructor, and it caused unexpected behavior for non-ASCII element names. These two functions should use the same lowercase function. BUG= 697658 R=yosin@chromium.org Review-Url: https://codereview.chromium.org/2722343002 . Cr-Commit-Position: refs/heads/master@{#454145} [modify] https://crrev.com/2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc/third_party/WebKit/LayoutTests/external/wpt/dom/nodes/Document-getElementsByTagName-expected.txt [modify] https://crrev.com/2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc/third_party/WebKit/LayoutTests/external/wpt/dom/nodes/Element-getElementsByTagName-expected.txt [modify] https://crrev.com/2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc/third_party/WebKit/LayoutTests/external/wpt/dom/nodes/case-expected.txt [modify] https://crrev.com/2f5e0aa4f9ab6fe3eb226bdfcb86e305f652e6bc/third_party/WebKit/Source/core/html/HTMLTagCollection.cpp
,
Mar 2 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by tkent@chromium.org
, Mar 1 2017