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. Firefox already has indicated that they approve of the new proposal: https://github.com/mozilla/standards-positions/issues/1060 We're only waiting on Safari now: https://github.com/WebKit/standards-positions/issues/386
  2. …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
  3. …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…
  4. …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
  5. …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
  6. 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)
  7. …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
  8. …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:…
  9. …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
  10. …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
  11. …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
  12. 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
  13. …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
  14. …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
  15. …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]…
  16. …matter expertise to build a safe, performant, compact, and compatible JPEG-XL decoder in Rust https://github.com/mozilla/standards-positions/pull/1064
  17. Direct link to the comment on the thread: https://github.com/mozilla/standards-positions/issues/340#is...
  18. ▲ 1
    Mozilla is currently not investing in PWAs (2021)
    story by trekz · 2024-10-18 · 3 comments
  19. …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…
  20. …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…
  21. ▲ 154
    Firefox will consider a Rust implementation of JPEG-XL
    story by mariuz · 2024-09-04 · 67 comments
  22. ▲ 13
    Firefox will consider a Rust implementation of JPEG-XL
    story by Fudgel · 2024-09-03 · 1 comment
  23. …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
  24. …[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:…
  25. …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
  26. 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
  27. …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
  28. 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
  29. …such a stark "Google couldn't care less" dark-world fantasy. This is literally the timeline: https://github.com/mozilla/standards-positions/issues/459
  30. 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…
  31. …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…
  32. …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
  33. …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
  34. …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
  35. …requirement? I think they explained their position pretty well here, regardless of whether I agree: https://github.com/mozilla/standards-positions/issues/95#iss...
  36. …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
  37. …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
  38. 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
  39. ▲ 1
    Mozilla's Position on CSS Scope
    story by Rapzid · 2023-12-27 · 1 comment
  40. …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
  41. ▲ 7
    Mozilla to Support Trusted Types
    story by CharlesW · 2023-12-22 · 1 comment
  42. …any version of Firefox, for the same reasons. Here's Mozilla's "considered harmful" GitHub issue. https://github.com/mozilla/standards-positions/issues/95
  43. …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
  44. ▲ 1
    WebHID API
    story by soraminazuki · 2023-12-10 · 0 comments
  45. ▲ 4
    Request for Position: WebUSB API
    story by xeonmc · 2023-11-06 · 0 comments
  46. …dictionary to encode & Moz didn't want to have to "standardize" one specific dictionary. https://github.com/mozilla/standards-positions/issues/105
  47. …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
  48. …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
  49. …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…
  50. …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