HTML: nested browsing contexts name attribute #15392
Conversation
wpt-pr-bot
requested review from
domenic,
foolip,
jdm,
jgraham,
zcorpan and
zqzhang
annevk
force-pushed
the
annevk/nbc-name
branch
from
6ebb6de
to
23e63bd
Compare
Name attributes of elements that cna create nested browsing contexts are only to be considered when the nested browsing context is created. Tests: web-platform-tests/wpt#15392.
|
It might be somewhat nice to extend this with cross-origin support. That'd require the frame to post the name to the parent and a state switcher in the listener that then does the various aspects of the test as you cannot get |
|
Still working through my queue of (really cool) PRs from you this morning, but I'll chime in quickly to say that I'm afraid cross-origin vs. same-origin goes through rather different code paths, at least in Chrome with site-isolation. So, it would be good to add. I certainly wouldn't require you to add that before merging any spec or test PRs. But, if you don't want to do the extra work yourself, it'd be good to file a follow-up issue when we do merge. |
|
That's a good point, let me try to revive what I had earlier and make it work, but might have to wait for tomorrow if I'm not done quickly. |
| @@ -0,0 +1,6 @@ | |||
| <script> | |||
| const ident = new URL(location).searchParams.get("ident"), | |||
| post = () => parent.postMessage({ name, ident }, "*"); | |||
There was a problem hiding this comment.
It's a little unclear that this is equivalent to name: window.name so I'd suggest changing it to make it explicit.
Name attributes of elements that can create nested browsing contexts (embed, frame, iframe, object) are only to be considered when the nested browsing context is created. Tests: web-platform-tests/wpt#15392.
No description provided.