CLOBBER
author Boris Zbarsky <bzbarsky@mit.edu>
Tue, 15 Nov 2016 17:44:43 -0500
changeset 322806 0a7ad34a4a516c5a6b34431a62823c538888f3ad
parent 322404 a516c754042c438a5c1499171ca525a980ecb911
child 324501 c5c8bd440978ec31deb66443bc2b17095e4a9fa4
permissions -rw-r--r--
Bug 1317591. Get rid of IsCallerChrome usage in Navigator. r=bkelly This restores the throwing behavior for .userAgent/appVersion/platform that was incorrectly removed in bug 925847.

# 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.

Merge day clobber