Re: [csswg-drafts] [css-content] Implementing content:none on elements is not web-compatible (#6503)

Thanks. It sounds like Gecko/Blink/WebKit all represent 'normal' and 'none' as distinct computed values.  So in response to @frivoal 's agenda+ comment...
> Agenda+ to decide if we want to make none compute to normal on regular elements, or keep them as distinct values with identical behavior

Of these two options^, we probably want the latter option (distinct computed values), so as not to unnecessarily force all engines to change (unless there's good reason to do so).

Having said that: there's some additional magic in how the value is used/not-used in each engine, so I'm not sure what makes to spec about that.

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-1089545434 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 5 April 2022 23:58:54 UTC