CLOBBER
author Timothy Nikkel <tnikkel@gmail.com>
Mon, 04 May 2015 14:29:19 -0500
changeset 242304 f58aab6a4e62d9ca2c0c9098c0eed84024adf85e
parent 242286 312707328997a7ed66ae71ff70d605e49853b24a
child 242330 8ab257db9630d9fa9d80449d5d0829cfbe97cc97
permissions -rw-r--r--
Bug 1159772. Don't let nsContainerFrame::SyncWindowProperties make widget calls that can result in synchronous painting during reflow or frame construction. r=mats Specifically on Windows nsIWidget::SetTransparencyMode can result in sync painting. So we give nsContainerFrame::SyncWindowProperties a sync or async option and use the view manager post pending update infrastructure to flush SyncWindowProperties calls async.

# 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 1159737 appears to cause bustage not rebuilding enough afterchanging nsXULAppAPI.h.