-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
output attributes on HTML's <input type=file>
element
#237
Comments
I am sympathetic to the argument that, even if client-side image optimization is technically possible today, it's the sort of complex thing that gets deployed by big sites when optimizing at scale. So this could both empower smaller developers, and nudge the ecosystem in a positive direction. On the flip side, I'm concerned about runaway complexity. The WICG thread is already talking about options for chroma sub-sampling, and it's not at all clear to me where the feature line should be drawn. Same goes for formats and media types. |
Agree, I also said the same in the thread. I think it should be possible to find a reasonable sub-set however. There is some precedence on iOS around images, for instance, and file size hints... and we could definitely make a case to triage, say, 2-3 things that would give the most return on investment. If those become interoperable, then pick up the next few from there and incrementally build on those across UAs. |
I'm concerned about complexity, and also concerned about inability to hook things up to other APIs the browser has reducing the value. I'd be less concerned about the latter if it output something like Maybe it makes more sense to start by more directly exposing the existing primitives, e.g., through a conversion of |
I think my inclination is to mark this as
Thoughts? |
It would indeed make much more sense to me if this were defined in terms of The other consideration here is that I think we only mandate conversion to PNG today, though I think implementations support JPEG too. |
<input type=file>
element
Request for Mozilla Position on an Emerging Web Specification
Other information
Proposal to add various output attributes on HTML's
<input>
elements that would allow developers to declare some conversions the browser could do to, for example, images and videos.Conversions can include:
This is intended to address the long-tail problem and complexity of converting/editing files by deferring the problem to either the OS or the browser (instead of JS libraries, CDNs, WASM, etc., which, it is argued by those making the proposal, haven't seen adoption in the long tail).
The text was updated successfully, but these errors were encountered: