We’ve been anticipating it for years,1 and it’s finally happening. Google is finally killing uBlock Origin – with a note on their web store stating that the …
We’ve been anticipating it for years,1 and it’s finally happening. Google is finally killing uBlock Origin – with a note on their web store stating that the …
Firefox needs to work on ensuring seamless compatibility with more websites, web apps and so on, because I’m personally very bored with my kids’ schools and related services sending out emails and forms with links that simply won’t open in FF but are clearly expecting Chrome or Edge where they work fine. Yes, this is on the lazy developers, but if FF want wider scale take-up outside of geeky niche groups then this is the stuff they must fix.
I just want my modern codecs to function. Why can’t I play .mov or h264??
Firefox can’t fix all the broken sites in the world, but they do investigate issues reported to https://webcompat.com
You can help by reporting sites that don’t work for you.
Yeah, unfortunately the next step will be sites rejecting “unsecure” browsers because they want the ad money.
This is going to get worse, not better.
What to do when the site is not compatible with Firefox: Alt + ←
I encounter this very infrequently. I think I only have 1-2 examples at work. It’s not a huge deal for me to spin up a chrome for those one or two occasions.
Just make an electron out of those sites 🌚
Sounds interesting, care to expand?
The only concrete one I can actually recollect is generating a quote from our quoting tool in Salesforce. I just ended up running my 100+ Salesforce windows in Chrome because it has a good feature where you can name each window so I can see which customers I’m working on in the taskbar. It’s good to have those cordoned off from my normal browsing anyway. So this one doesn’t bother me. For everything else I use Firefox.
I used this prompt
And chatGPT gave me a good instruction, will try that out. Apparently, you only need node, electron and the javascript like this:
const { app, BrowserWindow } = require('electron') function createWindow() { // Create the browser window const win = new BrowserWindow({ width: 800, height: 600, webPreferences: { nodeIntegration: true } }) // Load the third-party web app win.loadURL('https://www.thirdpartyapp.com') // Optionally remove the default menu win.setMenu(null) // Open DevTools (optional for debugging) // win.webContents.openDevTools() } // Run the createWindow function when Electron is ready app.whenReady().then(createWindow) // Quit when all windows are closed app.on('window-all-closed', () => { if (process.platform !== 'darwin') { app.quit() } }) app.on('activate', () => { if (BrowserWindow.getAllWindows().length === 0) { createWindow() } })I still don’t know what this is though? Something Linux specific?
Electron is a tool to bundle a website and a interpreter for that website in an application. That works on many platforms. Official discord desktop app, for example, is an electron app, spotify as well.
What you’re talking about is webcompat and is a very complicated issue. Also I’ve talked to some Mozilla devs who gave me multiple examples of Chromium rendering something wrong, and they’d have to intentionally break Firefox to render it incorrectly too, just so the end user would get a more consistent experience. Of course these issues happen more and more when things are only tested for one browser.
This is Chromium monopoly. At this time instead of W3C standards, Chromium itself becomes the standard.
Maybe there could be some sort of compatibility flag in Firefox which detects non-standard pages designed for Chrome. We could call it… hmm… something like Quirks Mode?
Slack calls disabled for firefox users, but if you change the user agent to chrome it works…
Almost like it does work on Firefox but for some reason they don’t want you using it. Honestly it’s so damn weird, why do that? Is there some incentive for them?
It’s pretty trivial to just use an alternate browser for the garbage sites that don’t support FF.