- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 00:16:54 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-values] Clarify fragment URLs resolve against the current tree, not document tree`. <details><summary>The full IRC log of that discussion</summary> <dael> TabAtkins: Last month I committed the initial spec text. fragement urls are now tree scoped references. Look up in tree style is in to find url. Lets you refer to global if nothing intervening<br> <dael> TabAtkins: A bit of changes to make. I don't strip fragment directives b/c waiting on that spec to extract that algorithm. They do that now so I'll make the change; that's minor<br> <dael> TabAtkins: Only other issue is fantasai comment on there that I'm not handling other types of fragments like media fragments in an intelligent way. Right now see if there's an element with the frag as the idea great. If not fail. Means media fragments almost always fail. Would like to specifically exclude them<br> <dael> TabAtkins: Don't think there's a conceptual definition of media fragments so right now I'm not. If someone knows a way to refer to these that is testable, great. For now no practical effects so I think spec is workable but not idea.<br> <dael> TabAtkins: If that's okay, we can accept and then tweak<br> <astearns> ack fantasai<br> <dael> fantasai: Disagree it's good now. Things like media fragments should just work. URL fragments are not about pointing at an element. They're sometimes pointing at an image. Often that.<br> <dael> fantasai: Media fragment is reasonable way to clip out section of image. I think spec text should work for these things<br> <dael> TabAtkins: If you can find a well defined way to talk about it, great<br> <dael> fantasai: Vaguely defined and correc tis better than precise and wrong. And you can file issue against url spec<br> <dael> TabAtkins: File and issue against me and I'll figure out some way to talk about that<br> <dael> astearns: Split into a separate issue or have that accurate but not precise issue before we close<br> <dael> fantasai: These changes are a regression so would like to address. It did not spec how you do it, but it wasn't wrong<br> <dael> TabAtkins: Didn't say anything about that in previous<br> <dael> fantasai: Which is better than saying something wrong<br> <dael> TabAtkins: Don't think that is a follow-up, but alright.<br> <dael> TabAtkins: Happy to figure out how to address. Would like it sep. so SVG working is in there<br> <dael> fantasai: If there's spec text that excludes ID is fine<br> <dael> TabAtkins: Can we do that as sep so we close this issue that's been open for years<br> <dael> fantasai: You don't have text that addresses this which is my problem<br> <dael> TabAtkins: Which we will fix in another issue.<br> <fantasai> Your text for this issue breaks other things.<br> <fantasai> Write text that doesn't break the other things, and then you can close this issue.<br> <dael> astearns: I don't think we are going to come to an agreement between the two of you on how we should track the remaining problems. I suggest we leave issue as is until we get something in the spec to address fantasai issue<br> <dael> astearns: And then we can close the issue. Acceptable TabAtkins?<br> <dael> TabAtkins: I can't do otherwise, so sure?<br> <dael> astearns: One remaining thing on this and we'll come back once there's a little more in the spec and then create a new issue for a better definition<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-1371571958 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 00:16:55 UTC