Re: [csswg-drafts] [css-cascade] Cascade priority of presentation hints vs. tree scopes (#6659)

The CSS Working Group just discussed `Cascade priority of presentation hints vs. tree scopes`, and agreed to the following:

* `RESOLVED: Presentation hints into their own origin between user and author in cascade`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Cascade priority of presentation hints vs. tree scopes<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6659<br>
&lt;dael> miriam: Problem noted here is that as specced presentational hints do sometimes override author styles. I think not the intent<br>
&lt;dael> miriam: Request is fix spec so presentational hints always overwritten by author styles. Likely moving up in cascade so immediatly after origins<br>
&lt;astearns> ack fantasai<br>
&lt;dael> fantasai: I would make it it's own origin. Simpliest fix<br>
&lt;dael> TabAtkins: I think so too<br>
&lt;dael> astearns: Make it its own origin and spec where it fits?<br>
&lt;dael> fantasai: Yeah. Answer to that is obvious. Don't want to change behavior<br>
&lt;dael> miriam: Between user and author?<br>
&lt;dael> fantasai: Yep<br>
&lt;dael> astearns: Concerns?<br>
&lt;dael> florian: Why is this not in UA origin?<br>
&lt;dael> TabAtkins: Presentational hints come from author doing things. Interp as author intent, jsut weaker<br>
&lt;dael> astearns: prop: Presentation hints into their own origin between user and author in cascade<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: Presentation hints into their own origin between user and author in cascade<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6659#issuecomment-937270531 using your GitHub account


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

Received on Wednesday, 6 October 2021 22:31:09 UTC