7 ms·

Most browsers are based on Chrome/Blink or at the very least WebKit now. Even Microsoft have thrown in the towel for the better as the new Edge is awesome. The

Most browsers are based on Chrome/Blink or at the very least WebKit now. Even Microsoft have thrown in the towel for the better as the new Edge is awesome. The only outlier nowadays is really Firefox/Gecko but they do a good job of keeping to standard, it's rare to find a site that doesn't work with it.

ilikepi 6y ago
And Safari, which is not insignificant if you're including mobile platforms.
- benbristow 6y ago
  Hence the mention of WebKit which Safari uses.
  - ilikepi 6y ago
    Apologies. That's what I get for posting while distracted from a conference call.
detritus 6y ago
I dunno - I hit a site a week that doesn't work in Firefox. The latest being a list of shows on https://www.bfi.org.uk/ https://www.bfi.org.uk/ that didn't … well, list. Turns out it did fine enough in Chrome. I accept that sites can be 'optimised' for use in certain browsers, but a complete lack of functionality is fundamentally anti-web and a sign of sloppy development. - ed url changed to correct one
- wldcordeiro 6y ago
  Almost always the sites that don't work in Firefox tend to do things in Chrome specific ways.
- shadowgovt 6y ago
  Any idea if the issue in BFI's website is the site or Firefox's implementation of the standard?
  - detritus 6y ago
    tbh, i didn't bother opening up the console and checking as I was a bit busy at the time and, bluntly - why should I? But I did get in touch to let them know there was an issue. Ultimately - it was a list of entries from a database. There's no real reason they should've been caught out by some inter-Browser Gotcha!
    - shadowgovt 6y ago
      Yep, and now we can see why developers end up putting "Best viewed with Chrome" on their pages; it's easier than handling bug reports from a userbase that won't open the console (nor should the users be expected to, but that's the space we live in). There's no real reason, but there is a reason. And part of the 5 why's analysis will show that the developer doesn't test on Firefox, but why should they when less than 1 in 10 users will use Firefox? They'll only make the spend if they have ideological dedication to a poly-culture of browsers or they are incentivized to capture the subset of the last 10% of potential users who can't see their way to switching to Chrome (for even one website).
      - detritus 6y ago
        All this has happened before, and will happen again. The reason should be that developers develop along as simple and as standardised a means as they can, so that what they're working on will be consumable by as many people now, and in future as they can be. Sure, I'm of the 0.001% of people on the planet that could easily spend a half hour going through the console and working out why on Earth their content isn't displaying to me… but this is a .org (.uk) - their remit is to be open and to Do The Right Thing. Almost 100% of their users are not the sort that should be expected to dissect their website to work out where they've gone wrong. Again, this isn't anything complicated - it should just be HTML spat out. That's it. Nothing fancy.
- extra88 6y ago
  Visiting the BFI site now, it looks the same in Firefox and Chrome. Maybe the problem you experienced was not due to a failure on the site designers' part or Firefox but elsewhere; a temporary "glitch" in its delivery to your Firefox browser, one of your browser extensions mucking it up, etc. I don't encounter sites that don't work in Firefox but a lot of that probably has to do with my browsing tendencies.
sebazzz 6y ago
SAP broke Successfactors in Firefox recently. I couldn't start my annual mandatory course I need for my work.

ilikepi 6y ago

And Safari, which is not insignificant if you're including mobile platforms.

benbristow 6y ago
Hence the mention of WebKit which Safari uses.
- ilikepi 6y ago
  Apologies. That's what I get for posting while distracted from a conference call.

detritus 6y ago

I dunno - I hit a site a week that doesn't work in Firefox. The latest being a list of shows on https://www.bfi.org.uk/ https://www.bfi.org.uk/ that didn't … well, list. Turns out it did fine enough in Chrome. I accept that sites can be 'optimised' for use in certain browsers, but a complete lack of functionality is fundamentally anti-web and a sign of sloppy development. - ed url changed to correct one

wldcordeiro 6y ago
Almost always the sites that don't work in Firefox tend to do things in Chrome specific ways.
shadowgovt 6y ago
Any idea if the issue in BFI's website is the site or Firefox's implementation of the standard?
- detritus 6y ago
  tbh, i didn't bother opening up the console and checking as I was a bit busy at the time and, bluntly - why should I? But I did get in touch to let them know there was an issue. Ultimately - it was a list of entries from a database. There's no real reason they should've been caught out by some inter-Browser Gotcha!
  - shadowgovt 6y ago
    Yep, and now we can see why developers end up putting "Best viewed with Chrome" on their pages; it's easier than handling bug reports from a userbase that won't open the console (nor should the users be expected to, but that's the space we live in). There's no real reason, but there is a reason. And part of the 5 why's analysis will show that the developer doesn't test on Firefox, but why should they when less than 1 in 10 users will use Firefox? They'll only make the spend if they have ideological dedication to a poly-culture of browsers or they are incentivized to capture the subset of the last 10% of potential users who can't see their way to switching to Chrome (for even one website).
    - detritus 6y ago
      All this has happened before, and will happen again. The reason should be that developers develop along as simple and as standardised a means as they can, so that what they're working on will be consumable by as many people now, and in future as they can be. Sure, I'm of the 0.001% of people on the planet that could easily spend a half hour going through the console and working out why on Earth their content isn't displaying to me… but this is a .org (.uk) - their remit is to be open and to Do The Right Thing. Almost 100% of their users are not the sort that should be expected to dissect their website to work out where they've gone wrong. Again, this isn't anything complicated - it should just be HTML spat out. That's it. Nothing fancy.
extra88 6y ago
Visiting the BFI site now, it looks the same in Firefox and Chrome. Maybe the problem you experienced was not due to a failure on the site designers' part or Firefox but elsewhere; a temporary "glitch" in its delivery to your Firefox browser, one of your browser extensions mucking it up, etc. I don't encounter sites that don't work in Firefox but a lot of that probably has to do with my browsing tendencies.

sebazzz 6y ago

SAP broke Successfactors in Firefox recently. I couldn't start my annual mandatory course I need for my work.