Hacker GitHub

← All repos

mozilla/standards-positions

View on GitHub ↗ ★ 763 HTML

192 mentions on Hacker News by 119 people: 14 stories, 178 comments · first 2019-03-13 · latest 2026-10-18

Mentions per year 192 mentions · busiest year 2023 (39)
20082026
  1. …implement jpegxl decoders in C/C++. I would really hope that isn't the case. Seems like they agree: https://github.com/mozilla/standards-positions/pull/1064
  2. …this into a web standard unilaterally; standards need consensus. Here is the Mozilla discussion: https://github.com/mozilla/standards-positions/issues/336 And here is the WebKit discussion: https://github.com/WebKit/standards-positions/issu…
  3. …have a positive view of the API [1], but it doesn't look like development has started [2]. [1] https://github.com/mozilla/standards-positions/issues/1053 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1923880
  4. …or refactors are more effective when it comes to the most core component of the browser. [0] https://github.com/mozilla/standards-positions/pull/1064
    comment by dralley · 2025-01-08 · in Servo Revival: 2023-2024
  5. I stand corrected. It was the absolute legends at Igalia. See links and explainer here: https://github.com/mozilla/standards-positions/issues/528
    comment by troupo · 2024-11-19 · in Is Chrome the New IE? (2023)
  6. …the unsuitability of these specifications in the Mozilla standards positions repo: Web Bluetooth: https://github.com/mozilla/standards-positions/issues/95 Web USB: https://github.com/mozilla/standards-positions/issues/100 Web MIDI:…
    comment by JimDabell · 2024-11-19 · in DOJ will push Google to sell off Chrome
  7. …hub.com/WebKit/standards-positions/issues/93 Here’s where Mozilla was asked for their position on it: https://github.com/mozilla/standards-positions/issues/350 Here’s the process Blink goes through to get a new feature like this going:…
  8. …just ship their own implementation, all others be damned. Here's the most egregious example: WebHID https://github.com/mozilla/standards-positions/issues/459 --- start quote --- - Asked for position on Dec 1, 2020 - One month later, on Jan…
    comment by troupo · 2024-11-02 · in Direct Sockets API in Chrome 131
  9. …Direct Sockets would be unsafe and inconsiderate given existing cross-origin expectations FWIU: https://github.com/mozilla/standards-positions/issues/431 > Direct Sockets API > Permissions Policy: https://wicg.github.io/direct-sockets/#perm…
    comment by westurner · 2024-11-02 · in Direct Sockets API in Chrome 131
  10. …analysis and conclusion "harmful" that Google sycophants and Apple haters couldn't care less about: https://github.com/mozilla/standards-positions/issues/431#is...
    comment by troupo · 2024-11-02 · in Direct Sockets API in Chrome 131
  11. I found this issue indicating a bad idea for end user safety: https://github.com/mozilla/standards-positions/issues/431
    comment by chrisvenum · 2024-11-02 · in Direct Sockets API in Chrome 131
  12. …of an otherwise essentially trusted app That’s what the Narrower Applicability section is about < https://github.com/mozilla/standards-positions/issues/431#is... >. It exposes new vulnerabilities because of IP address reuse across…
    comment by chrismorgan · 2024-11-02 · in Direct Sockets API in Chrome 131
  13. …used in Firefox, maybe there's a chance that Google would see the benefit in picking it up? [1] https://github.com/mozilla/standards-positions/pull/1064
    comment by SoothingSorbet · 2024-10-27 · in How JPEG XL compares to other image codecs
  14. …proposal [1], resolved it few years later [2], and finally implemented it since last year [3] [1] https://github.com/mozilla/standards-positions/issues/194#is... [2] https://github.com/mozilla/standards-positions/issues/194#is... [3]…
  15. …matter expertise to build a safe, performant, compact, and compatible JPEG-XL decoder in Rust https://github.com/mozilla/standards-positions/pull/1064
  16. Direct link to the comment on the thread: https://github.com/mozilla/standards-positions/issues/340#is...
  17. …on the topics API - https://github.com/WebKit/standards-positions/issues/111 also mentioned in https://github.com/mozilla/standards-positions/issues/622 The Register article on the topics api last year…
  18. …Google Research recently committed to help implementing it, in Rust, for inclusion in Firefox. https://github.com/mozilla/standards-positions/pull/1064 : “the team at Google has agreed to apply their subject matter expertise to build a…
  19. …Direct Sockets would be unsafe and inconsiderate given existing cross-origin expectations FWIU: https://github.com/mozilla/standards-positions/issues/431 Direct Sockets API > Permissions Policy: https://wicg.github.io/direct-sockets/#permis…
    comment by westurner · 2024-09-01 · in Chrome 130: Direct Sockets API
  20. …[3] (of course). 0: https://github.com/whatwg/fs/blob/main/proposals/MultipleReadersWriters.md 1: https://github.com/mozilla/standards-positions/issues/861 2: https://chromestatus.com/feature/5172892632875008 3:…
  21. …after compression dictionary work unblocked there concerns about dictionaries. As of 4 days ago! https://github.com/mozilla/standards-positions/pull/1042
    comment by jauntywundrkind · 2024-06-22 · in Exposition of Front End Build Systems
  22. You can read through the conversations to understand more of the context https://github.com/mozilla/standards-positions/issues/100#is... https://github.com/mozilla/standards-positions/issues/95#iss... https://github.com/mozilla/standards-po…
    comment by madeofpalk · 2024-05-03 · in Firefox Webserial Addon
  23. …was seen as reasonable by Mozilla. I'm not sure what progress has been on the proposal since then. https://github.com/mozilla/standards-positions/issues/154#is...
    comment by madeofpalk · 2024-04-16 · in iOS404
  24. You can check why Mozilla and Apple have opted to not support this. https://github.com/mozilla/standards-positions/issues/154 https://github.com/WebKit/standards-positions/issues/28 Neither Mozilla or Webkit are satisfied that the proposal…
    comment by madeofpalk · 2024-04-16 · in iOS404
  25. …such a stark "Google couldn't care less" dark-world fantasy. This is literally the timeline: https://github.com/mozilla/standards-positions/issues/459
  26. Hasn't FireFox been dragging their asses on @scope? https://github.com/mozilla/standards-positions/issues/472 It took years to just convince them of the need for it. And I'm not sure anyone got convinced vs Chrome had already shipped it…
  27. …For Position on Mozilla Zstd Support (2018) has a ton of interesting discussion on dictionaries. https://github.com/mozilla/standards-positions/issues/105 The original proposal for Zstd was to use a predefined stastically generated…
  28. …around the corner either. Happy (/hope) to be corrected. https://github.com/whatwg/html/issues/4180 https://github.com/mozilla/standards-positions/issues/990
    comment by 000ooo000 · 2024-02-29 · in An HTML Switch Control
  29. …in Chrome anyway, then people like you complain about Apple being mean. Here is Mozilla’s position: https://github.com/mozilla/standards-positions/issues/154 Here is Apple’s position: https://github.com/WebKit/standards-positions/issues/28
    comment by JimDabell · 2024-02-02 · in The web just gets better with Interop 2024
  30. …specs is nicely outlined publicly and transparently as part of their standards-positions project: https://github.com/mozilla/standards-positions/issues/100 I'm kinda glad it's not implemented in my browser, to be honest, because the whole…
    comment by lol768 · 2024-01-20 · in Platform Tilt
  31. …requirement? I think they explained their position pretty well here, regardless of whether I agree: https://github.com/mozilla/standards-positions/issues/95#iss...
  32. …but no sign of any movement on it: https://mozilla.github.io/standards-positions/#scroll-to-tex... https://github.com/mozilla/standards-positions/issues/194 https://bugzilla.mozilla.org/show_bug.cgi?id=1753933…
    comment by gwern · 2023-12-28 · in ArXiv now offers papers in HTML format
  33. …been marked as a “wontfix” in the Firefox bugtracker as they consider it a harmful feature [0] [0]: https://github.com/mozilla/standards-positions/issues/336
    comment by KANahas · 2023-12-28 · in Firefox Sync actually works
  34. Mozilla are dragging their heels on @scope: https://github.com/mozilla/standards-positions/issues/472 https://connect.mozilla.org/t5/ideas/implement-css-scope-rul... Someone who clearly didn't get it was wasting three years time "well…
    comment by Rapzid · 2023-12-27 · in CSS Is Fun Again
  35. …and Safari, but Firefox are dragging their feet. https://developer.chrome.com/docs/css-ui/at-scope https://github.com/mozilla/standards-positions/issues/472
    comment by montroser · 2023-12-27 · in CSS Is Fun Again
  36. …any version of Firefox, for the same reasons. Here's Mozilla's "considered harmful" GitHub issue. https://github.com/mozilla/standards-positions/issues/95
  37. …cherry-picked one every time. [1]: https://www.wired.com/story/chrome-yubikey-phishing-webusb/ [2]: https://github.com/mozilla/standards-positions/issues/58 [3]: https://github.com/mozilla/standards-positions/issues/238 [4]:…
    comment by soraminazuki · 2023-12-10 · in Firefox Keeps Getting Faster
  38. …dictionary to encode & Moz didn't want to have to "standardize" one specific dictionary. https://github.com/mozilla/standards-positions/issues/105
  39. …has taken a negative position against this standard. https://privacysandbox.com/proposals/topics/ https://github.com/mozilla/standards-positions/issues/622
    comment by brandon · 2023-08-08 · in Blocked by Cloudflare
  40. …a non-spec onto other browser vendors, shipped it to prod, and then "updated" the spec later: https://github.com/mozilla/standards-positions/issues/459
    comment by troupo · 2023-08-02 · in I'm betting on HTML
  41. …find the proposal itself, so I could see what the proponents considered the virtues of this to be. https://github.com/mozilla/standards-positions/issues/852 https://github.com/RupertBenWiser/Web-Environment-Integrity/... I stopped reading…
  42. …when they have been proven otherwise. [1] https://chromestatus.com/feature/5680923054964736 [2] https://github.com/mozilla/standards-positions/issues/622 [3] https://github.com/patcg-individual-drafts/topics
  43. …harmful to the openness of the Web ecosystem and are not good for users. The full response is here: https://github.com/mozilla/standards-positions/issues/852#is...
  44. …up again, here are my thoughts on the spec: - Mozilla is already publicly and officially opposed ( https://github.com/mozilla/standards-positions/issues/852#is... ), on principle ("Any browser, server, or publisher that implements common…
  45. > Mozilla opposes this proposal because it contradicts our principles and vision for the Web. https://github.com/mozilla/standards-positions/issues/852 I guess they would.
  46. …outline which goals are objectionable and why. Mozilla folks did a good job at articulating that in https://github.com/mozilla/standards-positions/issues/852#is ... Well, you asked for it, so here goes. WEI (IIUC) requires (at least the…
    comment by nobody9999 · 2023-07-25 · in So, you don't like a web platform proposal
  47. …which goals are objectionable and why . Mozilla folks did a good job at articulating that in https://github.com/mozilla/standards-positions/issues/852#is... A couple of things I should've included in that post and didn't: * It's important…
    comment by yoavweiss_ · 2023-07-25 · in So, you don't like a web platform proposal
  48. …was raised in February for both Mozilla[1] and WebKit[2] and neither have been responded to. [1] https://github.com/mozilla/standards-positions/issues/753 [2] https://github.com/WebKit/standards-positions/issues/142
  49. Given TFA, it looks like you can ask Mozilla for a position by opening a GitHub issue at https://github.com/mozilla/standards-positions
  50. …[5] https://github.com/RupertBenWiser/Web-Environment-Integrity/... [6] https://github.com/mozilla/standards-positions/issues/852#is...