3 ms·
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 c
by nerdjon 4y ago
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
- bee_rider 4y agoI'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.
- nerdjon 4y agoIf this is the intended effect, its bad one. 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.
- bee_rider 4y agoI get it on Apple as well. It must be a janky implementation or something.