usechromesheet attribute for all widget scrollbars

NEW
Unassigned

Status

()

Core
XUL
--
enhancement
17 years ago
8 years ago

People

(Reporter: rvj, Unassigned)

Tracking

Trunk
x86
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The current chrome/skin philosophy assumes only one style of scrollbar is to be 
applied to all widgets. This is VERY restrictive. 

Having spent the best part of a month trying to style widget scrollbars, would 
it be possible to add a new usechromesheet attribute to all widgets which would 
point to the appropriate scrollbars.css.  (replacing chrome scrollbars.css)

Attempts to clone new tree elements and/or modify the existing tree binding to 
include a usechromesheet reference are all unsuccessful. 

Adding a  usechromeshet option provides maximum flexibility. Something like

<tree usechromesheet="chrome://xyz/scrollbars1.css"  src="..." />
<tree usechromesheet="chrome://xyz/scrollbars2.css"  src="..."/>

This should overcome the problem of overriding inherited scrollbars of the 
current chrome which was raised in one of the newsgroup posts


PS Ive almost prototyped an xbl binding for iframe which permits this. 
unfortunately Ive been unable to get usechromesheets to work with other XUL 
widgets. 

<iframe usechromesheet="chrome://xyz/scrollbars3.css"  src="..."/>
(Reporter)

Comment 1

17 years ago
PS If this attribute is missing, then chrome://global/skin/scrollbars.css is 
assumed.

But equally it could be implied using the directory shortcut

<iframe usechromesheet="chrome://global/skin" src="..." />
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

17 years ago
Target Milestone: --- → Future

Comment 2

16 years ago
--> default owner.
QA Contact: jrgm → shrir
Target Milestone: Future → ---

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets

Updated

8 years ago
Assignee: hyatt → nobody
You need to log in before you can comment on or make changes to this bug.