271879 - Mouse cursor flickers heavily when page is loading

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Andrew Blake]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-GB; rv:1.7.5) Gecko/20041110 Firefox/0.10 StumbleUpon/1.998
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-GB; rv:1.7.5) Gecko/20041110 Firefox/0.10 StumbleUpon/1.998

On pages which take some time to load, Firefox causes the mouse cursor to
flicker badly. This only happens in the client area of the screen where the
webpage is due to appear. Moving the cursor onto the sidebar, address bar,
toolbar, or menu bar halts the flickering. Once the cursor is moved back into
the client area again, (provided the page is still loading), the flickering
starts again.

Once the page has completed loading, the flickering does not happen at all!

Reproducible: Always
Steps to Reproduce:
1. Log into www.theaa.co.uk.
2. Click "Traffic News" at the bottom of the screen.
3. Enter a location (I chose "Leeds/Bradford" if that makes a difference).
4. Click OK.
5. Observe the cursor flickering whilst the site is loading the required data.

Actual Results:  
Badly flickering cursor after step 2 and after step 4. This ceased when cursor
was positioned over any screen area other than the page client area. Recommences
when cursor is returned to the client area again.

Expected Results:  
The cursor should remain static on the 'busy' pointer, with no continous
flickering in the client area.

Theme: Noia Extreme 2

Probably seems to occur on any pages that take a considerable amount of time to
load, (regardless of whether this is sheer size, or the amount of traffic).

Comment 1

[Ryuichi KUBUKI]

Is the page you suggest 
http://www.theaa.com/travelwatch/inc/travel_news_redirect.jsp?searchParameter=city&searchParameterValue=Leeds+%26+Bradford&minx=407037&miny=416032&maxx=453976&maxy=443605&city=Leeds+%26+Bradford&region=+&road=&button_next.x=44&button_next.y=13
?

If so, WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6)
Gecko/20041225 Firefox/1.0+

Comment 2

[Andrew Blake]

(In reply to comment #1)
> Is the page you suggest 
> http://www.theaa.com/travelwatch/inc/travel_news_redirect.jsp?
searchParameter=city&searchParameterValue=Leeds+%
26+Bradford&minx=407037&miny=416032&maxx=453976&maxy=443605&city=Leeds+%
26+Bradford&region=+&road=&button_next.x=44&button_next.y=13
> ?
> If so, WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6)
> Gecko/20041225 Firefox/1.0+

That is certainly the correct page. However at this point I have discovered 
that the bug might just be confined to Windows 98 systems. I loaded that page 
at home on my XP Home PC, and there was no flickering whatsoever. I am using 
the same version of Firefox at home as I do at work.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.