W3C home > Mailing lists > Public > www-style@w3.org > November 2003

[www-style] <none>

From: Dris <dris86@cox.net>
Date: Wed, 19 Nov 2003 17:36:07 -0600
Message-Id: <2601B43B-1AE9-11D8-B559-000A95A18252@cox.net>
To: www-style@w3.org
On Nov 18, 2003, at 10:58 AM, Henri Sivonen wrote:

>> Also, I wasn't assuming they all look like Windows scrollbars (note 
>> my reference to different user agents and widget differences).  I'm 
>> using Mac OS X, and that's what I was modeling it after.
>
> The OS X scrollbars are very difficult to imitate if the browser 
> assumes that the scrollbars are Windows-like. In particular, the 
> extreme positions of the slider are hard. Mozilla tried to mimic the 
> OS X scrollbars using boxed images, but it didn't work out. 
> Thankfully, native scrollbars are used now.

Actually, looking at theme files for Mac OS X and the like, scrollbars 
are made up of around six (maybe a few more, such as for the 
transparent effect on the grip tab) images for each direction (vertical 
and horizontal).

> Also, suppressing system scrollbars causes all sorts of annoying 
> issues with mouse wheels and assistive technologies.

I would hope that UA's would use the system's input API to make the 
scrollbars just as functional.

>
>> A few other suggestions:
>> y-scrollbar-arrow-orientation: top || bottom || both;
>> y-scrollbar-tab-proportion: proportional || fixed;
>
> I prefer to keep those settings to my system-wide preferences without 
> every Web author altering them.

And thus, you have the beauty of overriding CSS with a custom file.  Of 
course, a designer could set these to "default" to automatically pass 
the user's system preference.
________
"Irony is a voluntary survey with required fields."
	~ Dris ~
Received on Wednesday, 19 November 2003 18:36:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:25 GMT