Code review comment for lp:~cimi/overlay-scrollbar/fix-771450

On Fri, 2011-06-10 at 15:29 +0000, Christian Giordano wrote:
> 1) what happens when the thumb is not external?

Then it will overlap content above and below. I don't see an issue
there that is worse than the thumb being not external in the first
place. If it's not external it's going to obscure content, it's just a
matter of what content.

> 2) shouldn't we promote good UX placing some limits? Scrolling
> content in a tiny area is likely to be a very unpleasant (far
> from usable) experience. Maybe we can take into consideration
> how much scroll is available, and show the thumb only when it
> is manageable (small difference from visible area and all
> scrollable area)?

I think we should, but we can't get to the point where it's *impossible*
to have it work in those situations. We can't make the data
unavailable. We can make it look ugly, not ideal, and generally
discourage people from doing it. But, making it so that the data is
unavailable breaks the program, perhaps in a significant way.

In my experience many of the times this happens isn't because of the
primary design of the application. Usually one or two entries is
enough. But someone makes a plugin or extension that adds a bunch of
entries, and that creates the issue.