mozilla/standards-positions on Hacker News

…browser console and devtools for your page: > XSLT will be removed from this web browser soon. See https://github.com/mozilla/standards-positions/issues/1287

comment by pamcake · 2026-10-18 · in Chrome and Edge are removing XSLT: what breaks and what does not

…in the others’ decision-making. [1]: https://issues.chromium.org/issues/40168998#comment85 [2]: https://github.com/mozilla/standards-positions/issues/522#issuecomment-1409539985 [3]: https://github.com/web-platform-tests/interop/issues/430#…

comment by F3nd0 · 2026-10-07 · in Shipping JPEG XL in Chrome

They didn't want to add 100K lines of multithreaded C++, for security reasons. See https://github.com/mozilla/standards-positions/pull/1064 . (I edited the timeline to clarify)

comment by cbolton · 2026-08-26 · in Firefox 157 will include JPEG XL by default on all platforms

Since Sep 4, 2024: https://github.com/mozilla/standards-positions/pull/1064

comment by Vinnl · 2026-08-26 · in Firefox 157 will include JPEG XL by default on all platforms

…positive.[0] I would assume their position for other permissions elements would be the same. [0]: https://github.com/mozilla/standards-positions/issues/1288

comment by sheept · 2026-07-02 · in The <usermedia> HTML element

…Mozilla and Apple say they are never going to implement it because of security concerns https://github.com/mozilla/standards-positions/issues/154 It is a great API though, I wish the other browser vendors liked it! Because currently us PWA…

comment by streptomycin · 2026-06-22 · in window.showDirectoryPicker opens up a whole new world

…software distribution, then maybe software distribution outside of browsers should get fixed. * [0] https://github.com/mozilla/standards-positions/issues/522 * [1] https://github.com/mozilla/standards-positions/pull/1064

comment by cyberrock · 2026-06-04 · in Journey to JPEG XL: open-source experiments shaped the future of image coding

…the risks are and how intractable trying to explain them in a permission prompt would be. https://github.com/mozilla/standards-positions/issues/95#iss...

comment by greyface- · 2026-05-24 · in Build Adafruit projects right from Firefox

…& revamped DOM parsing which does not have the positive signals that out-of-order streaming does: https://github.com/mozilla/standards-positions/issues/1370 https://github.com/WebKit/standards-positions/issues/629

comment by JimDabell · 2026-05-24 · in API proposed by Chrome: Declarative partial updates

…the best places to check are the "standards positions" Github repositories for Mozilla and WebKit. https://github.com/mozilla/standards-positions/issues/1369 Mozilla hasn't officially weighed in, but one decision maker (hsivonen) did vote…

comment by dfabulich · 2026-05-24 · in API proposed by Chrome: Declarative partial updates

…this is not the right solution to each problem, or in some case a step in the wrong direction. — https://github.com/mozilla/standards-positions/issues/1076 — https://github.com/WebKit/standards-positions/issues/630 As far as I can see,…

comment by JimDabell · 2026-05-20 · in HTML-in-Canvas Demos

Also note the Mozilla standards position on this API: https://github.com/mozilla/standards-positions/issues/1213#i... Or this summary on its status: > Mozilla: Opposed > WebKit: Opposed > Microsoft: Several concerns > W3C TAG: Several…

comment by Vinnl · 2026-05-06 · in Google Chrome silently installs a 4 GB AI model on your device without consent

I had to dig around to see where they took the stand. https://github.com/mozilla/standards-positions/issues/1213#i... Mozilla makes great points. Even if the API is model agnostic, which it ought to be designed as from the very beginning…

comment by crumpled · 2026-05-05 · in Google Chrome silently installs a 4 GB AI model on your device without consent

…properly updating that section of the explainer, for sure. (But hey, not my job anymore!!) [1]: https://github.com/mozilla/standards-positions/issues/1067#i... [2]: https://github.com/whatwg/sg/pull/264 [3]:…

comment by domenicd · 2026-04-30 · in Mozilla's opposition to Chrome's Prompt API

The objections seem clear: tight-coupling of prompts to models, and model neutrality in the TOU. From https://github.com/mozilla/standards-positions/issues/1213 : "A personal example: I created a system prompt for creating announcements…

comment by heresie-dabord · 2026-04-30 · in Mozilla's opposition to Chrome's Prompt API

This is the specific position posted today/yesterday: https://github.com/mozilla/standards-positions/issues/1213#i...

comment by Vinnl · 2026-04-30 · in Mozilla's opposition to Chrome's Prompt API

Sigh, when I posted this, I linked to https://github.com/mozilla/standards-positions/issues/1213#i... (which was posted 11 hours ago). Unfortunately someone changed the link.

comment by jaffathecake · 2026-04-30 · in Mozilla's opposition to Chrome's Prompt API

When I posted this, I linked to the latest statement https://github.com/mozilla/standards-positions/issues/1213#i... , which is the content relevant to the title (the details of our opposition to the API). Unfortunately someone removed the…

comment by jaffathecake · 2026-04-30 · in Mozilla's opposition to Chrome's Prompt API

▲ 663

Mozilla's opposition to Chrome's Prompt API

story by jaffathecake · 2026-04-30 · 231 comments

…WebML Community Group meetings at the W3C every few weeks. There were async discussions like https://github.com/mozilla/standards-positions/issues/1213 and https://github.com/WebKit/standards-positions/issues/495 . (Side note, I love the…

comment by domenicd · 2026-04-27 · in The Prompt API

See also: https://github.com/mozilla/standards-positions/issues/1213

comment by kurtoid · 2026-04-27 · in The Prompt API

https://github.com/mozilla/standards-positions/issues/1067

comment by afshinmeh · 2026-04-27 · in The Prompt API

…on Selkies remote desktop sites, which I assume is rather poor for my bandwidth and battery. [0] https://github.com/mozilla/standards-positions/issues/238 [1] https://caniuse.com/webcodecs

comment by cyberrock · 2026-03-22 · in Apple's intentional crippling of Mobile Safari

…believe that a browser is not a general purpose application launcher No, it's security concern. https://github.com/mozilla/standards-positions/issues/100

comment by OJFord · 2026-03-02 · in /e/OS is a complete, fully “deGoogled” mobile ecosystem

Security concerns are exactly the reason the format doesn't have native support yet. However: https://github.com/mozilla/standards-positions/pull/1064

comment by Vinnl · 2026-01-22 · in JPEG XL Test Page

…unpopular things on the web: https://github.com/webmachinelearning/prompt-api/blob/main/R... https://github.com/mozilla/standards-positions/issues/1213 And model for yourself what happens if developer interest exceeds vendor refusal in…

comment by BoorishBears · 2026-01-05 · in Swift on Android: Full Native App Development Now Possible

…has some major security flaws. They basically want to wait until libjxl/jxl-rs is performant enough https://github.com/mozilla/standards-positions/pull/1064 Here's the current issue for that proposal if you want to get involved…

comment by culi · 2025-12-27 · in PNG in Chrome shows a different image than in Safari or any desktop app

…browser engines are working on implementing this spec. However their official positions are absent: https://github.com/mozilla/standards-positions/issues/1167 https://github.com/WebKit/standards-positions/issues/453 And Firefox’s bug for…

comment by JimDabell · 2025-12-05 · in CSS now has an if() conditional function

…has no desire to introduce a barely supported massive C++ decoder for marginal gains either: https://github.com/mozilla/standards-positions/pull/1064 avif is just better for typical web image quality, it produces better looking images and…

comment by homebrewer · 2025-11-24 · in Chrome Jpegxl Issue Reopened

…and we support Chromium's effort to find out if it would be web compatible to remove support. — https://github.com/mozilla/standards-positions/issues/1287#i... WebKit: > WebKit is cautiously supportive. We'd probably wait for one…

comment by JimDabell · 2025-11-05 · in Removing XSLT for a more secure browser

…and WebKit[^1] projects have also indicated plans to remove XSLT from their browser engines. [^0]: https://github.com/mozilla/standards-positions/issues/1287#i... [^1]: https://github.com/whatwg/html/issues/11523#issuecomment-314...

comment by sangeeth96 · 2025-11-05 · in Removing XSLT for a more secure browser

…into writing that they're considering adopting it when the rust implementation is production ready. https://github.com/mozilla/standards-positions/pull/1064

comment by OneDeuxTriSeiGo · 2025-10-27 · in Why JPEG XL ignoring bit depth is genius (and why AVIF can't pull it off)

…Chrome-only non-standards. - All of hardware standards. WebHID's timeline is especially egregious https://github.com/mozilla/standards-positions/issues/459#is... - Most of standards advertised on web.dev as "new exciting opportunities you…

comment by troupo · 2025-09-25 · in Helium Browser

It's already under consideration but needs some work first: https://github.com/mozilla/standards-positions/pull/1064

comment by Vinnl · 2025-09-20 · in Philips announces digital pathology scanner with native DICOM JPEG XL output

Their standards position is still neutral https://github.com/mozilla/standards-positions/issues/522#is... https://github.com/mozilla/standards-positions/blob/711c5330...

comment by drewbitt · 2025-09-15 · in JPEG XL support is back in Firefox Nightly

…consider. Safari seems to be in the same boat, but I can't find an official standards position. [1] https://github.com/mozilla/standards-positions/issues/154

comment by jazzypants · 2025-08-10 · in Ask HN: What toolchains are people using for desktop app development in 2025?

…on the initial positive position have not been addressed and some new issues have arisen. — https://github.com/mozilla/standards-positions/issues/618 Apple had a vague “interested” position over three years ago, with no further detail:…

comment by JimDabell · 2025-07-29 · in Sign in with Google in Chrome

- https://github.com/WebKit/standards-positions/issues/309 - https://github.com/mozilla/standards-positions/issues/618

comment by captn3m0 · 2025-07-29 · in Sign in with Google in Chrome

It, sadly, seems unrealistic to have that API with cross-browser compatibility. https://github.com/mozilla/standards-positions/issues/154 https://github.com/WebKit/standards-positions/issues/28

comment by uallo · 2025-07-22 · in How to Firefox

…hard to continue pushing its adoption forward. ------ 1. https://github.com/libjxl/jxl-rs 2. https://github.com/mozilla/standards-positions/pull/1064

comment by OneDeuxTriSeiGo · 2025-07-15 · in The JPEG XL Image Coding History, Features, Coding Tools, Design Rationale

https://github.com/mozilla/standards-positions/issues/1015

comment by RockRobotRock · 2025-06-25 · in Web Translator API

It's not yet the end, a rust decoder is on the way: https://github.com/mozilla/standards-positions/pull/1064#iss... One day, people will wonder why it took so long, and I'll smile =) That's the decoder: https://github.com/libjxl/jxl-rs…

comment by illiac786 · 2025-06-23 · in Why JPEGs still rule the web (2024)

Some nuance there — it's not dead yet: https://github.com/mozilla/standards-positions/pull/1064

comment by Vinnl · 2025-06-18 · in Why JPEGs still rule the web (2024)

…the rust implementation [2] to help get it up to feature parity with the reference impl. ----- 1. https://github.com/mozilla/standards-positions/pull/1064 2. https://github.com/libjxl/jxl-rs 3. https://github.com/libjxl/libjxl 4.…

comment by OneDeuxTriSeiGo · 2025-06-17 · in Why JPEGs still rule the web (2024)

Oh, sorry, the modal discussion is in the Mozilla position, for example: https://github.com/mozilla/standards-positions/issues/908

comment by Kwpolska · 2025-06-15 · in An origin trial for a new HTML <permission> element (2024)

…have an opinion yet, but that sure is an interesting way to say both Firefox and WebKit oppose it. https://github.com/mozilla/standards-positions/issues/908#is... https://github.com/WebKit/standards-positions/issues/270#iss...

comment by madeofpalk · 2025-06-15 · in An origin trial for a new HTML <permission> element (2024)

…gained support from WebKit: https://github.com/WebKit/standards-positions/issues/163 …and Mozilla: https://github.com/mozilla/standards-positions/issues/143 …and it was trialled in Blink: https://developer.chrome.com/blog/private-network-ac…

comment by JimDabell · 2025-06-03 · in Covert Web-to-App Tracking via Localhost on Android

…gained support from WebKit: https://github.com/WebKit/standards-positions/issues/163 …and Mozilla: https://github.com/mozilla/standards-positions/issues/143 …and it was trialled in Blink: https://developer.chrome.com/blog/private-network-ac…

comment by JimDabell · 2025-06-03 · in Covert web-to-app tracking via localhost on Android

…. Per the last post there (Aug 24). > Mozilla standard position on this feature is positive > https://github.com/mozilla/standards-positions/issues/993

comment by mrandish · 2025-04-09 · in Better typography with text-wrap pretty

Mozilla seems to be in favor as well: https://github.com/mozilla/standards-positions/pull/1190 (and funnily enough, a comment on this PR agrees with you in that background work might not be a significant factor in terms of energy…

comment by aeontech · 2025-04-03 · in Declarative Web Push