w3c / w3c/csswg-drafts

[cssom-1] Indicating when a style sheet is script-blocking is duplicated several times

Open
#3,103 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cssom-1
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

In the HTML Standard's Interactions of styling and scripting section we have the definition of the "style sheet ready" flag for CSS style sheets. We also have a list of conditions which, if met, make a style sheet a script-blocking one. Not too long ago this section was reformatted, and another condition has been added.

The "style sheet ready" flag is seemingly never used or set, and we're going to change (and maybe rename?) this to be a flag that makes a style sheet that was previously script-blocking, no longer script-blocking. When searching around for usages of the flag, I noticed that some text at the bottom of both the xml-stylesheet process instruction and Link header requirements sections mention the conditions that make a style sheet a script-blocking one. This seems like normative information that is duplicated from the HTML Standard, and can easily get out of sync (like with the adding of more conditions as we've seen).

Would the editors accept a PR from me that replaces these paragraphs with something like a "Note" linking to the appropriate section in the HTML Standard so this logic might stay in one place?

/cc @emilio @annevk

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CSSOM sections on the xml-stylesheet processing instruction and Link header requirements, then compare their script-blocking conditions with the HTML Standard's Interactions of styling and scripting section. Replace the duplicated normative paragraphs with a note linking to the HTML definition, so the conditions are maintained in one place.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.