| 14:21 | <annevk> | Adam Rice: all those isURL libraries do seem to do the equivalent of a hypothetical URL.canParse. Why do you expect that callers want something else? What would they want? |
| 14:24 | <Adam Rice> | Thanks for checking. I thought they might want a validation that the input "looks" like a URL, eg. it only has one colon after the scheme, no punctuation in the hostname, no double-slashes in the path, stuff like that. |
| 14:27 | <Adam Rice> | I don't know what to make of the fact that there are three different libraries that do the equivalent of new URL inside a try ... catch. I guess we need to "pave the cowpath" here. |
| 14:35 | <annevk> | Adam Rice: some do offer additional things like isHTTPURL() (not sure how to case that properly), but that's on top |
| 15:57 | <Eric Portis (he/him)> | Noam Rosenthal: I need to do some thinking about https://github.com/whatwg/html/issues/8143#issuecomment-1457636957 (particularly the "it's easy" bit...), but my first reaction is, what about audio and video? |
| 16:01 | <Noam Rosenthal> | Eric Portis (he/him): yea, easier than with images, I'll reword. |
| 16:03 | <Noam Rosenthal> | Eric Portis (he/him): you mean like CSS video backgrounds? Is that a thing? Video/Audio elements have a crossorigin attribute |
| 16:06 | <Eric Portis (he/him)> | Ok so adding crossorigin falls under the "it's easy" part, hm. background-image: url(whatever.mp4) might actually work in Safari? I should test that. But generally not a thing. |
| 16:07 | <Noam Rosenthal> | Eric Portis (he/him): adding crossorigin in conjunction with usually having a lot more images from different sources on the page than video/audio |
| 16:08 | <Noam Rosenthal> | but I think starting with images and perhaps expanding to audio/video if we see a need/value/adoption is reasonable |
| 16:08 | <Noam Rosenthal> | note also that no-cors video/audio has strange issues with service-workers because of range (206) requests |
| 16:41 | <Noam Rosenthal> | Eric Portis (he/him): btw for CSS images I hope to get this in at some point: https://github.com/w3c/csswg-drafts/pull/8222 but it won't make CORS CSS images "easy" (only "possible") |
| 17:37 | <Eric Portis (he/him)> | Noam Rosenthal: amazing, thank you!! (also thanks for plugging CSS image fetching into Fetch (https://github.com/w3c/csswg-drafts/pull/6715)... 🙌🏻🙏🏻) |
| 18:45 | <TabAtkins> | Noam Rosenthal: apologies for the delay on #8222, will get to it as soon as i can |