9 ms·
Number three is interesting, especially if we consider what Canonical have done recently with Unity and moved scrollbars outside the window[1], freeing-up the s
by beaumartinez 16y ago
Number three is interesting, especially if we consider what Canonical have done recently with Unity and moved scrollbars outside the window[1], freeing-up the screen real-estate that they permanently occupy.
[1] http://design.canonical.com/2011/03/introducing-overlay-scrollbars-in-unity/ http://design.canonical.com/2011/03/introducing-overlay-scro...
- ryanf 16y agoIt's interesting how reminiscent that design is of Google Wave's much-criticized scrollbars: the position indicator following the thumb, the page-up/page-down buttons, and the minimalist appearance when not in use. I wonder if Wave's design was just ahead of its time.
- cnkt 16y agoWave itself was ahead of it's time. i was using it very much.
- Stuk 16y agoI think the problem most people had with Wave's scrollbars is that they didn't indicate the height/length of the document very well. The Canonical design above has solved this by retaining the visual indicator.
- ugh 16y agoI think that the problem with Wave's scrollbars wasn't so much that they were bad, they were non-standard. Scrollbars are OS territory, individual webapps should probably not try to reinvent them. (I would argue that they should only ever try to reinvent them when they provide something substantially better and when the standard OS implementation is lacking.)
- jacobolus 16y agoMy problem with wave’s scrollbars was that whatever code they had to do scrolling was dramatically slower and glitchier than native scrollbars.
- mcav 16y agoAnd OS X Lion's new "hidden" scrollbars.