Add media-feature-range-notation: "context" rule

[jeddy3]

What is the problem you're trying to solve?

Consistent range media features.

What solution would you like to see?

Turn the media-feature-range-notation on.

We'll want to use the context primary option as it addresses sort comings with the older prefix approach. We'll need to wait until

• it's supported in all evergreen browsers (waiting on Safari).
• we add autofix for this option to the rule

[ybiquitous]

Safari 16.4 now supports it!

In addition, the autofix is coming soon.

• Add media-feature-range-notation autofix stylelint#6742

[ybiquitous]

The next version to include this addition should be a major update.

[jdelStrother]

I was surprised this comes on by default when Safari 16.4 is only very recently available and has very low adoption so far. I'm not arguing to change the behaviour, would just love to hear more about the rationale - is the expectation that everyone should be using https://github.com/postcss/postcss-media-minmax to transpile it?

[ybiquitous]

This feature is excellent for people, and they should be so happy when all modern browsers support it. So this added rule could be a good opportunity to inform them about the feature.

If people don't need it, they can turn the rule off. Or, they can transpile CSS code with the beautiful Postcss plugin you mentioned.

[Mister-Hope]

This feature is excellent for people, and they should be so happy when all modern browsers support it. So this added rule could be a good opportunity to inform them about the feature.

If people don't need it, they can turn the rule off. Or, they can transpile CSS code with the beautiful Postcss plugin you mentioned.

Yes, I agree that you can add this in changelog with an h1, e.g.:

Welcome to turn on media-feature-range-notation

But I am surprised to see a rule like this being turned on so carelessly.

See the data from canIUse:

It has a low support rage of only <75%, and a one year old chrome even does not support it, and there are so many ios and macOS devices are not upgrading to 16.4 at all.

Also this feature is used to build reponsive layouts, which means that more than a quator people will see broken websites with this rule turn on, shall anyone feel that is affordable to any products or websites? @jdelStrother

I don't think this feature should be included at this point, as I think it's more common for any websites to provide at least one year backwords support for all browsers

Can we add some notes or commnunity standards, to unify in what case "A feature is already widely supported and can be turned on by default"? Especially the feature can not be pollyfilled by other tools at this time?