CLOBBER
author peter chang <pchang@mozilla.com>
Fri, 14 Apr 2017 11:58:42 +0800
changeset 403254 5fa3e998d3e5b22301c663837ab4acb1b580ba9f
parent 400867 819a666afddc804b6099ee1b3cff3a0fdf35ec15
child 401831 278c3bf8f7f4a1a8260e1563f18bf93ccb097d24
permissions -rw-r--r--
Bug 1345017 - Discard compositor animations on the next layer transaction, r=kats Animations in content side could be removed easily by changing CSS, but the CompositorAnimationStorage in parent side doesn't get updated. Therefore, we store the layer's CompositorAnimationsId before layer is destroyed in WebRenderLayerManager and then send out these discarded ids to parent on the next layer transaction. MozReview-Commit-ID: D4kbYsgLl4P

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1356151 - Clobber needed after bug 1353295 was backed out