=288670)
* [Bug 562648 - Prioritized locale list for fallback of strings or
add-ons](language/translation fall-back; fallback is always en-US)]
--
Marcos Caceres
Ping?
Mozilla would like to know if anyone else is interested or specially if people
are NOT interested. We would like to implement this and expose it on the
platform.
See:
https://bugzilla.mozilla.org/show_bug.cgi?id=780953
On Friday, July 26, 2013 at 8:14 PM, Marcos Caceres wrote
are not subscribed to this list and are unlikely to respond!**
The spec can be viewed at [1]; the GH repository is at [2].
[1] http://whatwg.github.io/serial/
[2] https://github.com/whatwg/serial
--
Marcos Caceres
, I kindly ask that we seek to find a way forward with src-n.
Kind regards,
Marcos
--
Marcos Caceres
On Monday, November 18, 2013 at 3:34 PM, Jirka Kosek wrote:
On 18.11.2013 14:38, Marcos Caceres wrote:
we really need to, srcset. The developer community already made
significant sacrifices in compromising on picture because of issues
that implementers raised about nested elements
issues/discussions:
https://bugzilla.mozilla.org/show_bug.cgi?id=1013913
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/nzRY-h_-_ig/IeXq74xUWzkJ
Thanks!
--
Marcos Caceres
can put the right license and allow more
people to edit the document on GH (it was a read only Google doc, which is not
great).
I'm not volunteer to edit it :)
--
Marcos Caceres
. The thing would be
to see if it really does make sense to reuse those things in contexts where
`brand-color` is to be used and not produce unexpected results.
--
Marcos Caceres
## Use cases
A website wants the prevent a device from entering a power-saving state to
allow a user to complete a task where it's not practical for the user to touch
the screen (e.g., a maps application while driving, a VR headset like
Cardboard).
A website needs to be able to complete a
On July 15, 2014 at 3:31:32 PM, Jasper St. Pierre (jstpie...@mecheye.net) wrote:
Should the lock automatically be released if the user switches to a
different tab or somehow makes the content unviewable?
Yes. But it could be automatically reapplied once the user switches back to the
On Wednesday, July 16, 2014 at 5:59 AM, Mounir Lamouri wrote:
On Wed, 16 Jul 2014, at 05:21, Marcos Caceres wrote:
I do not think we should have this timeout option. That sounds like a
very week use case and something fairly easy to do with the tools the
platform already provides
On Thursday, July 17, 2014 at 6:12 AM, Mounir Lamouri wrote:
On Thu, 17 Jul 2014, at 01:56, Marcos Caceres wrote:
I don't have a strong opinion. My concern was mostly about developers
having to watch for a whole bunch of different interaction queues (touch
events, mouse events, focus
On Monday, August 18, 2014 at 6:24 PM, Kornel Lesiński wrote:
I think it'd be unfortunate if this API had just one shared lock per browsing
context and required components on the page to coordinate locking, but
provided no means to do so.
The API allows scripts to check which locks
On Monday, August 18, 2014 at 7:21 PM, Kornel Lesiński wrote:
My biggest concern with the WakeLock API is that it's easy to forget (or
fail) to release the lock.
It's not a problem with the API per se, but a programming problem in general:
resource management in non-trivial programs is
On Monday, August 18, 2014 at 8:10 PM, Domenic Denicola wrote:
In general I feel this thread has taken a turn for the complex. Why don't we
just do what other platforms do, and provide a simple global request/release
mechanism (or toggleable Boolean property!), which developers can build
(sorry, accidental send before!)
On Monday, August 18, 2014 at 8:10 PM, Domenic Denicola wrote:
In general I feel this thread has taken a turn for the complex. Why don't we
just do what other platforms do, and provide a simple global request/release
mechanism (or toggleable Boolean
On Monday, August 18, 2014 at 6:41 PM, Kornel Lesiński wrote:
WakeLock.request() expecting a string isn't very friendly to feature
detection.
The API tells you if a wake lock type is not supported by either rejecting with
a TypeError or by a DOMException whose name is NotSupportedError.
On August 19, 2014 at 11:16:19 AM, Nils Dagsson Moskopp
(n...@dieweltistgarnichtso.net) wrote:
Tab Atkins Jr. writes:
This solves the GC and locking issues (the latter by delegating state
management to CSS, which everyone already knows to use).
It would also make it easily possible to
On August 19, 2014 at 2:08:04 PM, Jonas Sicking (jo...@sicking.cc) wrote:
How would you handle feature detection with this design?
This is a good question. I don't have a better solution than adding
separate DisplayWakeLock() and SystemWakeLock() classes.
Might make sense to do
it and
decide they don't need to request their own lock (only to be screwed when
the other lock releases earlier or later than they expected).
It's the only authoritative source of truth. But ok, fair point about the
footgun.
Consider the static dropped.
--
Marcos Caceres
On Wednesday, August 20, 2014 at 5:15 AM, Olli Pettay wrote:
On 08/20/2014 11:33 AM, Anne van Kesteren wrote:
On Wed, Aug 20, 2014 at 10:29 AM, Jonas Sicking jo...@sicking.cc
(mailto:jo...@sicking.cc) wrote:
FWIW, the web platform sorely needs a construct for readonly state
On Wednesday, August 20, 2014 at 11:14 AM, Anne van Kesteren wrote:
On Wed, Aug 20, 2014 at 5:09 PM, Marcos Caceres w...@marcosc.com
(mailto:w...@marcosc.com) wrote:
And of course Object.observe would work really nicely, but I've been told a
bunch of times by various people that we
22 matches
Mail list logo
