Closed Bug 21899 Opened 26 years ago Closed 4 years ago

Issues with GFX scrollbars and CSS

Categories

(Core :: XUL, defect, P3)

x86
Windows 98
defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: ian, Unassigned)

Details

(Keywords: css-moz, Whiteboard: (py8ieh:break this one into bits))

There are some issues with the CSS support of GFX scrollbars. * <scrollbar> doesn't appear to support 'margin'. * <scrollbar> doesn't appear to have a clear way of setting its size (e.g. using 'height' or 'width'). If it did, then its children could use percentage sizes which would make much more sense. * <scrollbar> doesn't take 'padding' into account when working out its width/height. For example, stick: scrollbar { padding: 20px; } ...into xul.css and the scrollbars will stick out of the bottom of your windows when you restart Mozilla. (THIS IS DEFINITELY A BUG!) * thumb doesn't appear to support 'height' or 'width' either. * etc. There does not appear to be a spec anywhere saying what we can expect scrollbars to support, style-wise. Nor could I find a relevant bug. If any of these issues are already covered somewhere or are known deficiencies for which there is no plan to ever provide support, then that's fine... but it should be documented somewhere! :-)
Assignee: trudelle → evaughan
Whiteboard: needs evaughan triage
One problem per bug report please! The others should be broken into separate bugs so we can fix, track, close, test, etc. independently. assigning to evaughan for triage.
Status: NEW → ASSIGNED
Target Milestone: M14
Keywords: css-moz
Target Milestone: M14 → M15
evaughan: Assuming that "triage" means "break this bug into little bits", I would be happy to do it. If that would help you, feel free to reassign the bug to me. Cheers!
Whiteboard: needs evaughan triage
Summary: {css-moz} Issues with GFX scrollbars and CSS → Issues with GFX scrollbars and CSS
Triage has the usual medical meaning, just think of software defects as wounds. It would certainly help to break this into separate bug reports, but you don't need this one assigned to you in order to do it.
Rightio. I'll put it on my radar... and look into it once I have a free second. Not before the end of the week, I expect.
Whiteboard: (py8ieh:break this one into bits)
All these issure are fixed in my tree.
Target Milestone: M15 → M16
Target Milestone: M16 → M17
Mass moving M17 bugs to M18
Target Milestone: M17 → M18
spam, open xptoolkit qa contact moving over to jrgm
QA Contact: paulmac → jrgm
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
(per trudelle). mass-moving all evaughan non-nsbeta3+ bugs to 'Future' milestone
Target Milestone: M21 → Future
Comment #2 talks about "break this bug into little bits", any progress with this? Close this bug and create 4 new ones?

I'm guessing this is too old to still be useful, and/or invalid/incomplete

The bug assignee didn't login in Bugzilla in the last 7 months.
:enndeakin, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: eric → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(enndeakin)

I don't think we need to support scrollbars outside the context of scrollable areas. Instead if a usecase arises, we should file a bug for that with a testcase.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(enndeakin)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.