Closed
Bug 324888
Opened 19 years ago
Closed 17 years ago
in most urls the screen jitters as it is in this very window
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jensmobil, Unassigned)
References
()
Details
(Whiteboard: CLOSEME 06/27)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 I have no extentions and have downloaded the latest version of Firefox. Windows is updated. Told that Quicktime gives problem and so updated with out help. Reproducible: Always Steps to Reproduce: 1.Booted and started Google News happenes everytime! 2. 3. Actual Results: screen jitters Expected Results: have a steady screen that does not go up and down a 16th of an inch 10x a second I have many things running so interference with another program is very possible but can not find out which.
Comment 1•19 years ago
|
||
*** Bug 324889 has been marked as a duplicate of this bug. ***
Comment 2•19 years ago
|
||
*** Bug 324890 has been marked as a duplicate of this bug. ***
Comment 3•19 years ago
|
||
*** Bug 324891 has been marked as a duplicate of this bug. ***
Comment 4•19 years ago
|
||
This can happen if the bookmarks toolbar is empty. Please see support on irc.mozilla.org or www.mozillazine.org for help.
(In reply to comment #4) > This can happen if the bookmarks toolbar is empty. See bug 247116.
Comment 6•17 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
Comment 7•17 years ago
|
||
I can't reproduce using Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9a6pre) Gecko/20070701 Minefield/3.0a6pre ID:2007070104. Closing as WFM. Reporter, if you're still seeing this, please comment with details and reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•