> Because removing the page-up/down functionality requires extra work.
100% this
Can someone PLEASE explain to me why front-end devs go out of their way to DISABLE features?
Scrolling works fine. Having multiple ways to scroll is user-friendly and adds accessibility. Someone please explain to me why a dev is going to go "You know, I don't use Page Down/Page Up to scroll, so I'm going to spend time hooking into the Page Down/Page Up key presses so they can be thrown out and disable scrolling through those keys".
EDIT: Page Up/Down work fine for me on that page btw. Using Chrome on a MacBook Pro.
100% this
Can someone PLEASE explain to me why front-end devs go out of their way to DISABLE features?
Scrolling works fine. Having multiple ways to scroll is user-friendly and adds accessibility. Someone please explain to me why a dev is going to go "You know, I don't use Page Down/Page Up to scroll, so I'm going to spend time hooking into the Page Down/Page Up key presses so they can be thrown out and disable scrolling through those keys".
EDIT: Page Up/Down work fine for me on that page btw. Using Chrome on a MacBook Pro.