1) A native scrollbar that is restyled to match the colors of the webpage it is in? 2) A janky web view with scrollbars hidden and then reimplemented in JS which doesn't function they way you want it to?
Like it or not designers usually don't spend time on the subset of the audience that clicks and drags the scrollbar. They spend time drawing a pretty looking scrollbar.
When it comes to the implementation personally I think it still better to have a scrollbar that functions the way you expect it to, even if it looks a little different, rather than ending up with many different reimplementations of the scrollbar by different programmers.
> Like it or not designers usually don't spend time on the subset of the audience that clicks and drags the scrollbar. They spend time drawing a pretty looking scrollbar.
If the designers in question, who are working on a user interface element, don't consider how users will interface with it, it's fair to criticise them for not doing their jobs.
Really? Have you got any numbers for this, or are you actually saying "this is how I use it, and I presume most people are like me"? Because what you're saying simply isn't true for me.
When I'm reading a long block of content, I'll often click the scroll thumb and keep it clicked, using either the mouse or trackpad (or trackball, for that matter) to seek proportionally through the page. You don't get that proportionality of motion with either the mouse wheel or the two-finger trackpad gestures which mimic it.
The "most people" argument you're making is what leads to broken ideas like infinite scrolling, which appeals to one subset of the population who assume that everyone else uses their UI in precisely the same way that they do.