Closed Bug 158449 Opened 22 years ago Closed 19 years ago

Click and Drag from Text Area inactivates Scrollbars

Categories

(Core :: DOM: Editor, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mozilla, Assigned: kinmoz)

References

Details

Load any page with a text area and that is long enough to need to scroll. Click
in the text area and drag down till the page scrolls to the bottom. Now try to
use the scrollbars. Reload doesn't help.

Mozilla 20020718 trunk
worksforme win2k 7/18 trunk for a testcase based on description above.
maybe I need more detail (or a specific testcase) or maybe it's an winxp
thing.
All that is required is to click into a textarea (and don't let up) and drag the
mouse to the bottom of the Mozilla window. The window will begin scrolling, and
once the textarea goes off the top of the page you lose all mouse control. You
can't stop the scrolling, and the scrollbars don't work.
Right. It was the "once the textarea goes off the top of the page" that I was
missing, since the testcase I set up, while scrolling to the bottom, did not
move the textarea offscreen.

Yep. Goes whacky, win2k 7/18 trunk.

However, I was able to recover with reload, or by hitting Esc and clicking 
above the scrollbar thumb. Still, it's broken (workaround or not).
bug confirmed - 2002071904/win98se
I see this on Linux too, build 2002061808.
This should be under Editor: Core, I think.
Assignee: jaggernaut → kin
Component: XP Toolkit/Widgets → Editor: Core
QA Contact: jrgm → sujay
A better workaround is to use the "arrow up" or "PageUp" key to scroll up until
you see the textarea again.
*** Bug 192079 has been marked as a duplicate of this bug. ***
*** Bug 193289 has been marked as a duplicate of this bug. ***
OS: Windows XP → All
Hardware: PC → All
Blocks: 67277
Is this still an issue?
I think this is fixed for quite some time. I'm marking this WFM. If someone can
still reproduce this, then please reopen.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.