Bug 876615 - Remove Vivo bookmarks in the browser
Bug 876145: fix authentication dialog in browser (wrong attribute)

Replace l10n-id with data-l10n-id in browser. As it is, the
authentication dialog's title is always displayed in English.
Bug 877960: followup to check the pref by default.
Merge remote-tracking branch 'upstream/master'
merge
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Bug 876703 - [Browser] Make activity filter case insensitive on URL protocol (http://).
Bug 878732 - Homescreen gets stuck between everything.me screen and time display
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Bug 856074 - Controls on the call screen should be disabled until the call is reported connecting when dialing emergency number in airplane mode
Bug 879177 - Can't fully scroll when searching (first time) contacts
add double quotes to nodejs and npm paths

fix the problem when path contains whitespaces
Merge remote-tracking branch 'upstream/master'
Bug 845760 - long press on period key does not show special character menu on French keyboard, r=dflanagan
Bug 877683 - [MMS] Compose field obscured by subheader r=gnarf37

In accordance with the UI specification, update the interaction between
the "subheader" elements and the Compose field. Specifically, this
means:

- Some elements should never obscure the Compose fields (when active,
  they should instead "push" the Compose field downward if it is
  rendered at maximum height. These elements are:
  - The Recipients List (or "To: Field")
  - The "MMS Max Length" notifications
  - The "Carrier" element
- The "Message Convert Notification" should render overlaid on the
  Compose field.

To implement the specified behavior, this commit includes the following
changes:

- The "subheader" elements
  - Markup has been updated to differentiate between notifications that
    should push the Compose field downward and those that are "overlaid"
    on the Compose field.
  - Styling has been updated to ensure that the appropriate elements
    trigger resizing of the "subheader" (while taking care not to alter
    the visual presentation of these elements)
- Compose field height recalculation:
  - Scheduled to occur whenever changes in the DOM may change the height
    of the "subheader"
  - Removed logic that triggered recalculation in response to the
    global `hashchange` event (the above change obsoletes this more
    simplistic heuristic)
- Maximum input height calculation now has been generalized to honor any
  change in height to the "subheader"
- The Compose field's height calculation logic has been updated:
  - Modify the input's scoll offset (in order to prevent undesired
    changes in position)
  - Comments and variable names updated as appropriate
  - Remove meaningless CSS calculation (setting the `bottom` attribute
    of a `position: static;` element)
Bug 809607 - Abort transactions / sync if account was removed r=lightsofapollo
Merge pull request #9852 from lightsofapollo/bug-809607-cleanup

Bug 809607 - Abort transactions / sync if account was removed r=lightsof...