Devs were only using one browser to test their code. Nonetheless, if you are going to implement any mouse behavior hijacking, you should reconsider your life choices. Take a long walk down the park, have a cup of coffee, come back and... Don't do it.
oh I totally get that, but I would expect that they would be doing their testing on Chrome. I mean I get not liking chrome but ignoring it for testing is... a choice.
I would have expected the worse behavior on Safari... not Chrome.
Or am I just being nieve about frontend development? I really only do it for any personal projects so don't really have any insight into it professionally
I'm not sure what the issue is (using firefox and I don't have Chrome installed to test with) but I'm pretty sure the scroll hijack that people are complaining about, it is an intentional effect to make the site "fancy," which they only tested in Chrome, or something like that.
One side perk of not using Chrome is that there's a correlation between only testing on Chrome and producing code that we're better off not interacting with.
I just find it interesting because I look at the apple product pages. While a bit janky they work as intended. But they are also applying that effect very deliberately and not to an article for some reason. So maybe that is the distinction.
