Closed Bug 1294391 Opened 8 years ago Closed 8 years ago

Animations leave pieces behind when moving out of screen and fading out of opacity

Categories

(Core :: Graphics: Layers, defect)

48 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1280060
Tracking Status
firefox48 --- affected
firefox49 --- fixed
firefox50 --- fixed
firefox51 --- fixed

People

(Reporter: ourensan, Unassigned)

References

()

Details

(Whiteboard: [gfx-noted])

Attachments

(3 files)

Attached image bug in transition.jpg
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160728203720 Steps to reproduce: When clicking on pagination buttons or forward/back arrows, the animation is displayed. The animation consist on div's going out and in of the screen. When div goes out, opacity also transitions from 1 to 0, and when going in, from 0 to 1. The page is http://beerbay.dk/shop.html#/shop Actual results: Animation works, but sometimes random pieces of the img inside the div are "left behind" (not moved out completely of the screen, and its opacity not completely gone down to 0). This "scattered pieces" dissapear later when hovering/unhovering the items in screen (an thus firing another opacity transition in this items). Expected results: Img inside the div should have gone out of the screen, and opacity went down to 0.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
EDIT: The scattered pieces dissapear not when firing an opacity transition, but when firing a mix-blend-mode transition (when hovering in Quick view, see last attachment)
Component: Untriaged → Graphics: Layers
Looks like an invalidation bug.
Whiteboard: [gfx-noted]
I can reproduce this on 48 on OS X with BasicCompositor when switching from page 2 to page 3. Looks like a partial composition / LayerTreeInvalidation bug.
I can not reproduce this on Nightly 51. (I do see flickering because of bug 1293908.) I'll get a progression range.
This was fixed by bug 1258904, and is very similar to bug 1280060 in general, so I'm duping it to bug 1280060. So the fix for this will be released with Firefox 49.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Depends on: 1258904
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: