Bug 25498 – No login form at myvodafone.vodafone.in because elements in document.all cannot be accessed by name

• Component: DOM
• Status: RESOLVED CONFIGURATION CHANGED

[Michael Du]

Steps:

1. Go to URL https://myvodafone.vodafone.in/NWSS-Project-context- root/NWSS.jsp?Circle=0007

Issue:

The Login form should appear, but it doesn't appear

Other browsers:

IE 7: OK
FF 3: OK

Nightly tested: 42793

Bug in Chromium : http://code.google.com/p/chromium/issues/detail?id=10838

[Michael Du]

Created attachment 29929 [details]
reduction case

Here is a reduction case: test-quirks.html

In inside-iframe.html there is a JS sentence:
......
var frame = this.parent.document.all("Loginifrm");
......
"Loginifrm" is the name of the iframe, Chrome/Safari couldn't retrieve the
corresponding element when using name property in document.all collection.

Currently Chrome/Safari recognize elements only when using id property in
document.all collection, however IE/FF recognize elements when using either id or
name property in document.all collection.

[Blake Sening]

This is a duplicate of Bug #24105

[David Wai]

Better to keep this bug open (and make Bug #24105) the duplicate.  The bug has the reduced test case and the corresponding Chromium bug number.

[Ahmad Saleem]

This got fixed in this commit in Chromium:

https://chromium.googlesource.com/chromium/src.git/+/e2fa87bd68aea47baf3ad53b8c9a088f60a13536

Where they added <applet> and <button> tag in the HTMLCollection.cpp but in Webkit, we don't have these:

https://github.com/WebKit/WebKit/blob/8afe31a018b11741abdf9b4d5bb973d7c1d9ff05/Source/WebCore/html/CachedHTMLCollection.h#L107

but Webkit follows the list from web-spec:

https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#all-named-elements

"The following elements are "all"-named elements: a, button, embed, form, frame, frameset, iframe, img, input, map, meta, object, select, and textarea".

I tried "reductions" from zip, only in Quirks Mode, Safari Technology Preview 152 matches with Chrome Canary 107 but differs from Firefox Nightly 106 besides that there is no change in behavior.

I tried to turn Chromium patch test case to following JSFiddle:

Link - https://jsfiddle.net/7afgx1y0/

But it does not work and don't display anything.

I will leave it for others to confirm or comment whether it is something yet to be fixed or not. Thanks!

[Ryosuke Niwa]

This seems to render as intended now.