Closed Bug 1081384 Opened 11 years ago Closed 11 years ago

Black or white rectangle appears. And Image corrupted when resize window

Categories

(Core :: Graphics, defect)

35 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 1085187
Tracking Status
firefox34 --- unaffected
firefox35 --- affected
firefox36 --- affected

People

(Reporter: alice0775, Assigned: bas.schouten)

References

Details

(Keywords: regression)

Attachments

(2 files)

Attached file test.html
[Tracking Requested - why for this release]: rendering error Steps To Reproduce: 1. Resize window size approx. 700x700px 2. Load the attached --- observe image 3. Resize window width to approx. 1200px and then reduce approx. 700px And reload (F5) --- observe image 4. Resize window height to approx. 500px and then enlarge approx. 700px --- observe image Actual Results: Black and white rectangle appears. And Image corrupted when resize window Expected Results: Render properly Regression window(m-i) Good: https://hg.mozilla.org/integration/mozilla-inbound/rev/165c3fd176ec Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 ID:20141001112720 Bad: https://hg.mozilla.org/integration/mozilla-inbound/rev/d954ed24e795 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 ID:20141001113823 Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=165c3fd176ec&tochange=d954ed24e795 Suspect: Bug 902952
Attached image screenshot
See Also: → 1081337
See Also: → 1077071
Bas - looks like your work is the culprit here, can you check into this?
Flags: needinfo?(bas)
Assignee: nobody → bas
Status: NEW → ASSIGNED
Flags: needinfo?(bas)
Looks to be a dupe of bug 1085187.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
I cannot reproduce the problem on the following m-i build. https://hg.mozilla.org/integration/mozilla-inbound/rev/0c50940fd16d Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20141029154215 I can verify that bug 1085187 fixes this problem.
Status: RESOLVED → VERIFIED
[Tracking Requested - why for this release]:
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: