W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2020

Re: [csswg-drafts] [css-values] attr()'s url type seems wrong (#5079)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Jun 2020 16:27:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-648926142-1593016068-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-values] attr()'s url type seems wrong`, and agreed to the following:

* `RESOLVED: Specify we use host document behavior for URL types in attr()`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-values] attr()'s url type seems wrong<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5079<br>
&lt;dael> TabAtkins: Ana reviewed changes to attr and noticed I have it defined as attr with URL type it takes string and spans into URL function using css resolution rules for relative urls<br>
&lt;dael> TabAtkins: Unfortunate because if have a href and pull it out it resolves different from if click a and if you pull it into css.<br>
&lt;dbaron> s/Ana/Anne/<br>
&lt;dael> TabAtkins: They're not concordant resolution mech<br>
&lt;dael> TabAtkins: Suggestion is when using url-type we should use same reoslution rules as HTML uses.<br>
&lt;dael> TabAtkins: Reasonable to me. Exact working needs to be worked out with Anne.<br>
&lt;dael> TabAtkins: As long as no one objects to that I'm happy to have it work<br>
&lt;dael> fantasai: Update L3 as well?<br>
&lt;dael> TabAtkins: Only to whatever version the new advanced attr function is in<br>
&lt;dael> fantasai: Right, yeah<br>
&lt;dael> fantasai: Also values 4 hasn't been published in long time<br>
&lt;dael> TabAtkins: Sure. Separate issue.<br>
&lt;dael> astearns: Other comments?<br>
&lt;fantasai> +1 to the change<br>
&lt;faceless2_> +1 from me, it's a good idea.<br>
&lt;bkardell_> +1<br>
&lt;dael> astearns: Prop: When attr function is using URL type use same resolution rules as HTML<br>
&lt;dael> fantasai: I think take resolution rules for the element from which took attr<br>
&lt;dael> TabAtkins: Yes, but only one language that deinfes which is HTML<br>
&lt;dael> fantasai: [missed]<br>
&lt;dael> TabAtkins: Yeah, generic HTML doc doesn't define either<br>
&lt;fantasai> s/[missed]/If you apply CSS to a generic XML document, then HTML doesn't define that/<br>
&lt;dael> s/HTML/XML<br>
&lt;dael> fantasai: You shoudl write spec so it works for whatever languages<br>
&lt;dael> TabAtkins: As long as not a huge pain of cross doc references sure. If it is a pain I'll write it how it's readable. We'll figure out details. Want to make sure general plan is right<br>
&lt;dael> astearns: Objections to specify we use host document behavior for URL types in attr()<br>
&lt;dael> RESOLVED: Specify we use host document behavior for URL types in attr()<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5079#issuecomment-648926142 using your GitHub account
Received on Wednesday, 24 June 2020 16:27:51 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:28 UTC