-
Notifications
You must be signed in to change notification settings - Fork 161
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
Definition of {} is slightly ambiguous #1344
Comments
I think “as if from ES null” covers it unambiguously and that the “or an object” part would be more misleading than helpful even if “corrected.” There’s a lot more than just |
The intent of that section, if I recall, was that the Note that "object with no properties" is mean to indicate an object with no properties, not an object which inherits its properties from Some more background can be found by digging through #750 and the linked threads. That said, it seems like there is some gap in the normative requirements here, which fails to translate the default values |
We have "If the argument at index i is declared with a default value, then append to values that default value." in https://webidl.spec.whatwg.org/#dfn-overload-resolution-algorithm. When the default value is
{}
, the only meaning I can find is in https://webidl.spec.whatwg.org/#dfn-optional-argument-default-valueConversion from ES
null
is fully defined by https://webidl.spec.whatwg.org/#es-to-dictionary, but an "object with no properties"--if that means what you get by typing{}
in ECMAScript--can be modified by changingObject.prototype
. We should ensure this is specified so thatObject.prototype
doesn't affect it. A simple way to do that might be to remove "or an object with no properties" from the parenthetical, but it might be better to actually spell it out.The text was updated successfully, but these errors were encountered: