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

[EXT_texture_compression_rgtc] Align with Web IDL specification #3172

Closed

Conversation

autokagami
Copy link

@autokagami autokagami commented Oct 18, 2020

🤖 This is an automated pull request to align the spec with the latest Web IDL specification. 🤖

The followings are the Web IDL validation messages, which may help understanding this PR:

  • Validation error at line 2 in EXT_texture_compression_rgtc,0, inside `interface EXT_texture_compression_rgtc -> extended-attribute NoInterfaceObject`:
    [NoInterfaceObject]
     ^
    

    Error: [NoInterfaceObject] extended attribute is a legacy feature that is now renamed to [LegacyNoInterfaceObject]. Refer to the relevant upstream PR for more information.

  • Validation error at line 3 in EXT_texture_compression_rgtc,0, inside `interface EXT_texture_compression_rgtc`:
    interface EXT_texture_compression_rgtc {
              ^
    

    Error: Interfaces must have [Exposed] extended attribute. To fix, add, for example, [Exposed=Window]. Please also consider carefully if your interface should also be exposed in a Worker scope. Refer to the WebIDL spec section on Exposed for more information.

Currently this autofix might introduce awkward code formatting, and feel free to manually fix it whenever it happens.

Please file an issue at https://github.com/saschanaz/webidl-updater/issues/new if you think this is invalid or should be enhanced.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@kenrussell
Copy link
Member

Looks like this one might still need to be handled @jdashg .

@kenrussell
Copy link
Member

Handled in #3279 .

@kenrussell kenrussell closed this Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants