- From: Delan Azabani via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Dec 2021 13:41:05 +0000
- To: public-css-archive@w3.org
> @delan Wrt which origins disable UA defaults, I'm OK with @emilio's answer as well. Though including the Transitions origin seems weird to me, what if the UA rules want to transition between two styles? So reading [these few comments](https://github.com/whatwg/html/pull/4857#pullrequestreview-424168323), I think the same choice was made for ‘appearance’ because neither Gecko nor Blink are *able* to tell the difference between a UA transition and an author transition, they are both just transitions? But like ‘appearance’, making transitions suppress UA defaults here improves the experience for authors at the expense of breaking UA transitions? Not sure if I’ve understood that correctly, maybe @andruud and @emilio can correct me. > Wrt unset/revert, the logic proposed makes sense to me. […] Run a search for "Firefox userContent.css". Thanks! I’ll play around with the user origin, then see if I can make a case for one or the other. > UA cannot do these weird things when the author has specified colors. They have to use the author-specified colors with no modification. But when using UA-chosen colors, they can choose anything. That would definitely make the reftest story easier, but I don’t think we can allow Safari to paint ::selection as a translucent “wash” *and* forbid Safari from making opaque ::selection backgrounds translucent. @mrego pointed out that the Gecko example actually only happens under UA-chosen highlight colors, so no worries there. Let’s discuss Safari in #6853 to avoid making this issue even longer. -- GitHub Notification of comment by delan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6386#issuecomment-985529922 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 December 2021 13:41:07 UTC