3 ms·

The important line here is this: > The update in Firefox 68 brings the Firefox implementation in line with Scroll Snap as implemented in Chrome and Safari Whi

The important line here is this: > The update in Firefox 68 brings the Firefox implementation in line with Scroll Snap as implemented in Chrome and Safari While "and Safari" is a less-relevant detail here, the general point is: where there is a monopoly, minority browsers will often need to implement user-hostile features in order to remain relevant/up-to-date/compatible. Web devs today don't test in Firefox, they test in Chrome. They might have a webdriver/saucelabs/etc. setup with Firefox/IE/Edge thrown in but in terms of day-to-day these are afterthoughts.

KamBha 7y ago
I only test in Firefox, because FF is my browser of choice. Everyone else in the office only tests on Chrome because that is their browser of choice. We all know it is wrong, but cross browser compatibility makes it so much easier to forget that there are subtle differences. Fun fact, we recently found a performance issue on one of our products which I was completely unaware of because it didn't affect. Even now, we cannot get Chrome to match FF's performance especially (of all things) for Google maps. Just goes to show that basic assumptions that Chrome is faster than Firefox are not 100% accurate. Like most things, it depends.
irrational 7y ago
What we do at my work is assign each developer a browser. I only use Firefox. Another coworker only uses Chrome. Etc. This way we will hopefully find any major browser issues before they get to QA.
magicalist 7y ago
The actual important line is the next one: > In addition, it removes the old properties which were part of the earlier Scroll Snap Points Specification. The earlier API was based on a working draft spec and has been available since 2015 in Firefox (Chrome only brought it out without a flag in 2018), so this isn't a recent development. https://caniuse.com/#search=scroll%20snap https://caniuse.com/#search=scroll%20snap
pbhjpbhj 7y ago
>Web devs today don't test in Firefox, they test in Chrome.// It's kind of an aside, but is that true? I only do small scale solo dev but I test in like a dozen UA as the bare minimum I can get away with. Presumably you're being slightly hyperbolic and saying that devs who are under major constraints will target Chrome?

KamBha 7y ago

I only test in Firefox, because FF is my browser of choice. Everyone else in the office only tests on Chrome because that is their browser of choice. We all know it is wrong, but cross browser compatibility makes it so much easier to forget that there are subtle differences. Fun fact, we recently found a performance issue on one of our products which I was completely unaware of because it didn't affect. Even now, we cannot get Chrome to match FF's performance especially (of all things) for Google maps. Just goes to show that basic assumptions that Chrome is faster than Firefox are not 100% accurate. Like most things, it depends.

irrational 7y ago

What we do at my work is assign each developer a browser. I only use Firefox. Another coworker only uses Chrome. Etc. This way we will hopefully find any major browser issues before they get to QA.

magicalist 7y ago

The actual important line is the next one: > In addition, it removes the old properties which were part of the earlier Scroll Snap Points Specification. The earlier API was based on a working draft spec and has been available since 2015 in Firefox (Chrome only brought it out without a flag in 2018), so this isn't a recent development. https://caniuse.com/#search=scroll%20snap https://caniuse.com/#search=scroll%20snap

pbhjpbhj 7y ago

>Web devs today don't test in Firefox, they test in Chrome.// It's kind of an aside, but is that true? I only do small scale solo dev but I test in like a dozen UA as the bare minimum I can get away with. Presumably you're being slightly hyperbolic and saying that devs who are under major constraints will target Chrome?