Closed Bug 268568 Opened 20 years ago Closed 20 years ago

Mouse pointer does not change after clicking to show large image at the original size

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 20022

People

(Reporter: ian, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When navigating to a large image file (one too large to fit in the current
window) Firefox resizes the image to fit in the window and changes the mouse
pointer to a magnifying glass with a '+' in it.

However, when you then click the image to view at the original size the mouse
pointer does not immediately change to the corresponding image with a '-' inside
the magnifying glass. It is necessary to move the mouse pointer before it changes.

Reproducible: Always
Steps to Reproduce:
1. Navigate to a large .jpg file (one too large to fit in the current window)
and place the mouse pointer over the image.
2. Observe the mouse pointer is a magnifying glass with a '+' in it
3. WITHOUT MOVING THE MOUSE click on the image.
Actual Results:  
The image resizes to the original size but *the same mouse pointer remains*
until you move the mouse.

Expected Results:  
The pointer should change immediately upon clicking on the image - it should not
be necessary to move the mouse pointer.
Another variant of bug 20022/bug 50511?
Yes, although I know there is a bug out there with this same bug description,
where a lot of bug where duped against. 
But I guess that doesn't matter much, because that bug also was fixed by the fix
for bug 20022.
This fix is only done in the trunk/1.8a builds, so you'll still see the bug in
the branch/1.7/Aviary builds.

*** This bug has been marked as a duplicate of 20022 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.