-
Notifications
You must be signed in to change notification settings - Fork 159
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
Consider renaming all legacy extended attributes #350
Comments
In general I'm very much in favor of this and I think they all make sense. I'm a little worried where we have something we recommend, EventHandler, depend on something that we don't, [TreatNonObjectAsNull], as I wouldn't want folks to start ignoring EventHandler. I think that'll probably be okay in practice though. |
|
If [Replaceable] is limited to globals it seems reasonable to keep it with the existing name. |
Hmm. In Gecko, the only non-global use of Replaceable is Of course there's no mention of it in ES either, for ES exceptions, but in practice browsers implement it (with non-identical semantics) and websites rely on it.... |
It sounds like we could limit it to globals in standards then and deal with stack once someone figures out what to do there (which likely will need to be defined in JavaScript-prose anyway given how we define DOMException today). |
Is this describing the same issue as #100? If so we should close one of them out. |
This issue seems specific to extended attributes. |
Updated the title of #100. |
I don't think we have any legitimate use cases for [Unforgeable] left. See also discussion over at w3c/webappsec-secure-contexts#46 and whatwg/html#2294. |
I think we should rename OverrideBuiltins to LegacyOverrideBuiltIns (note the uppercase I). That makes us more consistent with JavaScript and HTML, which mostly say "built-in", not "builtin". |
Part of #350. Also removes some references to usages in other specs that have since been fixed, and removes the discussion of the previous usage of this extended attribute for mixin purposes, as all those usages have migrated.
Part of #350. Also removes some references to usages in other specs that have since been fixed, and removes the discussion of the previous usage of this extended attribute for mixin purposes, as all those usages have migrated.
I'm not sure this is worth the churn, but if we wanted to, let's do it all at once.
I have attached varying degrees of ?s for the ones I am unsure on.
The text was updated successfully, but these errors were encountered: