Or uBlockOrigin in "medium mode" or higher incorporates JS blocking on a per-site basis.
window.removeEventListener('wheel', getEventListeners(window)['wheel'][0].listener); metaphysic.ai##+js(aeld, wheel)
Done.Why do people think it's a good idea to circumvent the scrolling behavior that the developers of the browser probably have spent hundred of hours perfecting over the years?
I switched to chrome, and that is just horrible!
I am curious why I am not seeing this on Safari (and apparently others on Firefox). I don't see any errors on Safari implying that some javascript is failing to load.
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
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.