Fix #278 and extend with --firefoxMacONLY, --chromiumONLY, --webkitONLY

[WebMechanic]

Test page and explainer https://codepen.io/WebMechanic/pen/poVexYp?editors=1100

Sources:

• WebKit https://webkit.org/css-status/#?status=non-standard
• Lea Verou's https://css3test.com/ "Experimental" filter
• https://github.com/fingerprintjs/blog-nojs-fingerprint-demo/

container-type:none is a non-standard value to test against. It must not be changed to inherit which is usually sufficient and safe to check property support.

[argyleink]

so far my tests have gone good and the updates seem fair. it is odd seeing container-type: none in there, but the reasoning seems good.

going to test more at work. thanks for this!

[argyleink]

where did you learn that container-type:none matched?
i'm on the fence about the chromium one, you?

[WebMechanic]

where did you learn that container-type:none matched?

using Lea Verou's https://css3test.com/ ("Experimental" filter selected) in Containment Level 3 / Properties.
It was "green" in Chromium but not in Chrome.

This is Chrome 105 (and WebKit "16")

i'm on the fence about the chromium one, you?

It could be useful to tweak font stuff but that's all I can think of now :)

That's likely the test that might break[^1] sooner or later[^2]. I wouldn't mind, if you want to skip it. It was more of a challenge to find sth at all and some sort of a "first match pick" from Lea's site. There could be others 🤷‍♂️ .

To be frank: we virtually have no Chromium or Linux visitors in our analytics so we don't really test in that browser. If stuff works in Chrome it's fair to presume it works in Chromium too. Both are very much on par with their CSS for "real world work".

I wouldn't add it back in for our copy. It's now "documented" and if somebody needs different style for Chrome and Chromium, here's how they learn how :D or scan css3test.com for sth else.

Your descision after all.

[^1] I just saw that Firefox' experimental implementation parses all properties here = it's all green.
[^2] 'none' appears to be from the 20211221 draft. It has since been removed. So should Chromium update their implementation it might be gone, too.