Closed Bug 743393 Opened 13 years ago Closed 13 years ago

background-attachment:fixed > black / white areas when maximizing

Categories

(Core :: Graphics, defect)

14 Branch
x86_64
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla14

People

(Reporter: fusionneur, Assigned: bas.schouten)

References

Details

(Keywords: css3, regression)

Attachments

(2 files)

Attached file Bug Simulation (deleted) —
User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:14.0) Gecko/20120406 Firefox/14.0a1 Build ID: 20120406031222 Steps to reproduce: Assumptions -using "background-attachment:fixed" over some text -make a windows very small (restore state) so that the margins of the browser cover a part of the text -then maximize the window Actual results: -text gets covered by black / white areas ______________________________________________________________ HTML code: http://jsbin.com/anafel/3 Screenshots: 1)-normal- http://i1271.photobucket.com/albums/jj627/Fusionneur/1.jpg 2)-small restore state -http://i1271.photobucket.com/albums/jj627/Fusionneur/2.jpg 3)-maximizing-http://i1271.photobucket.com/albums/jj627/Fusionneur/3.jpg 4)-bug-http://i1271.photobucket.com/albums/jj627/Fusionneur/4.jpg 5)-code-http://i1271.photobucket.com/albums/jj627/Fusionneur/5.jpg Expected results: -page should be rendered upon maximizing
OS: Windows NT → Windows 8
Hardware: x86 → x86_64
Summary: background attachment → background-attachment:fixed > black / white areas when maximizing
Attachment #613022 - Attachment mime type: text/plain → text/html
Keywords: css3
Regression window(m-c) Works: http://hg.mozilla.org/mozilla-central/rev/6881fa89cfca Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120404 Firefox/14.0a1 ID:20120404001322 Fails: http://hg.mozilla.org/mozilla-central/rev/638769f8ec54 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120404 Firefox/14.0a1 ID:20120404043722 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6881fa89cfca&tochange=638769f8ec54 Regression window(m-i) Works: http://hg.mozilla.org/integration/mozilla-inbound/rev/c95b597b5f08 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120403 Firefox/14.0a1 ID:20120403124022 Fails: http://hg.mozilla.org/integration/mozilla-inbound/rev/9fa58c6060c5 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120403 Firefox/14.0a1 ID:20120403132722 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c95b597b5f08&tochange=9fa58c6060c5 Suspected: Bug 740815 Graphics Adapter Description : ATI Radeon HD 4300/4500 Series Vendor ID : 0x1002 Device ID : 0x954f Adapter RAM : 512 Adapter Drivers : aticfx64 aticfx64 aticfx32 aticfx32 atiumd64 atidxx64 atiumdag atidxx32 atiumdva atiumd6a atitmm64 Driver Version : 8.950.0.0 Driver Date : 2-14-2012 Direct2D Enabled : true DirectWrite Enabled : true (6.1.7601.17776) ClearType Parameters : Gamma: 2200 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 200 WebGL Renderer : Google Inc. -- ANGLE (ATI Radeon HD 4300/4500 Series) -- OpenGL ES 2.0 (ANGLE 1.0.0.963) GPU Accelerated Windows : 1/1 Direct3D 10 AzureBackend : direct2d
Blocks: 740815
Status: UNCONFIRMED → NEW
Component: Layout: View Rendering → Graphics
Ever confirmed: true
Keywords: regression
QA Contact: layout.view-rendering → thebes
This is the result of the old scissor rect still being fixed. This patch fixes that issue, it also removes DualViewport setup as I realized the viewport used depends on the Geomery Shader and not on pixel shader output and we don't actually use more than one viewport. This means we can just use the LayerManager viewport code for this.
Assignee: nobody → bas.schouten
Status: NEW → ASSIGNED
Attachment #613115 - Flags: review?(jmuizelaar)
Attachment #613115 - Flags: review?(jmuizelaar) → review+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
How do I re-open this bug as I'm seeing this behavior in Firefox 20?
(In reply to Jim_Schneider from comment #7) > How do I re-open this bug as I'm seeing this behavior in Firefox 20? Please file a new Report with Testcase/Screenshot/Steps to reproduce and the Graphics Section of about:support.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: