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.

Sign up for GitHub

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

Jump to bottom

<style> entry in index of elements has not been updated to reflect removal of scoped attribute #1521

Closed
ExplodingCabbage opened this issue Jul 7, 2016 · 2 comments
Closed

<style> entry in index of elements has not been updated to reflect removal of scoped attribute #1521

ExplodingCabbage opened this issue Jul 7, 2016 · 2 comments
Labels
clarification Standard could be clearer

Comments

@ExplodingCabbage
Copy link
Contributor

The non-normative index of elements currently has flow* under "Categories" and "Parents". Unless I'm missing something, both of these have been incorrect since @domenic removed the scoped attribute in #1226. I guess that he missed this because he implemented the removal by reverting 29cf39d and related commits, but the elements index was not added until 3 years after scoped was added (778068c) and so just looking at the commits that added scoped could never reveal this bug.

The current draft of the W3C's HTML 5.2 spec is similarly affected, despite them having removed scoped independently.

In the next few minutes I'm going to push up a PR to fix this on this repo, open an issue about this on the W3C repo linking to this one, and open a duplicate PR on their repo.

Aside: the duplication of labour y'all have going on between the two specs is a tragic waste of good people's time and makes me sad.
@domenic
Copy link
Member

domenic commented Jul 7, 2016

Thank you for finding this! Much appreciated.

Aside: the duplication of labour y'all have going on between the two specs is a tragic waste of good people's time and makes me sad.

Yeah. As we say in the introduction, "Although we have asked them to stop doing so, the W3C also republishes some parts of this specification as separate documents." I agree it's very sad and a waste of a lot of peoples' time; see e.g. the comical w3c/html#364.

@domenic domenic added the clarification Standard could be clearer label Jul 7, 2016
ExplodingCabbage added a commit to ExplodingCabbage/html that referenced this issue Jul 7, 2016
@ExplodingCabbage
Remove errors about <style>'s Categories/Parents
f0e10cc 
These were true when the index of elements was introduced, but obsoleted when whatwg#1226 removed the scoped attribute.

Resolves whatwg#1521
@ExplodingCabbage ExplodingCabbage mentioned this issue Jul 7, 2016
Merged
domenic pushed a commit that referenced this issue Jul 7, 2016
@ExplodingCabbage @domenic
Fix erroroneous categories/parents for <style> in the element index
2acc100 
These were true when the index of elements was introduced, but obsoleted
when #1226 removed the scoped
attribute.

Fixes #1521.
@ExplodingCabbage ExplodingCabbage mentioned this issue Jul 7, 2016
Closed
@chaals
Copy link

chaals commented Jul 23, 2016

I'm not sure this is the right solution. See w3c/html#516 for explanation, but roughly the use of flow content in style goes back to last century and was considered a feature.

alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
@ExplodingCabbage
Fix erroroneous categories/parents for <style> in the element index
1b91103 
These were true when the index of elements was introduced, but obsoleted
when whatwg#1226 removed the scoped
attribute.

Fixes whatwg#1521.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarification Standard could be clearer
Milestone
No milestone
Development

No branches or pull requests
3 participants
@domenic @ExplodingCabbage @chaals