Closed
Bug 229054
Opened 21 years ago
Closed 21 years ago
Scrollbar customization
Categories
(Firefox :: General, enhancement)
Firefox
General
Tracking
()
VERIFIED
DUPLICATE
of bug 178651
People
(Reporter: dwightb, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Copied from similar entry for Browser (Seamonkey).
Firebird should support changing the color/style of the scrollbars (esp. for
overflow: auto; divs and textareas), similar to IE and Konquerer using
moz-specific CSS.
Personally I see this area as an opportunity for Mozilla to, yet again, surpass
IE in developer and end-user features.
Let's face it, better browsers and more features largely benefit web developers
first and foremost. I am able to create a similar web site on browsers from NS4
to IE6, but NS4 is a developer nightmare. Mozilla has no exceeded IE in
supporting developers and is why I now use it as my primary browser and
development platform.
The issue of scrollbar 'skinning' is important to a web designer because it
detracts from the ability we have from creating designs that are consistent
throughout. As has been said previously it is not so important that the primary
browser scrollbars be skinned but rather on those the exist within a page,
whether that be a textarea or a div with overflow:auto;
The arguement that it ruins a consistent user interface is irrelevent since we
all know styles can be changed completely on nearly all form elements (minus
some annoynaces with select elements). As well as the fact that Mozilla can be
skinned (including scrollbars) and the default 'Modern' skin does not match that
of any OS.
I propose a much more detailed approach by treating scrollbars as elements
within CSS as follows:
-moz-scrollbar-track {
width:
border:
background:
}
-moz-scrollbar-face {
width:
border:
background:
}
-moz-scrollbar-arrow {
width:
height:
border:
background:
}
Those are what I would consider the primary attributes of the elements and allow
for not only changing the colors of the elements but also the ability to use
images as a background as well.
------- Additional Comment #79 From Dwight Brown 2003-12-15 09:02 -------
After my initial proposal I gave the concept more thought and think inherency
would be needed and that this may be a more proper solution:
-moz-scrollbar {
-moz-scrollbar-width:
-moz-scrollbar-border:
-moz-scrollbar-background:
-moz-scrollbar-face-border:
-moz-scrollbar-face-background:
-moz-scrollbar-track-border:
-moz-scrollbar-track-background:
-moz-scrollbar-arrow-border:
-moz-scrollbar-arrow-color:
-moz-scrollbar-arrow-background:
}
The -moz-scrollbar attributes would be inherited by the other optional specific
attributes. -moz-scrollbar-arrow-color: would define the arrow color and if set
to "transparent" would allow for developers to use the background attribute to
create their own.
For example:
-moz-scrollbar {
-moz-scrollbar-width: 0.15in;
-moz-scrollbar-border: 1px solid black;
-moz-scrollbar-background-color: white
-moz-scrollbar-track-background-color: silver;
-moz-scrollbar-arrow-background-color: silver;
-moz-scrollbar-arrow-color: blue;
}
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•21 years ago
|
||
Bug 178651 was reported for this issue in Firebird, it was solved as WONTFIX.
Comment 2•21 years ago
|
||
Forgot to say, Opera 7 also has this feature, not enabled by default though.
Comment 3•21 years ago
|
||
Browser specific CSS elements (such as -moz CSS stuff) is not valid according to
the w3c spec. Duping.
*** This bug has been marked as a duplicate of 178651 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Comment 4•21 years ago
|
||
Nosebleed, there is a lot of stuff in Mozilla that has been added that are not
in the specs (like innerHTML, scrollHeight/Width etc). Dismissing this bug
report only for this reason is not good enough. I can buy that its annoying or
whatever, but this reason is not enough.
You need to log in
before you can comment on or make changes to this bug.
Description
•