Closed Bug 207301 Opened 22 years ago Closed 22 years ago

After clicking links or buttons cursor becomes a zoom-in magnifying glass

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mozbugs, Assigned: lordpixel)

References

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030527 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030527 Camino/0.7+ If you click on any links in a webpage or on menubar links the cursor becomes a zoom-in magnifying glass. This dissapears after some normal use. Reproducible: Always Steps to Reproduce: 1.Click "home" button on menubar or 1.Click any hyperlink Actual Results: the cursor became a zoom-in magnifying glass Expected Results: the cursor should have stayed the same.
Ive noticed this too starting with 2003052704
Confirmed. This regression starts on the 2003-05-27-04 NB. The application uses the magnifying glass as a wait cursor. This magnifying glass cursor tends to appear while loading page content or large images.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Summary: after clicking links or buttons cursor becomes a zoom-in magnifying glass → After clicking links or buttons cursor becomes a zoom-in magnifying glass
Confirmed with 2003052704
Confirmed with 2003052804
who landed this feature on the trunk? does mozilla have the same issue?
This doesn't happen in the Mozilla Macho trunk (2003-05-28-08) just in the Camino NB. This was working fine on the 05/26 build but regressed on the 05/27 build. Perhaps this is the culprit ? http://bugzilla.mozilla.org/show_bug.cgi?id=78363 This checkin was done on 5.26 ..
*** Bug 207376 has been marked as a duplicate of this bug. ***
Attached patch fix (obsolete) — Splinter Review
yeah, this is a regression from bug 78363
Attachment #124367 - Flags: superreview?(sfraser)
Attachment #124367 - Flags: review?(pinkerton)
reassigning
Assignee: saari → varga
Attachment #124367 - Flags: superreview?(sfraser) → superreview+
QA Contact: winnie → petersen
Yes. This was my fault. Essentially a 2 part problem: First, fix I was working on that went into the trunk that didn't go into Camino because discussion with smfr/pink suggested a different approach for Camino based on Cocoa's NSCursor class. This is something I'm working on that I didn't finish yet Second, I fixed a regression caused by an interaction between a bug varga fixed and a bug bryner was working on and some related bitrot with one of my patches. I decided to change the absolute numerical ids of some cursors to avoid a recurrance of the problem, but I only fixed it in Mozilla, not Camino :( I'm afraid the patch as given won't work. I'll attach something momentarily...
See previous comment. This will ensure cursor ids are correct in Camino until previously discussed Cocoa NSCursor implementation is completed.
Attachment #124367 - Attachment is obsolete: true
Attachment #124367 - Flags: review?(pinkerton)
Comment on attachment 124416 [details] [diff] [review] Fix also reassigns wait cursor. Temporary fix until camino cursor reimplementation done varga: thank for trying to fix my mistake. pink/smfr: sorry for screwing up Camino. I didn't see this in my tree due to a partial fix I have locally but didn't check in due to discussion of a different way of doing Camino cursors based on NSCursor. Mea culpa.
Attachment #124416 - Flags: superreview?(sfraser)
Attachment #124416 - Flags: review?(pinkerton)
Attachment #124416 - Flags: superreview?(sfraser) → superreview+
no problem
Assignee: varga → lordpixel
Comment on attachment 124416 [details] [diff] [review] Fix also reassigns wait cursor. Temporary fix until camino cursor reimplementation done r=pink
Attachment #124416 - Flags: review?(pinkerton) → review+
I have to go to work. Will check in this evening, unless someone else wants to do it in the next few hours.
landed on the trunk, should we try to get this on the branch?
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
*** Bug 207478 has been marked as a duplicate of this bug. ***
Doesn't need to go on the branch, because I didn't put the fix for bug 78363 (cause of this regression) onto the branch.
Verified on the camino 2003-05-30-04 NB.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: