Open Bug 72127 Opened 24 years ago Updated 2 years ago

vertical scrollbars disappear when row=1 and horizontal scrollbars are present

Categories

(Core :: Layout: Form Controls, defect)

All
Windows 98
defect

Tracking

()

Future

People

(Reporter: rubydoo123, Unassigned)

Details

during the course of debugging bug 72101, Kin and I found this problem: If you specify "style: scroll" then the vertical scrollbar never appears if row=1, if you specify "style: auto", then the vertical scrollbar only disappears if the horz scrollbar appears. Whenever there is a horz scrollbar and row=1 the vertical scrollbar disappears, bottomline it really doesn't matter what the overflow is set to, if the other conditions are met, the scrollbar disappears.
row=1? is this a tree control? If it is its Hyatts baby.
Assignee: evaughan → hyatt
It is referring to an HTML <textarea>, per bug 72101, not to a tree widget. I don't really follow the explanation of this bug, though. Aren't scrollbars intended to disappear when there is not enough vertical space in which to render them? (Or maybe I should say, in the current implementation that is the behaviour; I suppose there could be a way to do it so that "something" is shown (e.g., scaling the scrollbarbuttons down when the required space is not sufficient to draw them at full height).
This is an RFE for flex depth essentially. You want scrollbars to shrink to a miniscule size while losing the thumb area. This is a dup of one of my other futured bugs. Futuring.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Summary: vertical scrollbars disappear when row=1 and horizontal srollbars are present → vertical scrollbars disappear when row=1 and horizontal scrollbars are present
QA Contact: vladimire → layout.form-controls
Assignee: hyatt → nobody
This is a mass change. Every comment has "assigned-to-new" in it. I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.