- From: Dris <dris86@cox.net>
- Date: Mon, 17 Nov 2003 18:44:12 -0600
- To: www-style@w3.org
On Nov 17, 2003, at 5:55 PM, Boris Zbarsky wrote: > Dris wrote: >> y-scrollbar-slide-top: url(image); >> y-scrollbar-slide-center: url(image); /* This would essentially >> repeat-y */ >> y-scrollbar-slide-bottom: url(image); > > And if the scrollbar slider has more than three parts? And if the > middle part is NOT supposed to repeat (eg scrollbars that have a > grippy-like image at the center and just plain stuff otherwise)? Well, "slide" was referred to the region in which the "slider" slides. I used the term "tab" for "slider". Pick your own words. As far as the center grippy-image thing, that would in fact be good. So we could allow you to repeat-y, center, left, and everything else that applies to CSS background. Better yet, doesn't CSS3 have some support for multiple backgrounds layered on top of each other? If so, we could just cut it down to this: y-scrollbar-slide: url(image) whatever; >> y-scrollbar-arrow-top: url(image); >> y-scrollbar-arrow-bottom: url(image); > > And if there are no arrows? Indeed. From what I've seen, some browsers display widgets on web pages much differently than throughout the OS interface. One example is Mozilla. Another is Internet Explorer (when the widgets are styled). Couldn't other browsers do the same? This is why I'm not suggesting that this be applied to viewport scrollbars, as they aren't really part of the page (unless you consider html { overflow: auto; } or something). Even then, perhaps user agents should consider the viewport to be <html>, with no scrollbars rendered automatically unless the CSS overflow property says so. I'm not sure about all the workings of the spec in that area, so I may be way off base. >> y-scrollbar-tab-top: url(image); >> y-scrollbar-tab-center: url(image); /* Just like >> y-scrollbar-slide */ >> y-scrollbar-tab-bottom: url(image); > > I'm not even sure what part of the scrollbar this refers to. This refers to the grip tab ("slider", as you called it before). Everything I said about the "slide" above would apply to this as well. > Basically, this proposal, like all the preceding ones that have been > posted in this thread, assumes all scrollbars look like Windows > scrollbars. They don't. Well, I did say feel free to tear it apart. Whatever the case I think CSS should have a way to do this. I wasn't suggesting that my example was adequate, or even well thought-out. If you don't like it, suggest something new. 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. A few other suggestions: y-scrollbar-arrow-orientation: top || bottom || both; y-scrollbar-tab-proportion: proportional || fixed; This isn't just about scrollbars though... What about checkbox-checked and other widgets? Since XHTML 2.0 is moving to XFORMs or whatnot, it would have to take that into consideration as well. Again, I'm not claiming to know all the answers. Just putting forth a suggestions for people who know what they're talking about to consider. ________ "Irony is a voluntary survey with required fields." ~ Dris ~
Received on Monday, 17 November 2003 19:44:05 UTC