4 ms·

That’s odd. Are there standards in iOS Safari that macOS Safari doesn’t support, or that Firefox doesn’t support? It seems that if you have iOS in your user bas

by easton 6y ago

That’s odd. Are there standards in iOS Safari that macOS Safari doesn’t support, or that Firefox doesn’t support? It seems that if you have iOS in your user base, you couldn’t do Chrome only stuff anyway.

karatinversion 6y ago
I read it as “We only test on Chrome and mobile”.
- edoceo 6y ago
  I read: we don't test and our dev team only use Chrome
  - tomger 6y ago
    I read: this is a personal project of one of our devs who doesn’t use Firefox.
  - shadowgovt 6y ago
    Every team has a development environment. Some also have the luxury of a production environment that is separate from that environment.
- AlchemistCamp 6y ago
  I read it as "We hate the open web".
smnrchrds 6y ago
For the longest time, government websites in Iran required using Internet Explorer to access. A few years ago, it started to change. Now most of them refuse to work with anything but Chrome. At least in this sense, Chrome is really the new IE. And no, it's not because there is a standard Firefox does not support. I have installed a user agent switcher add-on on Firefox and that has been sufficient to let me use them. Like back in the days of IE, web developers do not care about users of non-dominant browsers to bother testing on them, and prefer to block them from access instead of risking receiving the occasional bug report or complaint from someone on Firefox or Safari.
- deleted 6y ago
  [deleted]
klodolph 6y ago
Nobody writes to the standard, because no browser is strict about only accepting standards-compliant code. Personal experience—there are a raft of minor differences between Chrome and Firefox, just to pick two. For example, they parse SVG paths differently. The exact behavior of <audio> tags when starting and stopping them used to be different (don’t know if it’s fixed). There are a bunch of other minor things. I have many times discovered that my app doesn’t work in Firefox if I’ve been developing in Chrome, or vice versa. If you write a lot of weird code, you can easily end up with broken features or a blank app and stack trace after switching browsers. Of course, 95% of the time it will work fine.
- shadowgovt 6y ago
  And to turn the question on its head: if a team has finite resources and can only get their site matching intended behavior 100% in one browser, obviously the right choice is one with dominant market-share, not sub-10% market-share, if the goal is to maximize number of people who can see the site.
Kiro 6y ago
My app is unusable in Firefox due to this: https://bugzilla.mozilla.org/show_bug.cgi?id=925025 https://bugzilla.mozilla.org/show_bug.cgi?id=925025 On Safari I get extremely low FPS in general when drawing on layered canvases and sound is not working at all.

by easton 6y ago

karatinversion 6y ago

I read it as “We only test on Chrome and mobile”.

edoceo 6y ago
I read: we don't test and our dev team only use Chrome
- tomger 6y ago
  I read: this is a personal project of one of our devs who doesn’t use Firefox.
- shadowgovt 6y ago
  Every team has a development environment. Some also have the luxury of a production environment that is separate from that environment.
AlchemistCamp 6y ago
I read it as "We hate the open web".

smnrchrds 6y ago

For the longest time, government websites in Iran required using Internet Explorer to access. A few years ago, it started to change. Now most of them refuse to work with anything but Chrome. At least in this sense, Chrome is really the new IE. And no, it's not because there is a standard Firefox does not support. I have installed a user agent switcher add-on on Firefox and that has been sufficient to let me use them. Like back in the days of IE, web developers do not care about users of non-dominant browsers to bother testing on them, and prefer to block them from access instead of risking receiving the occasional bug report or complaint from someone on Firefox or Safari.

deleted 6y ago
[deleted]

klodolph 6y ago

Nobody writes to the standard, because no browser is strict about only accepting standards-compliant code. Personal experience—there are a raft of minor differences between Chrome and Firefox, just to pick two. For example, they parse SVG paths differently. The exact behavior of <audio> tags when starting and stopping them used to be different (don’t know if it’s fixed). There are a bunch of other minor things. I have many times discovered that my app doesn’t work in Firefox if I’ve been developing in Chrome, or vice versa. If you write a lot of weird code, you can easily end up with broken features or a blank app and stack trace after switching browsers. Of course, 95% of the time it will work fine.

shadowgovt 6y ago
And to turn the question on its head: if a team has finite resources and can only get their site matching intended behavior 100% in one browser, obviously the right choice is one with dominant market-share, not sub-10% market-share, if the goal is to maximize number of people who can see the site.

Kiro 6y ago

My app is unusable in Firefox due to this: https://bugzilla.mozilla.org/show_bug.cgi?id=925025 https://bugzilla.mozilla.org/show_bug.cgi?id=925025 On Safari I get extremely low FPS in general when drawing on layered canvases and sound is not working at all.