Bug 1094141 - Don't export skia APIs from xul.dll. r=glandium
Bug 1084370 - Fix handling of vertical-align in lines with vertical writing mode. r=smontagu
Bug 1094434 - Render resizer appropriately for vertical-lr and vertical-rl writing modes. r=roc
Bug 1094434 - Reftests for display of resizer on vertical-lr and vertical-rl textareas. r=roc
(no bug) Update count of GC reasons in comment DONTBUILD
Bug 1021367 - Assertion failure in GetShaderConfigFor. r=nical
Bumping gaia.json for 2 gaia revision(s) a=gaia-bump

========

https://hg.mozilla.org/integration/gaia-central/rev/5d60b07fe90d
Author: James Burke <jrburke@gmail.com>
Desc: Merge pull request #26010 from jrburke/bug1096572-building-blocks-rtl-style

Bug 1096572 - [Building Blocks] Update some RTL styles to match latest RTL spec r=timdream

========

https://hg.mozilla.org/integration/gaia-central/rev/22ce8e6d96f5
Author: jrburke <jrburke@gmail.com>
Desc: Bug 1096572 - [Building Blocks] Update some RTL styles to match latest RTL spec
Bumping manifests a=b2g-bump
Bug 1044736 - Part 1. Add BrowserElement.webidl and stub implementation. r=bz
Bug 1044736 - Part 2. Add nsIBrowserElementAPI.idl and implement nsBrowserElement. r=bz
Bug 1044736 - Part 3. Make BrowserElementParent implement nsIBrowserElementAPI and use it. r=bz,fabrice
Bug 1044736 - Part 4.1. Delete old BrowserElementParent.js. r=bz,fabrice
Bug 1044736 - Part 4.2. Rename BrowserElementParent.jsm to BrowserElementParent.js. r=bz,fabrice

--HG--
rename : dom/browser-element/BrowserElementParent.jsm => dom/browser-element/BrowserElementParent.js
Bug 1044736 - Part 4.3. Export BrowserElementParent component from BrowserElementParent.js. r=bz,fabrice
Bug 1044736 - Part 5. Extract tests functions to file_test_widget.js. r=fabrice
Bug 1044736 - Part 6. Widget should only require embed-widgets permission. r=fabrice

As discussed on dev-webapi[1] the app that wants to use widgets only
need the "embed-widgets" permission to use <iframe mozbrowser mozwidget>

If the app also wants to implement a browser, it could request the
"browser" separately. A <iframe mozbrowser mozwidget> will have
restricted mozbrowser API defined on the prototype if the embedder has
the "brower" permission; they will always throw when used.

[1]: https://groups.google.com/d/msg/mozilla.dev.webapi/uQweGWtVKRA/Bj1jZq3LN-0J

--HG--
rename : dom/apps/tests/test_widget.html => dom/apps/tests/test_widget_browser.html
Backed out 8 changesets (bug 1044736) r=bustage

Backed out changeset 920775ddfb85 (bug 1044736)
Backed out changeset a3604ab2b3ca (bug 1044736)
Backed out changeset fb6a60700803 (bug 1044736)
Backed out changeset 7037d2b40d39 (bug 1044736)
Backed out changeset 1b55f80e1ca6 (bug 1044736)
Backed out changeset f55ff90f2b6f (bug 1044736)
Backed out changeset 8505276285fa (bug 1044736)
Backed out changeset e81aa95ac8d3 (bug 1044736)

--HG--
rename : dom/browser-element/BrowserElementParent.js => dom/browser-element/BrowserElementParent.jsm
Bug 1094090 - Explicitly declare trusted app doesn't have homescreen-webapps-manage permission in PermissionsTable.jsm r=fabrice
Backed out changeset 6ccbc46c33db (bug 1044736)

--HG--
rename : dom/browser-element/BrowserElementParent.jsm => dom/browser-element/BrowserElementParent.js
Backed out changeset 920775ddfb85 (bug 1044736)