New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 736430 link

Starred by 7 users
Status: WontFix
Owner:
tkent@chromium.org
Closed: Jun 2017
Cc:
tkent@chromium.org
pnangunoori@chromium.org
█ manoranj...@chromium.org
█ shanmuga.m@chromium.org
dtapu...@chromium.org
█ susanjuniab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

getElementsByTagName(localName) doesn't match to prefixed elements

Reported by ashwinmada@gmail.com, Jun 23 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36

Steps to reproduce the problem:
1. Open the attached file
2. Click on the button
3. Check the Console

What is the expected behavior?
getElementsByTagName should return the list of elements by tag name.

What went wrong?
On Chrome 59.0.3071.109, it returns the list of elements.
But on Chrome 60.0.3112.32, returns an empty array.

Did this work before? Yes 59.0.3071.109

Chrome version: 60.0.3112.32  Channel: stable
OS Version: 10.0
Flash Version:
dombug.html
8.6 KB View Download

Comment 1 by woxxom@gmail.com, Jun 23 2017 

See  issue 645165 , this is an intended change to comply with the new spec. In your case the correct tag name is "wsdl:operation", not "operation".

Comment 2 by tkent@chromium.org, Jun 26 2017

Components: -Blink Blink>DOM
Owner: tkent@chromium.org
Status: WontFix (was: Unconfirmed)
woxxom is right.  It's an intentional behavior change, and Firefox and Safari have the same behavior.

Comment 3 by phistuck@chromium.org, Aug 8 2017 

 Issue 753370  has been merged into this issue.

Comment 5 by tkent@chromium.org, Aug 9 2017

Cc: shanmuga.m@chromium.org dtapu...@chromium.org
 Issue 752150  has been merged into this issue.

Comment 6 by tkent@chromium.org, Aug 9 2017

Summary: getElementsByTagName(localName) doesn't match to prefixed elements (was: getElementsByTagName doesn't work on XML documents with namespace)

Comment 7 by manoranj...@chromium.org, Aug 10 2017

Cc: pnangunoori@chromium.org manoranj...@chromium.org susanjuniab@chromium.org
 Issue 751681  has been merged into this issue.

Comment 8 by tkent@chromium.org, Sep 19 2017

Cc: tkent@chromium.org
 Issue 760365  has been merged into this issue.
►

Sign in to add a comment