Bug 110552 - background-attachment: fixed causes redraw issues when applied to element alongside transform: perspective
Summary: background-attachment: fixed causes redraw issues when applied to element alo...
Status: RESOLVED DUPLICATE of bug 65793
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-02-21 21:41 PST by Peter Lejeck
Modified: 2013-06-15 13:04 PDT (History)
5 users (show)

See Also:


Attachments
Test Case Reduction (1.25 KB, text/html)
2013-02-21 21:41 PST, Peter Lejeck
no flags Details
Bug Screenshot (122.30 KB, image/png)
2013-02-21 21:42 PST, Peter Lejeck
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lejeck 2013-02-21 21:41:21 PST
Created attachment 189677 [details]
Test Case Reduction

Redraws for fixed backgrounds don't appear to be triggered automatically when applied to the same DOM node as a 3D CSS transform.

Steps to Reproduce:
1) Apply 3D CSS Transform to same node as a fixed-attachment background. (see attached test case for example)
2) Scroll down.
3) Force a redraw (partial or whole).  This can be done by (a) selecting text within the bounding box for a partial redraw or (b) resizing the window for a full redraw

Actual Results:
Visual tearing for partial redraws, and complete repositioning of background for full redraws.

Expected Results:
Background should behave as background-attachment: fixed, staying in one place while you scroll.

Platforms Confirmed:
Mac OS 10.8.2, Chrome 24.0.1312.57
Mac OS 10.8.2, WebKit Nightly 537.32+
Windows 8, Chrome 25.0.1364.97 (channel m)
Comment 1 Peter Lejeck 2013-02-21 21:42:27 PST
Created attachment 189678 [details]
Bug Screenshot
Comment 2 Radar WebKit Bug Importer 2013-02-22 11:13:30 PST
<rdar://problem/13274831>
Comment 3 Simon Fraser (smfr) 2013-06-15 13:04:16 PDT

*** This bug has been marked as a duplicate of bug 65793 ***