+ri...@opera.com
On Wed, 6 Aug 2014, at 07:14, Jonas Sicking wrote:
Hi All,
I think the current interaction between the screen orientation and
device orientation specs is really unfortunate.
Any time that you use the device orientation in order to render
something on screen, you have to
Welcome back - we missed you :-)
On Aug 5, 2014, at 9:43 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Arun Ranganathan a...@mozilla.com wrote:
There are two questions:
1. How should FileReaderSync behave, to solve the majority of use cases?
2. What is a
I would find it extremely useful to have a function available to a Worker
that would block and wait for a message from another Worker or from the
main thread. For example, instead of:
onmessage = function(event) {
// Do some work
// Save all state for next time
};
I'd like to have something
On Fri, Aug 8, 2014 at 12:49 PM, Alan deLespinasse adelespina...@gmail.com
wrote:
I would find it extremely useful to have a function available to a Worker
that would block and wait for a message from another Worker or from the
main thread. For example, instead of:
onmessage =
This is a really solid list. Thank you for pulling it together, so we can
start towards a harmonized set of user events.
From: Ben Peters [mailto:ben.pet...@microsoft.com]
Sent: Monday, August 4, 2014 7:28 PM
To: public-editing...@w3.org; Julie Parent; public-indie...@w3.org;
public-webapps
From: Julie Parent jpar...@google.com
This is a great list, and I agree it is the right starting point.
On Mon, Jul 21, 2014 at 6:12 PM, Ben Peters ben.pet...@microsoft.com wrote:
* Activate / Invoke
* Expand
* Collapse
* Dismiss
* Media next/previous/start/stop/pause
* Rotate
