Labels and form elements are defined in HTML, so that's the natural place to define what makes an element match a given selector. CSS Selectors ( https://drafts.csswg.org/selectors-4/#input-pseudos) specifically states that the details of which elements match which state are host-language dependent. To continue the discussion with implementers responsible for the HTML specs, I started (at Anne van Kesteren's suggestion) a Github Issue for WHATWG. Comments appreciated: https://github.com/whatwg/html/issues/1632 In particular, feedback is needed from developers working on the CSS side of browser implementations, regarding the potential performance issues raised previously by Boris Zbarsky ( https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Nov/0076.html ). ~ABR On 6 August 2016 at 11:01, Brad Kemper <brad.kemper@gmail.com> wrote: > > > > On Aug 5, 2016, at 2:15 AM, Florian Rivoal <florian@rivoal.net> wrote: > > > > But the definition of this is in HTML, not CSS, and IIRC I failed to > convince the whatwg. > > Why can't we just create our own independent definition in CSS for the > :checked behavior, and then let WHAT change their definition to match the > new reality once browsers implement it our way? >Received on Saturday, 6 August 2016 22:35:27 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:04 UTC