On Tue, Feb 23, 2021 at 9:49 PM fantasai wrote:
> We wanted it to be flexible enough that UAs could experiment with behavior and
> improve usability over time, so we locked down the one period in time that we
> felt was not up for debate (between attempted submission and next interaction
> with
On 2/23/21 09:24, Anne van Kesteren wrote:
On Mon, Feb 22, 2021 at 2:59 PM Emilio Cobos Álvarez wrote:
Let me know if you have any objections about this change, but I think
having a prefixed pseudo-class for this is not a great state of affairs.
This seems reasonable, but I think we should
On 2/23/21 11:52, Xidorn Quan wrote:
Please head up in CSS working group about this, and probably ask for a
resolution on no objection for us to ship it, as this spec is still in draft.
Hmm, is it? https://www.w3.org/TR/selectors-4/#user-pseudos has had
:user-invalid for quite a while, and
On Tue, Feb 23, 2021, at 12:59 AM, Emilio Cobos Álvarez wrote:
> Standard: https://drafts.csswg.org/selectors/#user-pseudos
>
> Other browsers: No signal from other vendors, though we've shipped this
> functionality for quite a while and the CSS working group considers it
> useful, see
On Mon, Feb 22, 2021 at 2:59 PM Emilio Cobos Álvarez wrote:
> Let me know if you have any objections about this change, but I think
> having a prefixed pseudo-class for this is not a great state of affairs.
This seems reasonable, but I think we should define the processing
model for them in the
Hi,
In bug 1694141 I plan to unprefix :-moz-ui-valid and :-moz-ui-invalid
pseudo-classes. These are useful pseudo-classes to determine when to
show feedback to the user about a form control being invalid.
Standard: https://drafts.csswg.org/selectors/#user-pseudos
Platform coverage: all
6 matches
Mail list logo
