- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Aug 2019 16:45:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `background-color in forced color modes needs more than a simple unset`, and agreed to the following: * `RESOLVED: background-color computes to the system background-color for all values but heh alpha channel` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: background-color in forced color modes needs more than a simple unset<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4175<br> <dael> Rossen_: I'll take it since melanierichards is on vacation<br> <dael> astearns: How much time do you need?<br> <dael> Rossen_: Quick.<br> <Rossen_> https://www.w3.org/TR/css-color-adjust-1/#forced-colors-properties<br> <dael> Rossen_: When the forced color behavior was desc in the link^<br> <dael> Rossen_: These are the properties overwritten by system colors. Fallback was spec that every property that has no overrides gets the revert !important which means revert to original UA stylehseet which for bg color is transparent<br> <dael> Rossen_: Not expected. All other colors reverting makes sense. Background being reverted to ransparent you lose all non-transparent. Intended it go to system bg color<br> <dael> Rossen_: Idea from fantasai was can re do something to transparent color and see if computes to self similar to currentColor. Not really the same. Transparent color is a named color.<br> <aja> re: forced-colors, should transparent (borders-color only?) be allowed in addition to the non-deprecated system colors? will file issue if it sounds reasonable.<br> <dael> Rossen_: If we spec transparent computes to itself as computed we're making an exception for one named color. Think it's a bit wierd. crrentColor is an instruction to cascade algo to go back to a value. Not really the same<br> <dael> Rossen_: Ask here is that we take bg color out of the list and spec the behavior that it falls back to system bg color in case of forced colors<br> <dael> Rossen_: That was intended impl that we had to back out when making code according to spec<br> <dael> AmeliaBR: This would need to be defined in prose b/c incvolves a switch on computed value we can't define in cascade.<br> <dael> Rossen_: Yes<br> <dael> AmeliaBR: Would it work to force all bg to be opaque?<br> <dael> Rossen_: Inverse problem which would be jsut as bad<br> <dael> AmeliaBR: Okay.<br> <dael> AmeliaBR: It really has to be done with a little magic ans special prose<br> <dael> Rossen_: Magic is simple. When you compute value of bg color for non-transparent the value is computed to the system bg color.<br> <dael> Rossen_: To your observation AmeliaBR the explanation will be bg color only.<br> <dael> AmeliaBR: Any interaction with bg image? bg image the current proposal is keep the image and use backplate behind text to add contrast. Would you do them separately?<br> <dael> Rossen_: What you said is right for bg image. For bg color if the color is non-transparent it will be system bg color. So if you draw a backplate it would be non-observable visually or object model. Somewhat wasteful to render.<br> <dael> Rossen_: Otherwise for bg image the backplate takes effect and guar. forground in desired contrast<br> <dael> dbaron: Is this the right treatment for bg colors with alpha between transparent and opaque. alternative is don't touch alpha and change color compontents to system color<br> <dael> Rossen_: valid point. There's a different issue that addresses what you desribed when talking about interpolation. It will end up interpolating most of alpha channel. I like your proposal<br> <dael> astearns: Summary Rossen_ ?<br> <dael> Rossen_: Prop: background-color computes to the system background-color for all values but hte alpha channel<br> <dael> astearns: Can we resolve on this?<br> <dael> astearns: Objections?<br> <dael> RESOLVED: background-color computes to the system background-color for all values but heh alpha channel<br> <dael> s/heh/the<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4175#issuecomment-523545605 using your GitHub account
Received on Wednesday, 21 August 2019 16:45:48 UTC