Closed
Bug 22512
Opened 25 years ago
Closed 25 years ago
Clicking just below scrollbar thumb moves thumb to bottom.
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: masri, Assigned: eric)
References
Details
(Whiteboard: [PDT+] 2/04/00 fixed awainting checking)
Build ID: 1999122111 (M12)
Platform: Macintosh PowerBook G3/300 (1024x768
display), MacOS 9, 128Mb RAM, VM off. (How long do we have to wait to get MacOS
9 added to the list of OSes on the bug submission form? Who handles this??)
Scroll bar jumping!
Here's one for you. Go to:
http://www.mozilla.org/status/
Expand the Moz browser window to full screen by clicking the grow box. First,
move your mouse approx. half way down the gray scroll bar, and click once. As
expected, the screen jumps down 1 screenful of text, and the scroll box moves
down (as expected) a small amount, showing you approximately where you are in
the document.
Now, position your mouse underneath the scroll box, approx. half
the length of the scroll box. (In other words, a little bit under the scroll box
in the gray scroll bar). Click, and make sure to leave the mouse where it was,
pointing at the gray scrollbar. The scroll box jumps all the way down the page!
This will continue to happen until you move the mouse outside the gray
scrollbar. When the scrollbar makes its way to the bottom, you can make it jump
back up to the top by reversing the process.
Caffinated scrollbar!
Ok, here's
another fun scroll bar bug. Go to this page.
http://www.mozilla.org/status/
Once again, expand your window to fullscreen by clicking the scrollbox. (Note,
I'm on a 1024x768 display.) Move your mouse to the gray area in the scrollbar
under the scrollbox, and click once. The scrollbox has moved to the bottom of
the scrollbar, and you're at the end of the document, right? DO NOT move the
mouse away from the scrollbox!
Ok. Grab the scrollbox, and try dragging it up.
See it jump back and forth between its new position and the originating position
(bottom)?
- Adam
Updated•25 years ago
|
Assignee: shuang → pinkerton
Component: UE/UI → XP Toolkit/Widgets
Comment 1•25 years ago
|
||
Hey, Mike ---
Thought you'd know who should get this, per our prior chat.
Comment 2•25 years ago
|
||
is this mac only?
Comment 3•25 years ago
|
||
Mike &&/|| Adam, do you think this is a dupe of 20476?
Updated•25 years ago
|
Summary: Mac: Browser scroll bar lunacy → [dogfood][beta] Mac: Browser scroll bar lunacy
Whiteboard: Need to know if this is XP!
Target Milestone: M14
Comment 4•25 years ago
|
||
M14, this needs to be fixed for beta. I don't think this is a dupe of 20476, but
it's probably related in some way. If this is XP, i'll give it to evaughan, but
will keep if mac only.
Whiteboard: Need to know if this is XP! → [PDT+] Need to know if this is XP!
Reporter | ||
Comment 6•25 years ago
|
||
re: 20476
It looks like only the first half of my report ("jumping") is a dupe of that bug.
The second half ("caffinated") is completely different.
- Adam
Updated•25 years ago
|
Assignee: pinkerton → evaughan
OS: Mac System 8.6 → All
Hardware: Macintosh → All
Whiteboard: [PDT+] Need to know if this is XP! → [PDT+]
Comment 7•25 years ago
|
||
Happens on both mac and linux. Cannot repro on win32, however. Reassigning to
evaughan.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14 → M13
Updated•25 years ago
|
Priority: P3 → P1
Comment 8•25 years ago
|
||
bumping priority to p1 due to PDT+ status.
Updated•25 years ago
|
QA Contact: elig → claudius
Updated•25 years ago
|
Target Milestone: M13 → M14
Comment 10•25 years ago
|
||
moving to m14, despite PDT+ status, since there is no crash, data loss, or leak,
and it isn't blocking anyone. Come to think of it, why is this PDT+?
Updated•25 years ago
|
Whiteboard: [PDT+]
Comment 11•25 years ago
|
||
Per request by Trudelle for reconsideration of PDT status, I've deleted the + on
the status whiteboard, and we'll reconsider at our next PDT meeting.
The claim to get PDT+ dogfood status would be that it makes use of the Mac
client impossible to use because you can't scroll around. IF indeed you can
view content and scroll around reasonably, and/or the alternate mechanism is
pretty discoverable, then this should not be a PDT+ bug (although it sure should
get fixed for our beta).
Comments? Work around? Ease of work-around?
Thanks,
Jim
Comment 12•25 years ago
|
||
Blocking work. Putting on Blocker severity. A PDT+ for Gecko team. List boxes
and view system held up until this is working. Putting on PDT+ radar.
Assignee | ||
Comment 13•25 years ago
|
||
Hmmm.. Every mac person I talked to said they had no problems with this bug. To
create it you have to intentionally click in the space between the thumb and the
down or up arrow. If you don't this never happens. The work around is just to
hit page down or up. BTW this does not crash or prevent the user from scrolling.
Comment 14•25 years ago
|
||
Jan: Blocking who on what list box/view system work? Why haven't the engineers
who are blocked commented in this bug? Why are there no bugs listed as depending
on this? Why are there zero votes for this bug? Is PDT now the court of first
resort?
Comment 15•25 years ago
|
||
However, due to the focus problems, pressing "Page Up" or "Page Down" frequently
doesn't work without clicking in the URL bar and back.
This may not be a PDT blocker, but this absolutely should be fixed by beta. This
happens to me at least once every hour of usage, and requires a full browser
restart.
Assignee | ||
Updated•25 years ago
|
Whiteboard: [PDT+] → [PDT+] 1/28/00
Comment 16•25 years ago
|
||
That sounds like a separate bug. This is only concerned with clicking in the
gray area under the scrollbar thumb. In fact, it is only a problem when you
click within one thumb-length of the thumb. It seems like a boundary case that
is being handled improperly, resulting in repeated hops of the thumb. There is
no crash, no need to restart anything, there are ample workarounds, and I still
haven't heard how this bug could possibly be blocking anyone from anything.
If I'm just missing something here, please let me know exactly what!
Removing vestigial tags and rewriting summary to reflect reality. Setting
Priority P3.
Comment 17•25 years ago
|
||
Keep in mind that a lot of dogfood work involves using pages that have a scroll
region that is only twice the height of the scroll bar. I've encountered this on
every bug I've been trying to use within Seamonkey recently.
(This problem is annoying enough that I'll probably stop using Seamonkey for my
Bugzilla work until it's fixed in M14 unless the focus problems that required
voodoo to use keyboard shortcuts are fixed.)
Comment 18•25 years ago
|
||
*** Bug 24813 has been marked as a duplicate of this bug. ***
Comment 19•25 years ago
|
||
*** Bug 24710 has been marked as a duplicate of this bug. ***
Comment 20•25 years ago
|
||
This bug describes more than one defect. Just copied second problem into new
bug 25012.
Keywords: beta1
Comment 21•25 years ago
|
||
*** Bug 25411 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 22•25 years ago
|
||
*** Bug 25012 has been marked as a duplicate of this bug. ***
Comment 23•25 years ago
|
||
*** Bug 25516 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•25 years ago
|
Whiteboard: [PDT+] 1/28/00 → [PDT+] 2/04/00 posible fix testing.
Comment 24•25 years ago
|
||
*** Bug 21531 has been marked as a duplicate of this bug. ***
Comment 25•25 years ago
|
||
*** Bug 26739 has been marked as a duplicate of this bug. ***
Comment 26•25 years ago
|
||
In bug 26739 the user actually filed a report that they liked the jump to the
bottom behaviour:
"I like this feature. I don't know how to file a "keep this bug" bugreport,
but keep this unusual behavior around, or make a formal TopOfPage (BottomOfPage
accelerator)". However, since this request is for something which is being fixed
in this bug, I have marked a dup and added a comment here.
Reporter | ||
Comment 27•25 years ago
|
||
LOL! They like this behavior? And here I thought it was totally psychotic.
- Adam
Comment 28•25 years ago
|
||
A top/bottom accelerator already exists (at least on my linux build). Just
click and hold down the mouse button on the scroll bar above/below the thumb,
and the page will scroll all the way to the top/bottom of the page. It isn't
necessary to keep this annoying bug around to have that feature.
I would never encounter this bug if scrolling via the keyboard consistently
worked, but since it doesn't I hit this bug all the time and it makes it
frustrating to browse the web with Mozilla. I'm glad to hear it's on the radar
to be fixed sooner rather than later.
Comment 29•25 years ago
|
||
myk wrote:
"Just click and hold down the mouse button on the scroll bar above/below the thumb,
and the page will scroll all the way to the top/bottom of the page."
that's a bug too...
Comment 30•25 years ago
|
||
claudius wrote:
"that's a bug too..."
If that other bug is fixed I'll put in an RFE to reinstate it. It's a very
useful way of getting to the top or bottom of a page or just scrolling up and
down as much as you want without having to grab the thumb or move your cursor
from whereever it is on the scrollbar.
That "bug" is a feature in Motif (or Lesstif anyway) and exists in my copy of
NS4.7. In fact I just used it to get to the bottom of this long bug page so I
could grab your message to quote it above.
Reporter | ||
Comment 31•25 years ago
|
||
Claudius,
It's not exactly a bug for the reason you outline. Please see
http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-121.html#HEADING121-34
Behavior on Mac (and I'm assuming wanted behavior on all platforms) is that a
click-hold in the gray area of a scroll bar moves the scroll bar to the bottom
of the page, or the location of the arrow, whichever comes first. I have spawned
bug 26914 to deal with that issue separately.
- Adam
Comment 32•25 years ago
|
||
*** Bug 26913 has been marked as a duplicate of this bug. ***
Comment 33•25 years ago
|
||
*** Bug 26914 has been marked as a duplicate of this bug. ***
Comment 34•25 years ago
|
||
QA,please note that the resolved duplicate bug 26914 describes a related case
that should be tested before verifying this bug. In the unlikely event that a
satisfactory fix for this bug doesn't fix 26914, then please reopen 26914.
Comment 35•25 years ago
|
||
*** Bug 26953 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 36•25 years ago
|
||
This is now fixed. Just need to test on all platforms and check in.
Whiteboard: [PDT+] 2/04/00 posible fix testing. → [PDT+] 2/04/00 fixed awainting checking
Assignee | ||
Comment 37•25 years ago
|
||
Fixed.
Assignee | ||
Comment 38•25 years ago
|
||
closing out
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 39•25 years ago
|
||
VERIFIED fixed on all platforms with the 2000021510 builds. and yes, it fixed bug 26914 as well
Status: RESOLVED → VERIFIED
Comment 40•25 years ago
|
||
*** Bug 30416 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•