W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2016

[csswg-drafts] [css-pseudo] Highlight pseudo-el cascade rules doesn't match reality

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Aug 2016 21:20:26 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-168991532-1470172824-sysbot+gh@w3.org>
tabatkins has just created a new issue for 

== [css-pseudo] Highlight pseudo-el cascade rules doesn't match 
reality ==
All browsers (now?) agree in nearly all details for how to render 
::selection (and presumably will apply the same to the other highlight
 pseudo-els). However, the spec text *drastically* conflicts with 

In particular, IE/FF/Blink all:

* have some default UA styles for the highlight
* each element's segment of the highlight is styled according to *that
 element's* ::selection rules
* if a given element doesn't style the highlight at all, it uses the 
UA rules

    (Definition of "doesn't style at all" is slightly inconsistent - 
all agree that an empty style rule for the element doesn't style it, 
and all agree that a highlight-valid property in the style rule does 
style it. IE assumes that a property that doesn't apply to the 
highlight doesn't count as styling, while FF and Blink treat it as 

There was some discussion/resolution about this in the past, of which 
the current spec text is apparently the result, but iirc browsers 
previously didn't agree as strongly so we believed there was some room
 to dictate a maximally "useful" result. However, they currently 
strongly agree (with only very minor differences) on what I described 
above. We should change the spec to match current browser behavior, 
which, while not *ideal*, is serviceable, simple, and mostly 
consistent with how other pseudo-elements work.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/374 using your GitHub 
Received on Tuesday, 2 August 2016 21:20:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:01 UTC