for..in no longer working for "HTMLFormControlsCollection" in chrome v63
Reported by
anov.sir...@gmail.com,
Dec 27 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: - open chrome devtools - open tab "elements" - click "form" element - open tab "console" - write "for(var n in $0.elements) console.log(n);" it only yield control [0,1,2...index], "namedItem", "length" and "item". What is the expected behavior? it should also yield control attribute element.NAME(s) and element.ID(s) What went wrong? element.NAME(s) and element.ID(s) is missing. Did this work before? Yes x < 63, i guess Chrome version: 63.0.3239.108 Channel: stable OS Version: 16.04 Flash Version: Shockwave Flash 28.0 r0 (sory for my english)
,
Dec 27 2017
,
Dec 27 2017
,
Dec 28 2017
Checked the issue on reported chrome version 63.0.3239.108, and on the latest dev 65.0.3305.0 using Ubuntu 14.04 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://jsfiddle.net/anovsiradj/vfa2nen2/ 3. Opened Chrome dev tools. 4. Opened tab "elements" 5. Clicked "form" element 6. Opened "Console" tab 7. Given "for(var n in $0.elements) console.log(n);" We got the result: 0 1 2 3 . .... 41 namedItem length item @Reporter: As you mentioned the earlier version was working fine, so we have checked it on chrome version #62.0.3202.38 by following the above mentioned steps. Attaching the screen cast of the same. Could you please clarify us on it, whether the screen cast has a good behavior, which helps us to triage the issue further in a better way. Any further inputs do help us. Thanks!
,
Dec 28 2017
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 28 2017
Yes! Confirmed, from your video, chrome v62 is working
and chrome v63 is not working.
v62 result: [0...41, {non..indexes..keys}, namedItem, length, item]
v63 result: [0...41, namedItem, length, item]
(@vamshi, see your video at minutes 0:30++, then compare with this video)
,
Dec 29 2017
Able to reproduce this issue on reported version 63.0.3239.108 and latest canary 65.0.3305.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1 with the confirmation given by reporter from comment#8. Good Build: 63.0.3219.0 Bad Build: 63.0.3220.0 You are probably looking for a change made after 502732 (known good), but no later than 502733 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/9e319197e596a8b57465591c2ded1afac2ab484d..231585efb676b7d99748e29f9049b29bf1f84f67 Reviewed-on: https://chromium-review.googlesource.com/654837 Suspecting same from changelog. @raphael.kubo.da.costa: Please confirm the issue and help in re-assigning if it is not related to your change. Adding RB-Stable as this is broken in M63. Please remove if not the case. Thanks!
,
Dec 29 2017
You've pinpointed the right commit, but everything's working as intended: as the commit message says, we're now following the specs correctly just like Firefox and Safari by applying the [LegacyUnenumerableNamedProperties] attribute to HTMLCollection and HTMLAllCollection. See also: issue 703990 and issue 719703 .
,
Dec 29 2017
There's also a chromestatus.com entry for this: https://www.chromestatus.com/feature/4759960915279872
,
Dec 29 2017
okay. thanks for your info. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by anov.sir...@gmail.com
, Dec 27 2017