Skip to content

Do not set data-dfn-for on top level IDL objects#3768

Merged
marcoscaceres merged 3 commits intospeced:developfrom
dontcallmedom:no-dfnFor-for-top-level-idl-objects
Sep 7, 2021
Merged

Do not set data-dfn-for on top level IDL objects#3768
marcoscaceres merged 3 commits intospeced:developfrom
dontcallmedom:no-dfnFor-for-top-level-idl-objects

Conversation

@dontcallmedom
Copy link
Copy Markdown
Member

@dontcallmedom dontcallmedom commented Sep 6, 2021

No description provided.

@marcoscaceres
Copy link
Copy Markdown
Contributor

@dontcallmedom, not sure how much you want to spend on this... I can try to fix it later this week.

Few notes/todo:

  • We have defined topLevelEntities in some other module, which should relocate to + export from the WebIDL module.
  • We should add a some tests.

@dontcallmedom
Copy link
Copy Markdown
Member Author

I'm supportive of DRYing and testing the code, but at the moment, this bug means quite a few IDL names from the permission API creates linking errors, so I would prefer if we could hot fix this and worry about the rest separately.

@marcoscaceres
Copy link
Copy Markdown
Contributor

Ok, no problem. @dontcallmedom, can you:

npm run lint -- --fix

@dontcallmedom
Copy link
Copy Markdown
Member Author

linted

@marcoscaceres
Copy link
Copy Markdown
Contributor

I'll update merge it once it's green, but will leave the bug open so I remember to add the tests, etc.

@marcoscaceres marcoscaceres self-requested a review September 7, 2021 06:33
@marcoscaceres marcoscaceres merged commit 9ec717a into speced:develop Sep 7, 2021
@marcoscaceres
Copy link
Copy Markdown
Contributor

Released respec@26.13.4

marcoscaceres added a commit that referenced this pull request Apr 13, 2026
Regression test for #3764 / PR #3768. Dictionaries and enums defined
inside a section with data-dfn-for should not inherit that attribute.
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.

2 participants