CLOBBER
author Jim Chen <nchen@mozilla.com>
Wed, 19 Jul 2017 14:29:59 -0400
changeset 418394 b7909eddfe2659a1d02afe4f416b28a2a21c0b28
parent 415642 587daa4bdc4b40b7053f4ca3b74723ca747f3b52
child 420956 86913f512c3cda5b2ec612476ea04a370bb3b686
permissions -rw-r--r--
Bug 1351170 - 2. Notify selection listeners after adjusting range offsets; r=smaug `nsRange` registers mutation observers to adjust the range when content changes. However, there are some cases where we adjust the start and/or end offsets but don't notify selection listeners (i.e. we don't call `nsRange::DoSetRange` to set the new range points, contrary to what the comment above `nsRange::DoSetRange` says). This patch makes us call `nsRange::DoSetRange` in those cases. The patch adds a testcase in test_selectevents.html, and changes a few unexpected-pass cases in test_composition_text_querycontent.xul that this patch fixed. MozReview-Commit-ID: 73D8RYMS3MS

# 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 1353650 - Update to ICU 59 requires clobber