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

Update guidance on relevant vs. current settings objects #1653

Closed
domenic opened this issue Aug 11, 2016 · 0 comments
Closed

Update guidance on relevant vs. current settings objects #1653

domenic opened this issue Aug 11, 2016 · 0 comments

Comments

@domenic
Copy link
Member

domenic commented Aug 11, 2016

Per previous discussions with @bzbarsky, he believes that the relevant settings object of this is more generally what should be used as the default, instead of the current settings object. This mismatches ECMAScript (which is why I originally preferred current settings object as the default), but in w3c/css-houdini-drafts#251 (comment) onward I remember him convincing me that relevant was a better default for some reason, and that's what we've been moving toward in specs since then. Also, there's the precedent set by whatwg/webidl#135, which is pretty prevalent.

We should also note how in constructors you should use current, since there is no object to get the relevant settings object of.

@domenic domenic self-assigned this Aug 11, 2016
domenic added a commit that referenced this issue Aug 24, 2016
Fixes #1653, and also clarifies and tidies up some stuff while in the area.
annevk pushed a commit that referenced this issue Aug 25, 2016
Fixes #1653, and also clarifies and tidies up some stuff while in the area.
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
Fixes whatwg#1653, and also clarifies and tidies up some stuff while in the area.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant