Closed Bug 744607 Opened 14 years ago Closed 13 years ago

scroll causes lines in webpage

Categories

(Core :: Graphics, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla14

People

(Reporter: xxbones21xx, Assigned: roc)

References

Details

Attachments

(2 files)

Attached image lines in nightly.png
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120411 Firefox/14.0a1 Build ID: 20120411030716 Steps to reproduce: I used the middle button to scroll through a webpage after Nightly's 4-11-12 update. Actual results: Its scrolled correctly but caused there to be lines appearing wear the page was scrolled. Expected results: Not this. Should have just scrolled and left the contents of the page untouched.
When i removed multirow bookmarks toolbar plus, then lines didnt appear anymore.
Caused by http://hg.mozilla.org/integration/mozilla-inbound/rev/25a13d26509d Link to the mentioned extension https://addons.mozilla.org/en-US/firefox/addon/multirow-bookmarks-toolbarplus Roc, is this a regression or just an incompatible extension?
Blocks: 733607
Status: UNCONFIRMED → NEW
Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core
QA Contact: untriaged → thebes
Version: 14 Branch → Trunk
Probably not the extension.
Do we snap the clip rect everywhere properly in FrameLayerBuilder?
I also notice this in current nightly build when scrolling iframes. Possible duplicate: bug #744666
Attached patch fixSplinter Review
We need to make sure that stuff outside the snapped clip rect isn't included in the layer's visible region. This patch does that. The change to nsDisplayClip::GetBounds doesn't really matter --- nothing uses this snap output --- but it's more correct; mClip's edges can be snapped, but the edges of the bounds of the wrapped list cannot be snapped.
Assignee: nobody → roc
Attachment #614669 - Flags: review?(tnikkel)
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #6) > The change to nsDisplayClip::GetBounds doesn't really matter --- nothing > uses this snap output --- but it's more correct; mClip's edges can be > snapped, but the edges of the bounds of the wrapped list cannot be snapped. So technically it should just leave aSnap alone and let nsDisplayWrapList::GetBounds set it?
Attachment #614669 - Flags: review?(tnikkel) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/e339ca6c2f11(In reply to Timothy Nikkel (:tn) from comment #7) > (In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #6) > > The change to nsDisplayClip::GetBounds doesn't really matter --- nothing > > uses this snap output --- but it's more correct; mClip's edges can be > > snapped, but the edges of the bounds of the wrapped list cannot be snapped. > > So technically it should just leave aSnap alone and let > nsDisplayWrapList::GetBounds set it? I suppose, but it doesn't matter.
Blocks: 744666
fwiw, this seems to be happening on my galexy tab, as well.
OS: Windows 7 → All
Hardware: x86_64 → All
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Depends on: 745934
No longer depends on: 745934
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: