[Feature request] Implement unprefixed :read-only and :read-write pseudo-classes

[SemiKebab]

Please consider implementing the :read-only and :read-write pseudo-classes, unprefixed.

Note they are implemented in other browser for a long time: https://caniuse.com/css-read-only-write.

Actually, Pale Moon already implements the "-moz" prefixed selectors. So it's just a matter of adding support for the unprefixed selectors, also keeping the prefixed ones for now, as does Firefox.

Use case: Adding a grey background to input elements that have a readonly property:

Code: Select all

input:not([type]):read-only,
input[type="text"]:read-only,
textarea:read-only {
    background-color: #F2F2F2;
}

[SemiKebab]

As a side note, the following CSS doesn't work in Pale Moon, nor in Chrome:

Code: Select all

input[type="text"]:-moz-read-only,
input[type="text"]:read-only {
    background-color: #F2F2F2;
}

The solution is to use two rulesets:

Code: Select all

input[type="text"]:-moz-read-only {
    background-color: #F2F2F2;
}
input[type="text"]:read-only {
    background-color: #F2F2F2;
}

It's a case where the unrecognized selectors discard the entire ruleset.

For both browsers: ":read-only" unrecognized by Pale Moon and ":-moz-read-only" unrecognized by Chrome.

[SemiKebab]

By the way, I just realized that for my use case (and I suppose for most use cases), instead of bothering with ":read-only/:-moz-read-only", I just had to use "[readonly]".

Though, this feature request is still valid :)

[SemiKebab]

Again as a side note, about the "ruleset entirely discarded" issue (my 2nd post), people encountered it on MDN, here and here.

They solved the issue by enclosing the selectors in an :is() list, which does forgiving parsing. Although it works, this solution doesn't look pretty (what to blame is the legacy, prehistoric unforgiving parsing).