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. …clearly couldn't care less. [1] https://arstechnica.com/tech-policy/2011/09/owning-the-stack... [2] https://github.com/mozilla/standards-positions/issues/336
  2. …know enough about it in truth, but it seems like there ought to be a sensible compromise available. https://github.com/mozilla/standards-positions/issues/58 https://bugzilla.mozilla.org/show_bug.cgi?id=836897
    comment by tweetle_beetle · 2021-03-01 · in Show HN: WebMIDI Enabled Editors and Tools
  3. …it as WONTFIX, as of 9 months ago. https://bugzilla.mozilla.org/show_bug.cgi?id=926940 Discussion: https://github.com/mozilla/standards-positions/issues/336 It seems unlikely to be implemented in Firefox, unless they change their mind or…
  4. …legitimate concerns around privacy and security. Mozilla, for example, won't be implementing this: https://github.com/mozilla/standards-positions/issues/336 https://github.com/mozilla/standards-positions/commit/18aa5e...…
  5. …other browser implementors even had the chance to weigh in on the specification. See, for example, https://github.com/mozilla/standards-positions/issues/459
  6. Mozilla provided feedback on the text fragments spec: https://github.com/mozilla/standards-positions/issues/194#is...
  7. …That is misleading. Mozilla chose not to implement it for security concerns. More context: https://github.com/mozilla/standards-positions/issues/58#iss...
  8. …on from various spec and browser developers, but those seem to have generally been sorted out. But https://github.com/mozilla/standards-positions/issues/335 is still open and awaiting a response. • As far as putting things into the WHATWG…
    comment by chrismorgan · 2020-10-02 · in Declarative Shadow DOM
  9. …in the spec are inadequate and I am of the opinion that this should be marked harmful. " [0] [0] https://github.com/mozilla/standards-positions/issues/154#is... [1] Specification Positions https://mozilla.github.io/standards-positions/#nati…
  10. https://github.com/mozilla/standards-positions/issues/157
    comment by dstaley · 2020-06-30 · in Portals API
  11. …As neat as Web MIDI is, I think Mozilla and Apple probably made the right security call here. https://github.com/mozilla/standards-positions/issues/58
  12. …by Peter Snyder Security Researcher @ Brave and another comment from David Baron from Mozilla https://github.com/mozilla/standards-positions/issues/194#is... . And it looks like Google is now automatically adding Scroll To Text Fragment to…
  13. Mozilla for now has been against WebMIDI due to concerns about the scope and security implications: https://github.com/mozilla/standards-positions/issues/58
  14. "The major blocker right now is security issues related to device firmware hijacking." - https://github.com/mozilla/standards-positions/issues/58
    comment by FrankBooth · 2020-02-12 · in Firefox 73
  15. …and it's hard to explain "this page may hack your keyboard" in a permission request dialog): https://github.com/mozilla/standards-positions/issues/58#iss...
  16. …sites that support it. Firefox doesn't support this yet, after years and years of talking about it. https://github.com/mozilla/standards-positions/issues/58 There are a ton of other things, but that one is a deal breaker for me. Works…
    comment by robbrown451 · 2020-01-15 · in The new Microsoft Edge is out of preview
  17. …approve; it's not clear when (or if) that will happen. Here's the most recent discussion from May. https://github.com/mozilla/standards-positions/issues/154 So file access isn't technically "stalled out," but it's still going to take a…
    comment by dfabulich · 2020-01-03 · in Chrome OS has stalled out
  18. …a bit confused. The meat of their concerns also seem to be primarily political, not technical. [1]: https://github.com/mozilla/standards-positions
    comment by Ajedi32 · 2019-12-04 · in Fight back against Google AMP (2018)
  19. …for about 7 years, and I'm pretty sure the holdup on finalizing the draft is on the Mozilla side. https://github.com/mozilla/standards-positions/issues/58
  20. If you want to see some part of this fixed, please UPVOTE this issue: https://github.com/mozilla/standards-positions/issues/143
  21. If there is any question to if this was published by Mozilla: https://github.com/mozilla/standards-positions/issues/29#iss...
    comment by joshenglish · 2019-05-29 · in Mozilla Position on Web Packaging
  22. …by reading the full conversation leading up to the "harmful" tag before spamming that link again: https://github.com/mozilla/standards-positions/issues/29
    comment by Kiro · 2019-04-17 · in Announcing AMP Real URL
  23. Google's response: https://github.com/mozilla/standards-positions/issues/29#iss... In all fairness I have to agree with Google on this one. Mozilla's current objections don't really make sense.
    comment by Ajedi32 · 2019-04-17 · in Announcing AMP Real URL
  24. Worth noting that Mozilla's current position on this standard doesn't really make sense: https://github.com/mozilla/standards-positions/issues/29#iss... There may indeed be valid issues with the standard, but their current rationale for…
    comment by Ajedi32 · 2019-04-17 · in Announcing AMP Real URL
  25. …to respond and informing the other party that it will take a while is not "never responded". [0] https://github.com/mozilla/standards-positions/issues/29#iss...
    comment by RubenSandwich · 2019-04-17 · in AMP pages displaying your own domain
  26. …that might cause people to consider whether or not their position should be given much weight. [1] https://github.com/mozilla/standards-positions/issues/29#iss...
    comment by tytso · 2019-04-17 · in AMP pages displaying your own domain
  27. …in the spec. I don't believe he has expressed any opinion on the changes themselves. I just filed https://github.com/mozilla/standards-positions/issues/151 on getting an actual Mozilla position on this.
    comment by bzbarsky · 2019-04-08 · in Native image lazy-loading for the web
  28. FWIW, Mozilla's current objections to the standard don't really make sense. See: https://github.com/mozilla/standards-positions/issues/29#iss... It seems the real issue at the moment is that it just isn't a high priority for them.
    comment by Ajedi32 · 2019-03-13 · in New in Chrome 73