Re:“We would be willing to set up a $2,500 bounty to impleme...
by regularfry on Tuesday April 07, 2015 @05:31AM
(#9332771)
Of the two, 1) is the less bad option. This seems obvious to me. It is wrong to treat the scroll bar as only visual element and not an input element; that's what I take issue with.
> 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.
Re:“We would be willing to set up a $2,500 bounty to impleme...
by TheLoneWolfling on Monday April 06, 2015 @04:45PM
(#9330593)
3) Overriding the removal of the default scrollbar so I can actually use a scrollbar that works.
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.