New issue
Advanced search Search tips

Issue 632243 link

Starred by 2 users

Issue metadata

Status: ExternalDependency
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue 538562



Sign in to add a comment

Content Window name not changed to new name value

Project Member Reported by shanmug...@samsung.com, Jul 28 2016

Issue description

URL:
LayoutTests\imported\wpt\html\semantics\embedded-content\the-object-element\object-attributes.html

obj1.setAttribute("name", "o1");
assert_equals(obj1.name, "o1", "The name of the object element should be 'o1'.");


https://html.spec.whatwg.org/#the-object-element:attr-object-name-3 says
"Whenever the name attribute is set, if the object element has a nested browsing
context, its name must be changed to the new value. If the attribute is removed,
if the object element has a browsing context, the browsing context name must be
set to the empty string."
 
Cc: alex...@chromium.org
Components: Blink>HTML>Object
That's odd, it seems like the same requirement doesn't exist for an iframe element. Given that it's apparently web compatible to not do this, simply dropping it from the spec seems reasonable.

Shanmuga, did you test what others browsers do?
Cc: -alex...@chromium.org
Here's an ad-hoc test:
https://software.hixie.ch/utilities/js/live-dom-viewer/saved/4353

It looks like Firefox doesn't propagate the new name (bar), and Edge doesn't even propagate the original name (foo), instead just returning the empty string before and after.
Foolip, 
When I tested with Iframe element, it works well in firefox 48.0.
But not works with <object> in firefox 48.0.
https://software.hixie.ch/utilities/js/live-dom-viewer/saved/4354 is a test for the iframe case. I can confirm that Firefox propagates the new name (bar) here, but Chrome seems not to. So at the very least it's probably not needed for web compat, but it's less clear what to do with that case.
Project Member

Comment 6 by sheriffbot@chromium.org, Aug 4 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

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

Labels: -Hotlist-Recharge-Cold
Status: ExternalDependency (was: Untriaged)
> I've filed https://github.com/whatwg/html/issues/1623

It seems the specification was changed but the test wasn't changed.

Blocking: 538562

Sign in to add a comment