Intentionally unusable. The text that is hidden elaborates:
> Is this really a good idea?
> Disabling a browser feature to replace it with your own implementation is a controversial topic. There are crowds that protest the very idea – that it's a much more complicated endeavor than it may initially appear. There are countless nuances and distinctions spread between different devices, operating systems, input controls, and applications.
> Covering every possible scenario is incredibly ambitious, and missing one could be a mistake you may not be able to afford. Consider the consequences: let's say you rolled out an elastic scrolling effect on your page, but you find out too late that 2% of your users on some device and software combination are impacted negatively. Not only are they deprived of the elastic euphoria, but the change has rendered the page unusable – they can't scroll.
> How quickly can you fix it? Are you willing to spend money to purchase the same device they're using so you can reproduce and debug it? How many more telephones can you stack in your closet before the tower tips over, sending a barrage of dusty cannonballs down on the box of Raspberry Pi parts on the floor? Is it finally time to move that box somewhere else?
> Maybe it's fine. Perhaps those users don't deserve to scroll. A privilege reserved for the elite 98%. This is your house and the scrollbar is your gatekeeper. Let them stand out there and peer through the bars, a distant glimpse of the fountain and marble lion statues is all they're getting. You didn't invite them. Put the rest of the page down there. `body { margin-top: 100vh; }`. Good luck trying to siege this castle with that moat of a scrollbar.
