Closed
Bug 130948
Opened 24 years ago
Closed 23 years ago
no scrollbar slider appears on this page
Categories
(SeaMonkey :: UI Design, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
mozilla1.2alpha
People
(Reporter: andreww, Assigned: jag+mozilla)
References
(Depends on 1 open bug, )
Details
Attachments
(1 file)
|
52.16 KB,
image/png
|
Details |
Using mac trunk build from the 13th.
Loading this page results in a page that needs a scrollbar, but there is no
slider inside it to move up and down.
major UI issue - if the user cannot use the scrollbar properly.
Comment 2•24 years ago
|
||
worksforme on linux, this morning's build. Mac-only?
Comment 3•24 years ago
|
||
Works for me, 2002031403 on WInXP.
Comment 4•24 years ago
|
||
wfm win2k too. ->jag Is this the only such page? Could it be a boundary case?
Do other scroll methods work (spacebar, arrow keys, pgUp/pgDn)?
Summary: no scrollbar appears on this page → no scrollbar slider appears on this page
Comment 7•24 years ago
|
||
WFM using NS 2002032513 build for MacOS X. I still need to know if the page is
scrollable using other means, and if this is seen on any other pages.
Interestingly enough, I don't get a scrollbar when viewing the attached screenshot.
Assignee: trudelle → jaggernaut
Some more information:
This only happens when mac's "smart scrolling" is turned off.
This does happen on more than one page. I can see this happening
consistently on another page which has a frameset.
You _can_ scroll the page by using the arrows, or by holdingdown the
mouse inside the scrolling "tray" area. But you cannot drag anything
around to scroll up and down.
| Reporter | ||
Comment 10•24 years ago
|
||
here is the other bug that is related:
http://bugzilla.mozilla.org/show_bug.cgi?id=123741
Comment 11•24 years ago
|
||
nsbeta1- per Nav triage team.
Comment 13•23 years ago
|
||
WFM 20030306 OSX. Mozilla CFM/Classic build is dead.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•