Re: [csswg-drafts] [css-values] Clarify fragment URLs resolve against the current tree, not document tree (#3320)

The CSS Working Group just discussed `[css-values] Clarify fragment URLs resolve against the current tree, not document tree`, and agreed to the following:

* `ACTION: fantasai ask ryosuke to review`
* `RESOLVED: Accept edits`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> -> https://drafts.csswg.org/css-values-4/#local-urls<br>
&lt;fantasai> TabAtkins: Awhile ago, we discussed how a fragment-only URL needs to be resolved<br>
&lt;fantasai> TabAtkins: both in general, in presence of base URL changes, or history API changing URL etc.<br>
&lt;fantasai> TabAtkins: wanted those to be stable<br>
&lt;fantasai> TabAtkins: also question of how that works in shadow DOM<br>
&lt;fantasai> TabAtkins: IDs are scoped to a particular shadow tree<br>
&lt;fantasai> TabAtkins: the resolution was that a fragment URL in a shadow tree resolves against IDs in that tree if possible<br>
&lt;fantasai> TabAtkins: if document-global, does page-local resolution<br>
&lt;fantasai> TabAtkins: not paying attention to absolutized URL still matches or not<br>
&lt;fantasai> TabAtkins: fantasai objected to the way I was writing because of future-compat with other types of fragment URLs (that are not IDs)<br>
&lt;fantasai> TabAtkins: I'm not 100% sure, because not familiar with other parts of the ecosystem<br>
&lt;fantasai> TabAtkins: but I think it gets the point across<br>
&lt;fantasai> TabAtkins: if your fragment is an ID reference, treat as ID reference relative to whatever shadow tree you're in<br>
&lt;fantasai> TabAtkins: otherwise, resolve against document e.g. as media fragment<br>
&lt;fantasai> TabAtkins: if other fragment types need to be shadow-sensitive, can adjust, but for now they're all globla<br>
&lt;fantasai> s/globla/global<br>
&lt;fantasai> TabAtkins: so requesting review from CSSWG, maybe take a resolution to accept text but can take time to review if wanted<br>
&lt;fantasai> astearns: has ryosuke reviewed?<br>
&lt;fantasai> ACTION: fantasai ask ryosuke to review<br>
&lt;fantasai> astearns: any comments?<br>
&lt;bkardell_> q+<br>
&lt;fantasai> astearns: proposed to accept edits and close the issue<br>
&lt;fantasai> bkardell_: does it take into account the base URL?<br>
&lt;fantasai> TabAtkins: no, very specifically not paying attention to URL before the fragment part<br>
&lt;fantasai> TabAtkins: if your URL is just a fragment, it's guaranteed local<br>
&lt;fantasai> TabAtkins: no matter what you do to page URL, or when you resolve URL<br>
&lt;fantasai> TabAtkins: we interpret as an ID reference<br>
&lt;fantasai> bkardell_: ok, I get it<br>
&lt;fantasai> astearns: objections?<br>
&lt;fantasai> RESOLVED: Accept edits<br>
&lt;fantasai> astearns: as people find more problems, open more issue<br>
&lt;fantasai> s<br>
</details>


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


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

Received on Wednesday, 13 December 2023 17:25:25 UTC