Re: [csswg-drafts] Let’s Define CSS 4 (#4770)

> developer-friendly approach than your average marketing campaign so the feedback here will certainly be useful.

Developer here:
In my case, I prefer having some means to know when mainstream versions of mainstream browsers already picked up a certain feature and that feature should be stable.
For example, in JS, there was a shadow DOM v0. I don't want advertisements to ES about shadow DOM v0's because it can be killed, just like it was. Currently, I'm making sure that shadow DOM v1 won't be killed too.
With CSS, if a CSS feature is around for people to try and understand the mistakes in the design, don't advertise it as part of a CSS version. Instead, advertise as a CSS experimental or beta or canary or alpha.
I'm in favor of unstable versioning more closely related to semversioning than how ES is doing.

This versioning method is intended to use only the major and minor numbers. I'd use the following ideology:

1. Major version number changes when something believed to be a big deal or game changer. Usually something that required major javascript hacks to work (which probably didn't always work) and/or are too complex to be implemented reliably as polyfills or shims.
2. Minor version changes when a set of welcome features are released. These are usually some new attribute values or a small set of cosmetic attributes people will feel pleased to use because, due to them, less "HTML hacking" is required to get things done.

Examples:
1. Example attributes for 1: `display: grid` `display: flex` (alongside: `grid-template-*`)
2. Example attributes for 2: `position: sticky` `scroll-snap-*` `text-underline-*` `display: flow-root`
    Or the selectors for 2: `>>` `:placeholder-shown` `:indeterminate` `:blank`

Opinions/comments?

-- 
GitHub Notification of comment by brunoais
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-595664270 using your GitHub account

Received on Friday, 6 March 2020 08:45:07 UTC