mozilla/standards-positions on Hacker News

…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…

comment by pimterry · 2021-06-15 · in IndexedDB is completely broken in latest Safari

…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

…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

…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

…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

…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

…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

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…

comment by acqq · 2021-06-08 · in FaceTime on the web requires Chrome or Edge, no mention of Firefox

It looks like mozilla has marked that standard as worth prototyping: https://github.com/mozilla/standards-positions/issues/330

comment by X6S1x6Okd1st · 2021-06-08 · in FaceTime on the web requires Chrome or Edge, no mention of Firefox

…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…

comment by dmitriid · 2021-05-20 · in WebContainers: Run Node.js natively in the browser

…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…

comment by dmitriid · 2021-04-30 · in EU says Apple’s App Store breaks competition rules after Spotify complaint

…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…

comment by dmitriid · 2021-04-09 · in W3C slaps down Google's proposal to treat multiple domains as same origin

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.

comment by jefftk · 2021-03-22 · in Firefox 87 trims HTTP Referrers by default to protect user privacy

▲ 1

Chrome ships Web HID API. Mozilla devs can't even understand the specs

story by dmitriid · 2021-03-16 · 0 comments

…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

comment by dmitriid · 2021-03-03 · in Google to stop selling ads based on your specific web browsing

…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

…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…

comment by lioeters · 2021-02-06 · in Show HN: Web Serial Controller – Web App for USB Serial Communication

…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...…

comment by gred · 2021-02-01 · in Chrome 89 Beta: advanced hardware interactions, web sharing on desktop

…other browser implementors even had the chance to weigh in on the specification. See, for example, https://github.com/mozilla/standards-positions/issues/459

comment by dmitriid · 2021-02-01 · in Chrome 89 Beta: advanced hardware interactions, web sharing on desktop

Mozilla provided feedback on the text fragments spec: https://github.com/mozilla/standards-positions/issues/194#is...

comment by lol768 · 2020-11-18 · in Firefox beta supports Apple silicon natively

…That is misleading. Mozilla chose not to implement it for security concerns. More context: https://github.com/mozilla/standards-positions/issues/58#iss...

comment by nmy · 2020-10-16 · in Pianojacq, an easy way to learn to play the piano

…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

…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…

comment by nuker · 2020-09-09 · in The Native File System API allows web apps to save directly to files

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

comment by dstaley · 2020-06-30 · in Portals API

…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

comment by jamesgeck0 · 2020-06-29 · in Apple declined to implement 16 Web APIs in Safari due to privacy concerns

…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…

comment by SaijoGeorge · 2020-06-03 · in Google Automatically Adds Scroll to Text Fragment to Search Results on Chrome

Mozilla for now has been against WebMIDI due to concerns about the scope and security implications: https://github.com/mozilla/standards-positions/issues/58

comment by detaro · 2020-02-19 · in Show HN: An online drawing tool that lets you change colors via MIDI controller

"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

…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...

comment by uhoh-itsmaciek · 2020-01-30 · in MIDI 2.0, first major overhaul to music interface standard from 1983

…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

…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

…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)

…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

comment by robbrown451 · 2019-11-10 · in Using Firefox for a faster, calmer and distraction-free internet

If you want to see some part of this fixed, please UPVOTE this issue: https://github.com/mozilla/standards-positions/issues/143

comment by Jlleitschuh · 2019-07-09 · in Vulnerability in the Mac Zoom client allows malicious websites to enable camera

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

…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

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

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

…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

…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

…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

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