Skip to content
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

_Which_ unit of related similar-origin browsing contexts? #88

Closed
domenic opened this issue Oct 8, 2015 · 1 comment
Closed

_Which_ unit of related similar-origin browsing contexts? #88

domenic opened this issue Oct 8, 2015 · 1 comment

Comments

@domenic
Copy link
Member

domenic commented Oct 8, 2015

Mutation observer algorithm steps say:

Let notify list be a copy of unit of related similar-origin browsing contexts' list of MutationObserver objects.

and

append it to the unit of related similar-origin browsing contexts' list of MutationObserver objects, and then return it.

This seems pretty ambiguous to me. Shouldn't be trying to go from e.g. entry settings object to browsing context to unit of related similar-origin browsing contexts, or something?

Maybe HTML needs to define "current unit of related similar-origin browsing contexts"?

@annevk
Copy link
Member

annevk commented Oct 9, 2015

Yeah, that could work. Or IDL defines it as a thing you can grab at anytime.

annevk added a commit that referenced this issue Nov 26, 2018
Using "unit of related similar-origin browsing contexts" never made much sense as a browsing context could always hold several cross-site documents.

Helps with whatwg/html#4198.

Fixes #88.
annevk added a commit that referenced this issue Jan 16, 2019
Using "unit of related similar-origin browsing contexts" never made much sense as a browsing context could always hold several cross-site documents.

This also changes the structures these agents hold from lists to (ordered) sets as that's more accurate and precise.

Helps with whatwg/html#4198.

Fixes #88.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants