========
https://hg.mozilla.org/integration/gaia-central/rev/e056f253a60c
Author: Andrew Sutherland <asutherland@asutherland.org>
Desc: Merge pull request #10808 from leob2g/Bug_890486_ValueSelector_UL_Height
Bug 890486 - [Email] Last folder name is not displayed properly in the value selector UL. r=asuth (as v1.1 targeted minimal fix)
========
https://hg.mozilla.org/integration/gaia-central/rev/7b26580b900a
Author: praveen.singapati <praveen.singapati@lge.com>
Desc: Bug 890486 - [Email] Last folder name is not displayed properly in the value selector UL
========
https://hg.mozilla.org/integration/gaia-central/rev/b1f9cd3cbbb1
Author: Ian Liu <iliu@mozilla.com>
Desc: Merge pull request #10796 from ian-liu/clock/Bug890216_creating_alarm_button_is_not_align_with_date/day_context
Bug 890216 - [Clock] The button of creating alarm is not align with displaying date/day context, r=@rexboy7
========
https://hg.mozilla.org/integration/gaia-central/rev/e7bc55c1e56a
Author: ian-liu <iliu@mozilla.com>
Desc: Bug 890216 - [Clock] The button of creating alarm is not align with displaying date/day context
========
https://hg.mozilla.org/integration/gaia-central/rev/6ac97ae41660
Author: Ian Liu <iliu@mozilla.com>
Desc: Merge pull request #10789 from ian-liu/bluetooth/Bug881134_hdpi/xhdpi_resolution_assets_and_layout_for_Bluetooth_File_Transfer_app
Bug 881134 - hdpi/xhdpi resolution assets and layout for Bluetooth File Transfer app, r=@rexboy7
========
https://hg.mozilla.org/integration/gaia-central/rev/f04b97517eab
Author: Ian Liu <iliu@mozilla.com>
Desc: Bug 881134 - hdpi/xhdpi resolution assets and layout for Bluetooth File Transfer app
========
https://hg.mozilla.org/integration/gaia-central/rev/fced758fbf0b
Author: Corey Frang <gnarf37@gmail.com>
Desc: Bug 887737 - [SMS] The device is not recognizing the phone number received completely - r=julienw
* Rewrite the phone number matching regexp
* Include all the fixtures from Utils tests in FixturePhones and include in setup so we can share test cases
========
https://hg.mozilla.org/integration/gaia-central/rev/9621115bda40
Author: Fabien Cazenave <fabien@cazenave.cc>
Desc: Merge pull request #10709 from fabi1cazenave/l10nOptim-bug853933
Bug 853933 - Don't inline all locales as JSON in the HTML, r=ochameau
========
https://hg.mozilla.org/integration/gaia-central/rev/cf0c69f54763
Author: Fabien Cazenave <fabien@cazenave.cc>
Desc: Bug 853933 - Don't inline all locales as JSON in the HTML
Currently, in order to ensure that apps are translated before first paint, all l10n resources are included as one multi-locales JSON dictionary, which is serialized in an inline `<script>` element for each HTML document. This works fine when shipping few locales, but it can increase the document size quite badly for 60+ locales, thus delaying the startup time very significantly.
This patch allows to support 60+ locales more easily by having:
* one minimal JSON dictionary per locale in each HTML file;
* one extensive JSON dictionary per locale in each webapp.
The inline JSON dictionary is split on a per-locale basis (= one `<script>` node per supported locale) and only contains the l10n strings that are required to translate the HTML document: the "startup cost" of each locale becomes neglectable, and it removes the risk of high RAM consumption when parsing a giant multi-locale JSON at startup.
All l10n resources that are not declared in the HTML document are concatenated in a single JSON dictionary per locale: this reduces the number of disk I/O to load l10n resources and does not increase the total disk size of each webapp. To enable this, this patch implements a `{{locale}}` quasi-litteral in the HTML markup that is used to declare l10n resources:
<link rel="prefetch" type="application/l10n" href="/{{locale}}.json" />
where `{{locale}}` is replaced by the value of `navigator.language`.
Note that this latter optimization is only interesting for apps that wait for the `localized` event to start. With the inline JSON dictionary for the declarative content and the `mozL10n.localize()` method, most apps could probably stop waiting for this `localized` event now.
