standards-positions VS firefox-ios

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 is safe by default, and contains footguns for the user that can be pretty destructive.

FWIW Mozilla updated their position on Web Serial API to "neutral" and clarified that they might be okay with enabling the API with an add-on.

https://mozilla.github.io/standards-positions/#webserial

Allowing serial but not HID would be really strange. With HID you get standard identifiers that let you filter out devices that are too dangerous for the web. With serial you get nothing. Even if you know a device is dangerous, there's no way to protect users from it.

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 and Safari has it planned so they caved in.

Hard to believe FireFox used to be a leader of the modern web.

As mentioned by others, OK idea, but not a fan that this isn't standardized. After a quick search+peruse, these seem to indicate that it's not around the corner either. Happy (/hope) to be corrected.

https://github.com/whatwg/html/issues/4180

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

Mozilla's position on these 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 thing seems like a security nightmare.

It's a shame it impacts some hobby usecases, but I don't think this outweighs the reasoning set out on the GitHub issue.

This should have big warnings on it. Some of these are not web standards; they are features implemented unilaterally by Google in Blink that have been explicitly rejected by both Mozilla and Apple on privacy and security grounds.

Take Web Bluetooth, for example:

Mozilla:

> This model is unsustainable and presents a significant risk to users and their devices.

— https://mozilla.github.io/standards-positions/#web-bluetooth

Apple:

> Here are some examples of features we have decided to not yet implement due to fingerprinting, security, and other concerns, and where we do not yet see a path to resolving those concerns

— https://webkit.org/tracking-prevention/

This is Microsoft’s Embrace, Extend, and Extinguish bullshit applied to the web platform by Google. Google keeps implementing these things despite all other major rendering engines rejecting them, convinces people that they are part of the web, resulting in sites like this, then people start asking why Firefox and Safari are “missing functionality”. These are not part of the web platform, they are Google APIs that have been explicitly rejected.

Is BLE a PWA requirement? I think they explained their position pretty well here, regardless of whether I agree:

https://github.com/mozilla/standards-positions/issues/95#iss...

I took a glance at Can I Use what the difference between the last public release of Firefox and Chrome is [1] and they don't really have that big of a difference in the eyes of normal use-cases? Some of these aren't implemented purely because of privacy reasons, the proposals aren't finished yet or complexity [2].

Why would Firefox need to change to Chromium engine? The only websites I notice that don't work with Firefox is because of user-agent targetting or just putting 5-second time-outs in Youtube code on non-chrome webbrowsers [3].

Can you give some examples of websites not working on Firefox?

[1] https://caniuse.com/?compare=chrome+120%2Cfirefox+121&compar...

[2] https://mozilla.github.io/standards-positions/

[3] https://www.neowin.net/news/youtube-seemingly-intentionally-...

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 actually"ing everything. The latest news is "it's worth prototyping". Meanwhile Chrome has released it(steam rolled?) and Safari has it in tech preview.

I question if FireFox has the resources to keep up with the pace of the modern web.

Users are complaining that the latest Firefox for iOS update has removed the "Dark mode" option from the menu:[1]

> I suffer from Diabetic Retinopathy and hence photophobia. To me, this removal is an Accessability issue.

A forum moderator who's in touch with the developers said days ago that this is an experiment affecting half of the userbase:[2]

> The team is currently doing an experiment. Since March 15, 50% of users no longer see Night Mode switch from the hamburger menu. We're using this experiment to monitor and evaluate the impact of removing, so it'll be hugely valuable to hear your feedback around this feature. Thanks!

However, Mozilla's iOS team manager doesn't know about this huge experiment and think it is a bug:[3]

> Moving Focus into the Firefox repo so it can get more love and support. This happened last release and may be the culprit that broke dark mode. We're looking into this right now.

[1] https://github.com/mozilla-mobile/firefox-ios/issues/19365#issuecomment-2018447405

Yeah, Orion's support for Firefox extensions is a big red flag. These 2 issues on the Firefox-iOS tracker[0,1] around extensions and content blockers have long mentioned Orion, but there's no response from Mozilla.

[0]: https://github.com/mozilla-mobile/firefox-ios/issues/7374

[1]: https://github.com/mozilla-mobile/firefox-ios/issues/9155

If you keep being logged out, open this page and click on New issue.

Follow this bug report: Tabs reload when switching to another tab or app and screen remains blank in Firefox for iOS.

Please file an issue on Bugzilla (Android) or GitHub (iOS).

Please open this page and click on New issue to report bugs affecting Firefox for iOS.

If you have a GitHub account, subscribe to this issue: Extensions support on iOS.

https://github.com/mozilla-mobile/firefox-ios/commit/686d36402c6a956f460abafc8f1fe19a7887a2f3 landed in v38, so it looks like v37 was the last to support iOS 12.

When you use Reader View, Firefox parses the text of the webpage and loads it as a local page. It isn't supposed to show a red slash, though. Reader Mode shows a neutral icon (📄) on the desktop version. Please open this page and click on New Issue to report this to Mozilla, and then share the link with us.