… people keep nagging about making fonts resizable (em or %) for the benefit of the elderly… well my grandma has trouble accurately clicking the scrollbars… I wanna make the scrollbars FAT and CHUNKY… DO IT FOR MY GRANDMAAAAA!!!! (and the 4-year-olds!)

Under Windows you can change the thickness of scrollbars system-wide by going to Display Properties -> Appearance -> Advanced -> Scrollbar. Change the size to whatever you want. I imagine you can do something similar under Mac.

That’s the correct way to adjust these things. If the user has a problem with scrollbars, they’ll have problems *everywhere*, and the OS should correct it. “Fixing” is on a single site doesn’t really help anyone, and is actively bad for people with normal eyesight and motor skills.

That depends entirely on the website! For example if you have a black website, say a photo gallery, and want scroll bars embedded in the middle of the page (not part of the window chrome), then you should have dark coloured scroll bars. White and candy blue will clash horribly and distract from the content on the page.

For example, MobileMe uses black scroll bars in it’s photo gallery. They’re using javascript, and so don’t function as other scroll bars do. This commit can be used to fix that problem.

For the record, my languages in the International preference pane are set to English, French, German, yet only en-us is sent in the Accept-Language header. It means that on most web sites designed for Switzerland that are available in German, French and Italian, the server, seeing it (seemingly) can’t provide any of my preferred language(s), default to German. With a proper header (e.g. en,fr;q=0.7,de;q=0.3), it would serve me French content.

I’m pretty sure it’s not the right place to report this, but hey, I also sent it using the ad hoc Safari menu command, several times is the past few years.

The HTML 4 standard explicitly leaves it up to the UA how to style form elements; the application of CSS attributes to these elements is left undefined. Until there’s a definite standard used by the majority of browsers for rendering form elements, I’m not sure it’s wise to incorporate CSS styles for these form elements. Styling these with the UA-proprietary prefix is just admitting that there’s no real merit to this addition.

In addition to that, the most noticeable things about the example are that a) you have to wait for your scroll bar elements to load before you can interact with the page properly (providing nostalgic flashbacks to the web of a decade ago), and b) the vertical scroll bars consistently fail to display properly (in Safari 4/5528.16 and WebKit r41944 under OS X).

Don’t get me wrong, this is very “cool”, but should never be used in an sensible design ever.