Re: [csswg-drafts] [css-fonts] Unknown fragment identifiers in @font-face src:

The Working Group just discussed `Unknown fragment identifiers in @font-face src:`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Unknown fragment identifiers in @font-face src:<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2566<br>
&lt;gsnedders> I think Anne added it because Domenic drafted some text in HTML to better define what blocks the load event, including CSS.<br>
&lt;gsnedders> and Domenic said "it would be great if the CSSWG was able to resolve this one way or another, write the tests, and move the definition into one of their specs"<br>
&lt;dael> TabAtkins: Some fontface formats let you do special things with fragments. There might be more in the future. Question is how should we handle font URLs in fontface with unknown types of fragment identifiers.<br>
&lt;dael> TabAtkins: Initial suggestion was ignore, but I suggested do same as image function where if you see a fragment ID and don't know how to handle treat the URL as invalid. You don't know what the fragment is trying to do.<br>
&lt;dael> TabAtkins: Suggestion: we spec that for the fontface rule if a URL has a fragment identifier you don't know how to deal with you treat it as invalid.<br>
&lt;dael> myles: Not sure I agree. It seems in some situations you want to treat fragment as unknown and some others for whole is unknwonw.<br>
&lt;myles> my client crashed<br>
&lt;dael> TabAtkins: Browser that doesn't know what an open type collection is. Your fragment says load the second. Browsere tries to download but you don't know what will happen. Best situation is it see sa url that says to do something it doesn't understand best thing to do is to say I don't know what to do, skip it.<br>
&lt;dael> TabAtkins: I don't think doing something arbitrary can be argued as better for the user.<br>
&lt;dael> fantasai: Treating uninterpretable fragment IDs as invalid seems appropriate. It's just like if you got a URL with a theme you can't load you treat as invalid.<br>
&lt;fantasai> s/theme/scheme/<br>
&lt;dael> myles: TabAtkins said browsers that don't understand collections will ignore the whole ting, but I think all 4 browsers do understand collections<br>
&lt;dael> TabAtkins: Yes, it was a hypothetical example. I was using it as a stand in for a future where the fragment does something significant and you either load it and do someothing wrong or load it and have no idea how to deal with it so you wasted bandwidth.<br>
&lt;dael> myles: It sounds like there is a real discussion so we should maybe continue next week.<br>
&lt;dael> TabAtkins: I'm repeating from the thread so put your arguments in there.<br>
&lt;dael> Rossen_: Sounds like we won't get to consensus today. We'll take it up next week.<br>
</details>


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

Received on Thursday, 3 May 2018 00:02:52 UTC