gcp

You also get the ability to deploy all browser infrastructure on-premise, to effectively decouple yourselves from us and get sync data, telemetry, and so on all stored on-prem, serve updates from your own servers, etc. This is something that wasn't really practical before.

I'm not sure why we would be okay with breaking a browser's trust in that way

I'm not sure what you mean here. If we accept that this is something a lot of Enterprise deployments require, wouldn't you prefer to have things like DLP, VPN and security logging be built-in in the browser, rather than being provided by third-party products that intercept or hook the browser traffic somehow?

Comment · 20 days ago

Can you please file a bug in Bugzilla with all the details? A colleague who works on this feature may be able to help get any relevant logging out of it to pinpoint the bug.

If the site is public and the issue happens in a fresh profile, just a link here would likely do the trick.

Comment · 20 days ago

Given that the initial market is Europe, where "surveillance of employees" has pretty strong legal limits, the answer to this is actually no! You can still report security relevant information and events of course, within reason.

Comment · 21 days ago

Of course with AI one could go as far as adding a "Report this site doesn't work in Firefox" button that magically sends a report (+ suggested fix) to the people operating the website/app.

Not sure if you're aware, but this button does actually exist in the help menu, at least for getting a public report filed. I looked through our tracker and didn't find any report similar to yours though (..and Office365 has a ton of webcompat bugs on file...), so I'd recommend you and "others" to actually file those bugs.

Finding and fixing those bugs in websites (unless they're behind a login that you can't easily sign up for) typically isn't the issue, but getting ahold of the site owner sometimes is.

If we can't get ahold of the website operator, or they're slow or unwilling to fix it, we can ship compatibility shims in the browser.

Take a look at about:compat to get some idea.

Comment · 21 days ago

you don’t need 750 employees to make a browser, and probably can’t effectively use even a hundred

Browser engines are incredibly complicated, yet at the same time are very performance and security sensitive while needing insane backwards compatibility and full multi-platform support. That unfortunately requires large teams, which is why there's only Gecko and WebKit/Blink left.

"Making a browser" you can do with a team of 1 person. Just search & replace the branding in the Chromium source.

Comment · 21 days ago

Only browser with an independent engine? Everything else is a Chromium reskin these days.

Comment · 21 days ago

Part of the sales pitch of Firefox Enterprise is that the management console includes a sync server that you can run on premise.