Yoav Weiss
Yoav Weiss
> It would mean that `image/jxl` would not work cross-origin by default. This would be similar to module scripts. The usage patterns of module scripts and images are extremely different....
I understand the benefits of CORS in general, but protecting one format while not protecting others seem to provide marginal benefits at best. > I think you can make a...
> * CORS, while this has opposition it is the correct solution. And for other formats this is what we require, e.g., module scripts Module scripts are significantly different than...
Requiring CORS for new image types would have the following consequences: * Developer confusion - Developers would not understand why they need to add `crossorigin` attributes to `` tags when...
The only scenario in which we would be doing that is the one where developers actually adopt new formats (despite the hurdles pointed out in my [comment above](https://github.com/annevk/orb/issues/3#issuecomment-973818278)), and they...
> It's not clear to me why the transition for media formats is harder than for JS (note that JS modules require CORS as well as a MIME type) JS...
I'm happy to hear that the image-CDN use case is one that we would be able to solve with CORP. I'm still concerned about developer confusion when it comes to...
You're right. I'll add one (It's tested in the layout tests, but that's no excuse)
Shouldn't we spec this? I don't think picture's ARIA roles are well defined
Shouldn't we spec this as part of picture's accessibility model?