Closed Bug 4476 Opened 26 years ago Closed 24 years ago

Setting Cursor to Wait cursor causes cursor flickering.

Categories

(Core Graveyard :: Java: OJI, defect, P4)

PowerPC
Mac System 8.0
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: Hemant.Inamdar, Assigned: nezbo)

Details

(Keywords: platform-parity)

If in a top level frame, the cursor is set to a wait cursor, the cursor alternates between a wait cursor and the default cursor. causing a flickering effect.
QA Contact: 4082 → 1698
Eli, I'm re-assigning you these Mac bugs to take ownership. These are Greg's old bugs...
Component: OJI → Viewer App
This is not a plugin/OJI bug.
Assignee: amusil → don
I think Don would know better than I who should get this bug.
Sorry if I didnt make the bug description clear. This happens only when running an applet on the Mac using the plugin to use MRJ as the Java VM. When the cursor of a window created in the applet (lets say derived from JFrame) is changed fron the default cursor(arrow) to the wait cursor(hourglass) using setCursor(), the flickering behavior is noted. The cursor alternates between wait cursor and the default cursor.
Assignee: don → beard
Component: Viewer App → OJI
This is an OJI bug with the MRJ plugin running in 4.X.
Status: NEW → ASSIGNED
Target Milestone: M5
Not sure yet how to fix. Only happens under 4.X browser. My have to patch SetCursor!
Summary: Setting Cursor to Wait cursor causes cursor flickering. → [PP]Setting Cursor to Wait cursor causes cursor flickering.
Target Milestone: M5 → M6
-> M6
Target Milestone: M6 → M8
Safe to defer.
Target Milestone: M8 → M15
Assignee: beard → mark.lin
Status: ASSIGNED → NEW
Reassigning bug to mark.lin@eng.sun.com This is a 4.X bug, so it is a lower priority...
Hello. I do understand that issues regarding 4.X are at a lower priority than 5.0. However, its also true that 4.x browsers are the current browsers available from Netscape. Solving this bug and possibly others related to the OJI plugin and 4.x browsers would really help lots of mac users using Netscape 4.x browsers to use the full power of Java through OJI and using MRJ. It would be great if this bug is solved, this is probably the last issue which is holding us from shifting over to the MRJ plugin in out applet. Do let me know if you need any help on this, like test cases etc. I will try my best to help! Thanks, Hemant.
QA Contact: elig → paw
Status: NEW → ASSIGNED
Keywords: pp
Summary: [PP]Setting Cursor to Wait cursor causes cursor flickering. → Setting Cursor to Wait cursor causes cursor flickering.
No progress since August :-( In any case, this can't be blocking M15 branching, so I'm pushing this to M16
Target Milestone: M15 → M16
Mark Lin no longer works for Sun. Reassigning his bugs to George Drapeau
Assignee: mark.lin → drapeau
Status: ASSIGNED → NEW
downgrade priority, push milestone, free george.
Assignee: drapeau → loki-sun
Priority: P3 → P4
Target Milestone: M16 → M17
No target milestone: no resources to work on Macintosh bugs right now.
Target Milestone: M17 → ---
Re-assigning this bug to myself, as Loki no longer works at Sun. Leaving target milestone as undefined, as there are no resources to work on Macintosh problems.
Assignee: loki-sun → drapeau
this isn't really mac only last i looked. it was happening because we are constantly calling SetCursor even when the cursor hasn't changed, or even sometimes we change it to "default" and immediatly change it to something else. i'm not sure who's doing this though.
Re-assigning to Terry Noyes. I don't know if this is still happening.
Assignee: drapeau → tnoyes
Updating the QA contact
QA Contact: paw → junruh
Does anyone have a URL for this? Things may have improved in the last two years.
Sorry, No URL. I had put this bug in when I was having problems running the OJI plugin (to use MRJ) with the Netscape 4.x browsers on the mac. It probably does not happen now, as not only MRJ has changed, but probably the OJI plugin code has changed too. If this behavior does not happen in the current mozilla codebase, the can be ignored and closed.
Setting bug to invalid based on reporter's comments.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Verified invalid.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.