Open Bug 655646 Opened 12 years ago Updated 6 months ago
Text box displaying two extra lines below flashing cursor
(Firefox :: General, defect)
(Reporter: luke_alabaster, Unassigned)
(3 files, 1 obsolete file)
6.34 KB, text/plain
53.69 KB, image/jpeg
7.14 KB, text/plain
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 From the time the flashing cursor displays its self for the first time to when it first disapears to begin flashing, an extra two lines that are similar or identical to it appear below it. This occurs in all text boxes that I have looked at so far, including the Google search bar that is in-built into firefox, placed by default in the top right of the page. Reproducible: Always Steps to Reproduce: 1. Find a text box 2. Click on it (the problem will be visible for around a quarter of a second) 3. Begin typing (Every keystroke causes the problem to re-apear) Actual Results: As you type, you should notice two black vertical lines just below where you are typing. Diferent things happen when you select text - if you select a chunk of text and overwrite it, the lines appear on the far left and right of the previous text. Expected Results: The lines should not be visible. This has occured after I updated to firefox 4.0.1. It does not occur on my laptop. See attachments for troubleshooting information for both computers.
12 years ago
Is your Issue reproducible in Safe-Mode when Hardware Acceleration is disabled? https://support.mozilla.com/en-US/kb/Safe+Mode If no, does setting only "gfx.direct2d.disabled" to "true" via "about:config" and restarting Firefox show a Difference? Can you attach a Screenshot showing the Issue? Also - if possible - can you check against a more recent Graphics Driver?
Version: unspecified → 4.0 Branch
The issue is not reproducable in safe mode or when Hardware Acceleration is disabled, or under both circumstances. (i.e. it gets 'fixed' if I do either of your first suggestion, or both at the same time) Setting "gfx.direct2d.disabled" to "true" does not 'fix' the problem - it remains. (I had HA mode enabled when I changed this setting) I updated my graphics drivers to the most recent version, then re-tested. No change in results. A screenshot is present in the "URL" near the top of the page. Here it is again: http://imageshack.us/photo/my-images/189/firefoxerrorn.jpg/
The problem seems to have gotten worse. I'm not sure why, but the lines don't go away after the cursor's first flash. This occured after I updated my graphics drivers. In this screenshot, you can see that I have entered "2" into the text box to the right of the "Ore", and entered "114" into the text box next to the "Gemstones". The screenshot gives a better view of where the lines appear. I have not intereacted with the Fuel or Faction packages text boxes at all. They went away when I alt-tabbed to another window. They also seem to be appearing in odd spots - I think one just below where I last typed and one where I am about to start typing, even if I go from one firefox tab to another.
http://sites.amd.com/us/game/downloads/Pages/radeon_vista-32.aspx According to this there is a newer version of your driver which has been updated this month. Please update to that driver and retest. Thanks.
12 years ago
WOW64 is 64 bit Windows. Luke would need the drivers at http://sites.amd.com/us/game/downloads/Pages/radeon_vista-64.aspx
(In reply to comment #7) > WOW64 is 64 bit Windows. Luke would need the drivers at > http://sites.amd.com/us/game/downloads/Pages/radeon_vista-64.aspx Good catch, thanks Kevin.
Updated the revised troubleshooting information - I probably should have done this after I updated my graphics drivers. I decided to turn off "Use Graphics accelleration when available" and the problem is no longer fixed - this fixed it with the old set of drivers. Darn, there goes a possible temporary fix...
Attachment #530975 - Attachment is obsolete: true
6 months ago
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.