@raphlinus I don't suppose you know what the right place would be to submit a proposal for a new Compression webapi? (so that the gzip required for server-gzip/WOFF or brotli required for server-brotli/WOFF2 can be made available to everyone, rather than be locked away)
I think this level of standardization is IETF, which is why Brotli is an RFC (7932). But maybe I'm misunderstanding?
-
-
Oh, I think you're asking why compression is in neither the JS standard or as a Web API. I actually don't know the answer. But I think there might be some Web experts at the company you work for...
-
I'm not, I'm asking how to go about putting in a proposal to add a "Compression" object to the already established Web APIs (e.g. audio api, gamepad api, fetch api, etc). Browsers already have _almost_ all the code in place, all they need is to expose zip/gzip/brotli.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.