Closed Bug 176278 Opened 22 years ago Closed 12 years ago

classic: can't use scrollwheel at left edge of screen

Categories

(SeaMonkey :: Themes, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: classic)

In Mozilla 10/17 with a maximized window using the classic skin, I can't use the
scroll wheel at the left edge of the screen.  Wheel scrolling at the left edge
of the screen works in IE (even though IE has a similar-looking left border for
the content area) and it works in Mozilla with the modern skin.  I turned off
the sidebar rather than collapsing it, so this is not a dup of bug 44618.

This also happens in Phoenix 10/22 with the default Phoenix skin.
*** Bug 182826 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 143038 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
This doesn't look like a dup of bug 143038 to me.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Product: Core → SeaMonkey
Assignee: shliang → nobody
Status: REOPENED → NEW
Keywords: classic
QA Contact: pmac → themes
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
I can reproduce this bug on the latest-comm-central-trunk build.

The lest side of the maximized window has border. So, the cursor isn't on the content area when I moved cursor to the left most point of screen.

I recommend that SeaMonkey theme should remove the border if it's not needed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
> I recommend that SeaMonkey theme should remove the border if it's not needed.
The border appears to be gone. And scrolling with the scrollwheel at the left margin works. => WFM

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 SeaMonkey/2.14a1
Build identifier: 20120814163219
Status: NEW → RESOLVED
Closed: 20 years ago12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.