author Kearwood Gilbert <>
Wed, 25 Jan 2017 14:45:23 -0800
changeset 378067 c76aa324c7c2b57ce42a8b26c48778782b41be76
parent 377912 dca7b42e6c67219398e6419293c075ef829adb29
child 389740 d8dd09d7df1dc97677499f08f3b99737b4821660
child 391141 b86ff4066687c7f880598820360b3c564b4f60d6
permissions -rw-r--r--
Bug 1328053 - Correct thumb position when shift-click scrolling r=mats a=jcristau During the refactoring of nsSliderFrame::SetCurrentPositionInternal in Bug 957445, one of the two calls to nsSliderFrame::UpdateAttribute was missed. This resulted in the position, identified with nsGkAtoms::curpos, not being updated immediately after the call to nsSliderFrame::SetCurrentThumbPosition MozReview-Commit-ID: 6gedouG4OFX

# 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