Last Comment Bug 295303 - pieces of loaded page shift one pixel upon selecting or scrolling
: pieces of loaded page shift one pixel upon selecting or scrolling
Status: RESOLVED WORKSFORME
:
Product: Core
Classification: Components
Component: Layout (show other bugs)
: 1.0 Branch
: x86 Linux
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-23 23:01 PDT by chocolateleafmonster
Modified: 2008-06-07 11:16 PDT (History)
2 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description chocolateleafmonster 2005-05-23 23:01:38 PDT
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

In Firefox 1.0.3 in Linux and previous versions I've experienece graphical
gliches as a result of selecting text, scrolling, clicking links, or virtually
any action.  Typically the selected text and/or other aspects of the page will
shift one pixel.   

Reproducible: Sometimes

Steps to Reproduce:
1. Select text or scroll the page

Actual Results:  
The page creased.
Comment 1 José Jeria 2005-05-24 06:51:39 PDT
I saw this as well using SuSE 9.2 with KDE, but not when using Ubuntu with Gnome
Comment 2 Boris Zbarsky [:bz] 2005-07-28 20:00:59 PDT
Is this a problem with Deer Park 2?
Comment 3 Tony Mechelynck [:tonymec] 2008-06-07 11:16:19 PDT
(In reply to comment #2)
> Is this a problem with Deer Park 2?
> 

I don't know, but I don't remember ever noticing it. At the moment I'm using:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008060701 SeaMonkey/2.0a1pre

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.15pre) Gecko/20080607 BonEcho/2.0.0.15pre

Resolving WORKSFORME. If someone can reproduce this with a recent build, please provide a testcase or (if possible) instructions to produce it every time, and (in any case) say in which build you saw it.

Note You need to log in before you can comment on or make changes to this bug.