Bug 1349255 - Make PBrowser.NotifyIMEFocus async to avoid UI jank. MozReview-Commit-ID: 15eUwMJ2Q7H

Bug 1363678 - Adapt tests to the new filtering logic. r=bgrins MozReview-Commit-ID: Kv4fmQ4hU9c

Bug 1363678 - Refactor how we do the messages limit on the reducer. r=bgrins The parent commit did some changes to the architecture of the store that needed to be handled on the limit messages function. We take advantage of this to rewrite the functions involved to be as efficient as possible. To do that, we limit the work done by Immutable structures by doing changes in them only once per added messages. MozReview-Commit-ID: 6VzobhWzK40

Bug 1363678 - Move the filtering logic to the reducer. r=bgrins We used to do the filtering on the selector, which can be costly because we're looping through all the messages of the store on each new message. Moving the logic to the reducer allow us to be more thoughtful about which messages to evaluate and when. In order to make this change, we need to pass the filter state to the message reducer. This is done by ditching the combineReducers helper function and do the plumbing by ourselves, which isn't complex. MozReview-Commit-ID: Lw37XgEFf7e

Bug 1363678 - Adapt tests to the new filtering logic. r=bgrins MozReview-Commit-ID: Kv4fmQ4hU9c

Bug 1363678 - Refactor how we do the messages limit on the reducer. r=bgrins The parent commit did some changes to the architecture of the store that needed to be handled on the limit messages function. We take advantage of this to rewrite the functions involved to be as efficient as possible. To do that, we limit the work done by Immutable structures by doing changes in them only once per added messages. MozReview-Commit-ID: 6VzobhWzK40

Bug 1363678 - Move the filtering logic to the reducer. r=bgrins We used to do the filtering on the selector, which can be costly because we're looping through all the messages of the store on each new message. Moving the logic to the reducer allow us to be more thoughtful about which messages to evaluate and when. In order to make this change, we need to pass the filter state to the message reducer. This is done by ditching the combineReducers helper function and do the plumbing by ourselves, which isn't complex. MozReview-Commit-ID: Lw37XgEFf7e

Bug 1368041 - Enable no-array-constructor across mozilla-central r?standard8 MozReview-Commit-ID: EXJNufdKKhJ

Bug 1354078 - update labels for customization context menus for Photon, r?bgrins MozReview-Commit-ID: 1qMCkzxuT4M

Bug 1354078 - update panel/toolbar context menus to move items to the right place, with tests, r?bgrins MozReview-Commit-ID: DpQdvE25iqU

Bug 1366252 - Include the URL of the support page in the error message of the no-results-found view of about:preferences search. MozReview-Commit-ID: 8WkMtMhN74B

Backed out changeset 08b93bba921c (bug 1358117) for Android Nightly bustage. r=backout a=backout MozReview-Commit-ID: IgiZGwOZ3tD

Backed out changeset 44e144a782e1 (bug 1361664) for Android Nightly bustage. r=backout a=backout MozReview-Commit-ID: L3hDVLxBkoJ

Backed out changeset d289ee2c794d (bug 1361664) MozReview-Commit-ID: gNRtEiyg7W

Bug 1361938 - Disable test_transitions_replacement_on_busy_frame.html. r?boris This test had been passed accidentaly. In the test initially a transition (transform: none to translateX(300px)) is created. After the transition was sent to the compositor, secondary transition tries to be created, the after-change style of the secondary transitions is translateX(0px). As per the transition spec, the before-change style of the secondary should be translateX(300px), but on current implementation it's approximately translateX(0.3px) that including the first transitioning value. It's apparently wrong. With the first patch in this bug, the value becomes sometimes translateX(0px) on non-E10S debug build for unknown reasons. As a result, we don't create the secondary transition because of there is no difference between before-change(translateX(0px)) and after-change style(translateX(0px). This test can be enabled once we get correct before-change style (bug 1368235). MozReview-Commit-ID: IHKCf5fnKRA

Bug 1361938 - Don't process visited rules during animation-only restyle. r?jryans MozReview-Commit-ID: GEKzOanu0VD

Bug 1361938 - Do not cascade when we have both of RESTYLE_STYLE_ATTRIBUTE and animation RestyleReplacements. r?heycam The PropertyDeclarationBlock which has been set for RESTYLE_STYLE_ATTRIBUTE is stored in rule nodes, we will end up processing RESTYLE_STYLE_ATTRIBUTE in animation-only restyle if we call cascade_primary_and_pseudos duing animation-only restyle in the case where we have both of RESTYLE_STYLE_ATTRIBUTE and animation RestyleReplacements. MozReview-Commit-ID: DatPeRJkAlv

Bug 1362542 - Avoid flusing layout when updating tabs' visiblity status for the overflow menu. r?florian MozReview-Commit-ID: IG3t4vMdDFu

Bug 1368208 - Don't flush layout to determine whether scrollbox scroll buttons should be enabled/disabled. r?florian MozReview-Commit-ID: 78COLSJRszS

Bug 1363596 part 3 - Add string support for list-style-type. r=heycam MozReview-Commit-ID: 9zT8IH6sxWH