- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Apr 2022 04:07:17 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-ui-4] appearance-disabling property origins == This is an issue against a detail of the text in https://github.com/w3c/csswg-drafts/pull/6537 > Let |authorProps| be a [=map=] of all properties that have a <a>cascaded value</a> for |element|, where the [=Author Origin=], [=Animation Origin=] and [=Transition Origin=] [=Cascade Origins=] are included and the [=User Origin=] and [=UA Origin=] [=cascade origins=] are ignored, where the key is the property name and the value is that <a>cascaded value</a>. I don't think it makes sense to include the Transition Origin here. A declaration can only exist in the Transition Origin if there is a related declaration in another origin, as it represents the transition between two declarations outside the Transition Origin. So first, I assert that the Transition Origin doesn't need to be inspected. And second, suppose we were to adopt this spec text and the UA defined a rule like input:focus:hover { border-color: orange; } and gave it a 1s transition. Then for the 1s transition, we'd need to treat the element as having `appearance: none`... which would be absurd. I think it should be sufficient to inspect the [=Author Origin=] and [=Animation Origin=] only. And maybe only the [=Author Origin=], as I doubt there's content out there relying on animation rules disabling native `appearance`. CC @zcorpan @emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7215 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 April 2022 04:07:18 UTC