Closed Bug 751508 Opened 12 years ago Closed 12 years ago

Blackened parts on places where content should be partly transparent

Categories

(Core :: Graphics, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 750535
Tracking Status
blocking-fennec1.0 --- +

People

(Reporter: martijn.martijn, Assigned: cwiiis)

References

()

Details

(Keywords: mobile, regression, testcase)

Attachments

(2 files)

Attached file testcase
See testcase, in current trunk builds parts of that page can have more black parts or completely black parts where you should see transparency.

I see this on the HTC Desire HD, Samsung Galaxy SII and Samsung Galaxy Nexus.

I'll attach a screenshot of the bug.

This seems to be a regression.
I don't see it in an Aurora build of 2012-04-02, but I do see it in today's Aurora build. Also seeing it today's trunk build.
Initially, the page might look good, but a small scroll is enough to show the bug.
Chris - does this seem related to some of your changes?
Assignee: nobody → chrislord.net
blocking-fennec1.0: ? → +
The transparancy doesn't scroll down with the current nightly 5/7/2012 on initial land.  I don't see the blackend parts.  Once the screensaver clicked in and repainted everything, the page works fine.  This was on the HD Desire HD


The aurora build shows the blacked parts 05-02-2012:
2012-04-02 - works
2012-04 15 - works
2012-04-22 - works
2012-04-26 - works (but you have to go out of the app and back in to see it working correctly when panning)
2012-04-27 - bug actual result occurs
2012-04-28 - bug actual result occurs
2012-04-30 - bug actual result occurs
2012-05-03 - bug actual result occurs

Bug occurs between  4/26 and 4/27
I imagine this was a retained tile bug, which would've been fixed with bug 750535, though is still possible to manifest (just a lot more difficult, and the glitch would be transient). I would suggest that the bug in its current form should not block beta - I can cook up a complete fix so that retained tiles don't render incorrectly when opacity is involved if it's a priority.
I'm not seeing this bug anymore, so you can mark this bug fixed too, if you prefer (and file a follow-up for whatever you describe in comment 5).
Marking as fixed, as per comment #6.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Resolving as a dup based on comment 5-7
Resolution: FIXED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: