-
Notifications
You must be signed in to change notification settings - Fork 162
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
Is [AllowShared] an applicable-to-types attribute? #687
Comments
The link "annotated types" in OP should probably go to https://heycam.github.io/webidl/#idl-annotated-types. In any case, I think you've found an error and |
Oops. Yes. I fixed the link. If the list of applicable to types has [AllowShared], it answers my questions, |
I haven't really done a deep dive, but it seems you need this list for step 4 and 5 of https://heycam.github.io/webidl/#idl-type-extended-attribute-associated-with as well as the requirement directly after this algorithm. Do see a way to address that in some other way? |
IMO, it's enough if the section of each applicable-to-types extended attribute mentions that the attribute is applicable to types. |
Annotated types lists 3 extended attributes as applicable-to-type attributes, and [AllowShared] is not in the list. On the other hand, [AllowShared] is explained to appear on one of the buffer source type, and it means [AllowShared] is applicable to types. This adds [AllowShared] in the list of applicable to types extended attributes, so that it fixes the ambiguity. Fixes #687.
The section of annotated types has an explicit list of applicable-to-types, as
[Clamp]
,[EnforceRange]
, and[TreatNullAs]
.Beside it, in the section of
[AllowShared]
, it saysit seems to say [AllowShared] is an applicable-to-types. Is it correct? And do we need the explicit list of applicable-to-type ones?
The text was updated successfully, but these errors were encountered: