overflow:scroll doesn't work with Gfx scrollbars

RESOLVED INCOMPLETE

Status

()

Core
Layout: Form Controls
P4
critical
RESOLVED INCOMPLETE
18 years ago
11 years ago

People

(Reporter: rods (gone), Assigned: kinmoz)

Tracking

({helpwanted, regression})

Trunk
Future
x86
Windows NT
helpwanted, regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3-])

(Reporter)

Description

18 years ago
There are actually two problems
1) the style rule for textarea in html.css should have "overflow:scroll" so the 
textarea always has scrollbars.

2) When in Gfx mode "overflow:scroll" doesn't create the scrollbars, with native 
scrollbars it does.

One reason might be that the GfxTextControlFrame calls 
sv->SetScrollPreference(scrollPref) where scrollPref is equal to 
"nsScrollPreference_kAlwaysScroll"

The call is really a call to:
nsIScrollableView::SetScrollPreference
which is really a call to:
nsScrollPortView::SetScrollPreference
which doesn't do anything, it just returns

My guess is this is an evaughan bug, but starting out in editor land.
(Reporter)

Comment 1

18 years ago
nominating for nsbeta2, because the textarea has to have scrollbars even when 
there is nothing to scroll. making it a regression because it worked with native 
scrollbars
Keywords: nsbeta2, regression

Comment 2

18 years ago
asking Simon to give this a quick look to see if it is ours or whether it should 
move over to Erik
Assignee: beppe → sfraser

Comment 3

18 years ago
kin: you're the input scroll bar dude, can you take a look at this? Thanks!

Comment 4

18 years ago
Reassign duh
Assignee: sfraser → kin
(Assignee)

Comment 5

18 years ago
Accepting bug.
Status: NEW → ASSIGNED
Target Milestone: --- → M17

Comment 6

18 years ago
[nsbeta2-] will reconsider if there is a specific scenario that is bad enough.
Whiteboard: [nsbeta2-]

Comment 7

18 years ago
updated priority and severity
Priority: P3 → P1

Comment 8

18 years ago
textareas should have visible vertical and horizontal scrollbars regardless if 
they content or not.
Keywords: nsbeta2 → correctness, nsbeta3
Whiteboard: [nsbeta2-]
Target Milestone: M17 → M18

Comment 9

18 years ago
setting to nsbeta3+
Whiteboard: nsbeta3+

Comment 10

18 years ago
setting priority in status whiteboard
Priority: P1 → P4
Whiteboard: nsbeta3+ → [nsbeta3+][p:4]

Comment 11

18 years ago
due to the timeframe and the number of issues that need to be addressed, marking 
this as minus, setting to future and adding helpwanted
Keywords: helpwanted
Whiteboard: [nsbeta3+][p:4] → [nsbeta3-]
Target Milestone: M18 → Future

Comment 12

17 years ago
Updating QA contact.
QA Contact: ckritzer → bsharma

Comment 13

17 years ago
QA Contact Update
QA Contact: bsharma → vladimire

Comment 14

16 years ago
removing myself from the cc list

Updated

16 years ago
QA Contact: vladimire → tpreston

Comment 15

12 years ago
Is this still an issue?
The code referenced is obsolete, and it's not clear what the bug was really about.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.