-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"child browsing context name property set" has some potentially-strange behavior #1337
Comments
Actually, if this behavior is intentional, then adding an example like the one in my OP would probably be the best way to go. |
Pretty sure that is intended. E.g., I tested with
in Live DOM Viewer and that yields undefined (frame.html sets window.name to "test"). |
Wow, weird! OK, then yeah, clarifying that duplicates is based on name, and adding an example like that one, would be quite helpful. |
This is a follow-up of #1312 which I just merged; I should have asked this before merging.
The ordering of step 2's "later duplicates omitted" and step 3's removal of different-origin browsing contexts seems potentially suspect. Consider the following set of child browsing contexts of the active document, where the current origin is example1.com:
With this set, the result of running the algorithm after step 2, by my reading, is:
(later duplicates being omitted. Assuming duplicates means duplicate names?)
Then, after step 3, we remove that list entry, because it is not same-origin. The result is that there are no child browsing context names. This seems unlikely to be intended.
Suggested solutions:
The text was updated successfully, but these errors were encountered: