Skip to content

Conversation

SebastianZ
Copy link
Contributor

To unify the specification titles, they now all include the word "Module" and also explicitly the mention their level.
See also #12866.

I also added "Module Level 1" to CSSOM 1 and CSSOM View 1. See also #10686.

Sebastian

To unify the specification titles, they now all include the word "Module" and also explicitly the mention their level.
@frivoal
Copy link
Collaborator

frivoal commented Oct 1, 2025

I'm ok with the addition of the Level on every spec.

As for the word "Module", it works in most cases, but there are a few where I'm not sure:

  • Media Queries & Selectors: while the primary application of these specs is CSS, they are usable in other contexts as well. Is it "you can used Media Queries with CSS as well as with Window.matchMedia(), or is it "You can also use the CSS ’Media Queries’ Module with Window.matchMedia()"? Same with Selectors. I've mostly tought of it so far in the first way, though we could make it work the second way too I suppose.
  • cssom-view : I can't quite put a finger on what's wrong, but adding the word module feels strange. Then again, the name of that spec in general feels pretty strange to me, so ¯\_(ツ)_/¯

@svgeesus
Copy link
Contributor

svgeesus commented Oct 3, 2025

I agree with @frivoal that MQ and Selectors are special; they are intended to be used in multiple places of which CSS is but one, so I would avoid "Module" for those two.

@SebastianZ
Copy link
Contributor Author

SebastianZ commented Oct 4, 2025

@frivoal @svgeesus Ok, I've reverted the titles for the Selectors and Media Queries specs. Though I want to mention that if we applied that reasoning consequently, we'd have to remove "CSS" and "Module" from many other specs as well, like CSSOM, CSSOM View, CSS View Transitions 1, CSS Highlight API 1, all the Houdini specs, and more.

Sebastian

@SebastianZ
Copy link
Contributor Author

And just to be clear, you are saying that the word "Module" shouldn't be added to those specs, because they can be used outside of CSS? Though allowing the features to be used in other contexts as well or even requiring them, isn't that rather a reason to remove "CSS" from the specs? "Module" to me is only an indicator that it's part of something bigger.

Sebastian

@frivoal
Copy link
Collaborator

frivoal commented Oct 5, 2025

"The CSS XYZ Module" means it's a part of CSS. Selectors and Media Queries are not called CSS Selectors or CSS Media Queries, so you can't add module to make them part of a whole, since we haven't specified what whole.

And the lack of CSS in the name is deliberate, as they're conceptualized not as a part of CSS that can be used with other things too, but as a separate thing on top of which CSS is built. A normative dependency of CSS, not a part of it. Being maintained by the CSS WG, the distinction is somewhat blurry, but that's how I've understood it.

@SebastianZ
Copy link
Contributor Author

The counter-argument is that Media Queries 3 and Selectors 3 are part of the official definition of CSS for many years now.

Sebastian

@svgeesus
Copy link
Contributor

svgeesus commented Oct 6, 2025

Yes, CSS uses them.

Not having "CSS" in the titles was a deliberate choice some decades ago, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants