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. Mozilla just took position against this DRM API: https://github.com/mozilla/standards-positions/issues/852#is... Also, Firefox just passed ahead of Chrome on some JS speed benchmark, so you should get ready to switch back!
  2. …it even exist at all?” wasn’t enough): https://github.com/WebKit/standards-positions/issues/111 https://github.com/mozilla/standards-positions/issues/622 https://github.com/w3ctag/design-reviews/issues/726
    comment by chrismorgan · 2023-07-13 · in New in Chrome 115
  3. …extension for that but not the bookmarking I was looking for.) A discussion about it is on GitHub: https://github.com/mozilla/standards-positions/issues/194 And there's some discussions on Reddit which are currently dead and I didn't…
  4. https://github.com/mozilla/standards-positions/issues/698 https://github.com/WebKit/standards-positions/issues/74 Hmm. I wish some other ones got as warm of a reception as this one.
    comment by benatkin · 2023-05-24 · in Popover API
  5. Mozilla is neutral on JPEG XL: https://github.com/mozilla/standards-positions/issues/522#is...
  6. I was curious about Mozilla's stance on the API. They have a GH issue for it: https://github.com/mozilla/standards-positions/issues/677 but it's not finalized yet. View the very interesting dashboard here:…
    comment by afraca · 2023-04-11 · in Htmx 1.9.0 has been released
  7. …gives a good summary of takes form both ends and why they decided their position was neutral https://github.com/mozilla/standards-positions/issues/522#is...
  8. …[2] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/... [3] https://github.com/mozilla/standards-positions/issues?q=anch...
  9. Not implemented in Firefox yet, but they like it: https://github.com/mozilla/standards-positions/issues/695 They're tracking work in https://bugzilla.mozilla.org/show_bug.cgi?id=1648037
    comment by jefftk · 2023-02-16 · in WebKit Supports Nested CSS
  10. Thankfully Firefox recently changed their stance from "Neutral" to "Positive". https://github.com/mozilla/standards-positions/pull/740 > Neutral stance: We're not convinced that the complexity this feature introduces upon the HTML parser…
    comment by j79 · 2023-02-13 · in Declarative Shadow DOM
  11. …usb port your device is connected to and "install." Bam, done. Firefox team views it as insecure: https://github.com/mozilla/standards-positions/issues/336
  12. …think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.
  13. …point. For the more general part of File System Access Mozilla's and Safari's positions are: nope. https://github.com/mozilla/standards-positions/issues/154 There was also Storage Foundation API but it was thankfully never shipped (it was…
  14. …is shipped by default. What was the input from other browsers? Here's the timeline for HID: https://github.com/mozilla/standards-positions/issues/459#is... Constructible Stylesheets: the spec contained a trivially reproducible race…
  15. …standards. Edit. As to "then someone writes a standard". This also happens. See Web HID timeline: https://github.com/mozilla/standards-positions/issues/459#is... Same happened to WebRTC, by the way. Stable spec version was finally complete…
  16. …by default in 2016, and which still had issues in 2019 that both Firefox and Safari objected to: https://github.com/mozilla/standards-positions/issues/214 No idea what their position on it is now. And so on and so forth. But these articles…
  17. …codecs have been developed. I'd like to highlight two things there: My arguments for JPEG XL: https://github.com/mozilla/standards-positions/issues/522#is... -- it comes with links to 3rd party evidence of the somewhat outrageous but…
    comment by JyrkiAlakuijala · 2022-11-03 · in The case for JPEG XL
  18. …[2] - https://helpx.adobe.com/camera-raw/using/hdr-output.html [3] - https://github.com/mozilla/standards-positions/issues/522#is... [4] - https://bugzilla.mozilla.org/show_bug.cgi?id=1539075#c23 [5] - https://github.com/exifto
  19. …For example, there is no way to get the URL if the protocol is `file://`. For a real world example: https://github.com/mozilla/standards-positions/issues/194#is... See the stack overflow issue: https://stackoverflow.com/questions/67039633/g…
  20. …features please tell me one. Easy. The most obvious/glaring one is WebHID. Enjoy the timeline: https://github.com/mozilla/standards-positions/issues/459 It's not just HID, of course. All/most of the hardware APIs are considered harmful by…
  21. …a bit strong in my accusations, because these people are doing bad, & uncompromisingly so. [1] https://github.com/mozilla/standards-positions/pull/368/file... [2] https://microbit.org/get-started/user-guide/web-usb/ [3]…
    comment by rektide · 2022-06-09 · in What’s new in Safari and WebKit
  22. …& "Intent to Prototype". Ah yes. "Responsible". Here's a prime example of responsibility: https://github.com/mozilla/standards-positions/issues/459 > Chrome wants & believes in an alive standards making process, in advancing, carefully,…
    comment by dmitriid · 2022-06-08 · in What’s new in Safari and WebKit
  23. …will serve the majority of web bundles, allowing them to see what sites the user is visiting. https://github.com/mozilla/standards-positions/issues/264 https://www.ghacks.net/2020/08/30/google-proposed-web-bundle...
  24. …(three years ago). Refs: - https://research.securitum.com/security-analysis-of-portal-e... - https://github.com/mozilla/standards-positions/issues/157
  25. …three years ago Firefox's position was also largely negative due to unresolved security issues: https://github.com/mozilla/standards-positions/issues/58 It's possible those issues are now resolved, that's why it's making its way into…
    comment by dmitriid · 2022-03-15 · in New WebKit features in Safari 15.4
  26. Someone linked "Request for position" on these APIs: https://github.com/mozilla/standards-positions/issues/519#is... Here's Mozilla's response: --- start quote --- 4x4 transforms: There are a bunch of implementation concerns here (and…
    comment by dmitriid · 2022-03-04 · in It's always been you, Canvas2D
  27. > 1. ctx.roundRect() ... Note: I can't find mention of .roundRect() in the MDN documentation. https://github.com/mozilla/standards-positions/issues/519#is... raised some questions about the addition of .roundRect(); I don't know if any…
    comment by jfk13 · 2022-03-04 · in It's always been you, Canvas2D
  28. …Or maybe look at the status of the APIs you so ardently defend. Example, WebHID timeline: https://github.com/mozilla/standards-positions/issues/459#is... etc. > It's also really important to be specific as to why the behaviour is harmful…
    comment by dmitriid · 2022-03-02 · in Open Web Advocacy
  29. …was had regarding this feature in Firefox[1] before brazenly claiming it's an obsolete browser. [1] https://github.com/mozilla/standards-positions/issues/194
  30. …of the standard - asks other browser vendors for their position on "emerging standard". Example, https://github.com/mozilla/standards-positions/issues/459 - ignores feedback, and enables by default (see link above) - advertises as fait…
  31. …feature [1], it comes at no surprise that major products are dropping Firefox compatibility. [1] https://github.com/mozilla/standards-positions/issues/154
    comment by kushan2020 · 2021-10-26 · in Photoshop’s journey to the web
  32. …what is even the point of Firefox? (Disclaimer, I work on Firefox but I know anything about specs.) https://github.com/mozilla/standards-positions/issues/453
  33. …a Google specific thing. It's worth to note that Mozilla's position on this proposal is "harmful": https://github.com/mozilla/standards-positions/issues/552
    comment by zebracanevra · 2021-09-16 · in Chrome user agent string reduction
  34. …storage/file api proposals, at least one of them is already in stable Chrome... it's a mess. [1] https://github.com/mozilla/standards-positions/issues/481 [2] https://lists.webkit.org/pipermail/webkit-dev/2021-February/...
    comment by dmitriid · 2021-08-13 · in A future for SQL on the web
  35. …pushes (and ships) "standards" so bad other browser developers can't even understand them [1] [1] https://github.com/mozilla/standards-positions/issues/459 Edit: grammar and typos
  36. …and releases them against any objections. See WebHID as the best example of this: Issue https://github.com/mozilla/standards-positions/issues/459#is... and timeline https://news.ycombinator.com/item?id=27512354
  37. …by Googlers only (sometimes with egregious disregard for standards work, see WebHID [1]). [1] Issue https://github.com/mozilla/standards-positions/issues/459#is... and timeline https://news.ycombinator.com/item?id=27512354
  38. …of the web all by themselves. There's clearly demand for these features (read the comments of https://github.com/mozilla/standards-positions/issues/154 for some examples). It would be better to have privacy and security baked in with input…
  39. …Safari and Firefox objecting to many, many, many things in the specs. Google. doesn't. care. [1] https://github.com/mozilla/standards-positions/issues/459#is... [2] https://webapicontroversy.com [3] https://web.dev/hid/
    comment by dmitriid · 2021-06-14 · in Let web applications be file handlers
  40. …and contrary to what the name might suggest, does not degrade a user's privacy or security. [1] https://github.com/mozilla/standards-positions/issues/154
    comment by kushan2020 · 2021-06-14 · in Let web applications be file handlers
  41. …are so Chrome-only) that sometimes the devs from competing browsers can't even understand them: https://github.com/mozilla/standards-positions/issues/459#is... And yet, Chrome will have you believe that these standards are not only there,…
    comment by dmitriid · 2021-06-14 · in Let web applications be file handlers
  42. …of the other browsers confusingly think this is a threat to the web ecosystem. [1] Mozilla https://github.com/mozilla/standards-positions/issues/154 [2] Brave https://github.com/brave/brave-browser/issues/11407
    comment by 1234fef · 2021-06-14 · in Let web applications be file handlers
  43. …lists this API as "defer" as well. https://mozilla.github.io/standards-positions/#wicg-file-han... https://github.com/mozilla/standards-positions/issues/158 is where they discussed that. (Note this is issue 158, as opposed to issue 154 in…
    comment by dfabulich · 2021-06-14 · in Let web applications be file handlers
  44. …is not standardised, and it likely won't be coming to Firefox at all, as they consider it harmful: https://github.com/mozilla/standards-positions/issues/154#is...
    comment by worble · 2021-06-14 · in Let web applications be file handlers
  45. The state of it in Firefox: "Opened Apr 2020" https://github.com/mozilla/standards-positions/issues/330 Then in October added "Insertable streams is worth prototyping " Also: "I will remind people that this isn't the place for advocating…
  46. It looks like mozilla has marked that standard as worth prototyping: https://github.com/mozilla/standards-positions/issues/330
  47. …6, 2020. And yet, as late as August 2020 they were saying that they'd just got the spec in shape: https://github.com/mozilla/standards-positions/issues/154#is... . And there are still unresolved issues around actual security of the thing…
  48. …happily shipped? Well, that specification is so bad that Mozilla devs didn't even understand it : https://github.com/mozilla/standards-positions/issues/459#is... Or look, Idle Detection API, currently in trial in Chrome. Firefox just…
  49. …in Chrome. They asked for Mozilla's position, and Mozilla couldn't even understand the proposal: https://github.com/mozilla/standards-positions/issues/459 And this keeps happening over and over and over and over again. Their reaction when…
  50. They've indicated they may: https://github.com/mozilla/standards-positions/issues/202#is... Commenting in support of Chrome's proposal to freeze the user agent and provide UACH instead.