> some UX that doesn't exist and won't exist as it's outside the scope of the project It seems to me removing scrolling is actually work as opposed to just let

> some UX that doesn't exist and won't exist as it's outside the scope of the project It seems to me removing scrolling is actually work as opposed to just letting the default behavior of the browser to prevail. I'm not saying there is no point in having a site with keyboard navigation as the primary mode of interaction. It's just that when you go out of your way to remove something that should be supported natively you're scope creeping. If losing selection highlight is a problem just disable that feature only why mess with scrolling?