- From: Alison Maher via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Sep 2020 22:19:25 +0000
- To: public-css-archive@w3.org
I was chatting with Rossen around this one and wanted to add on a bit more based on the discussion. Let's say that we have the following case: ``` <div id="parent" style="background: black;"> <div id="child " style="background: black; transition: 3s;"></div> </div> ``` And let's also say that when we change the `background-color` on the parent, we also update the child's `background-color` to match, triggering a transition. Given [approach (B)](https://github.com/w3c/csswg-drafts/issues/5419#issuecomment-679002425), we can have the following cases in Forced Colors Mode: 1) If `forced-color-adjust` is `auto`, and we change the parent's `background-color` to `white`, we wouldn't trigger a transition on the child because the background remains the same color. 2) If `forced-color-adjust` is set to `none` on the parent, and we change the parent's `background-color` to `white`, we would update the child's `background-color` to `white` as a result, triggering a transition. 3) If case 1 happens again, and then we change the value of `forced-color-adjust` to `none` on the parent, should we trigger a transition on the child in this case or not? I do see the value of the current proposal given case 2. However, considering case 3, perhaps the simplest and most consistent behavior here would be to not trigger transitions at all in Forced Colors Mode. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5419#issuecomment-698001619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 September 2020 22:19:27 UTC