Bugs 1183355 and 1209958 have now landed on inbound, which means that
crashes caused by MOZ_CRASH in release builds will now be annotated, and
the annotation reasons should be visible on crash-stats. Currently the
crash will be annotated with any string literals passed to the MOZ_CRASH
macro, so
Note that Chrome 46 has a way to work around the white screen while a
page load using a new property in the Manifest. If a website added to
the homescreen on Chrome Android has a background_color information, it
will be used while the page loads. After Chrome gets the first paint
following a
On Thu, Oct 8, 2015 at 9:10 AM, Mounir Lamouri wrote:
> Note that Chrome 46 has a way to work around the white screen while a
> page load using a new property in the Manifest. If a website added to
> the homescreen on Chrome Android has a background_color information, it
> will
In a couple threads we've been debating back and forth about what we currently
have as navigator.mozHour12 in Firefox OS.
It's a tri-value setting (undefined, true, false) that we take from mozSettings
to adjust our Clock to use user chosen setting.
For a while, I've been asking to get it in
I promised a proposal:
navigator.mozSettings.get('locale.hour12').then(value => {
console.log('value for locale.hour12 is: ' + value);
});
This would be asynchronous, and only available for a small set of variables
(whitelisted).
zb.
___
We're about to start working on another API for the next Firefox OS, this time
for DOM Intl, that will operate on `data-intl-format`, `data-intl-value` and
`data-intl-options`.
It would be much easier for us to keep l10n and intl separately and
independently, but in the current model we will
6 matches
Mail list logo