Unless stated otherwise, the term screen is ... Does it ever state
otherwise? Please remove the conditional if not.
a Promise object whose associated task Instead of task use a word
like operation so readers are not confused with the event loop from
HTML.
Unless specified otherwise, when
Sorry for the late response Arun. I blame vacation and not being quite
sure how we should solve this taking into account the legacy
consumers.
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
On August 5, 2014 at 6:33:46 AM, Anne van Kesteren (ann...@annevk.nl) wrote:
snip
This is great feedback - thanks for this Anne! I've captured each of the issues
you raised in the bug tracker on GH [1] (and cc'ed you on them). We will
address them in the next few days.
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 do non-obvious math in order to get
coordinates which are usable. Same thing
I have added proposed text to this bug. Any objections to this?
Proposed text, based on the text for collapse():
void setBaseAndExtent (Node baseNode, unsigned long baseOffset, Node
extentNode, unsigned long extentOffset);
The method must throw an IndexSizeError exception if offset is negative
Ben, All:
As we're progressing in our discussions about working jointly, allow me
to invite you to the next Indie-UI teleconference as detailed below.
Please feel free to join us on this call, or any following call to
discuss our mutual interests. This is simply another opportunity to
advance our
For consistent terminology with the rest of the API, shouldn't it be
`setAnchorAndFocus`?
Sincerely,
James Greene
Sent from my [smart?]phone
On Aug 5, 2014 5:54 PM, Ben Peters ben.pet...@microsoft.com wrote:
I have added proposed text to this bug. Any objections to this?
Proposed
?This API is already used on the web so we should probably keep it as-is.
From: James M. Greene james.m.gre...@gmail.com
Sent: Tuesday, August 5, 2014 4:58 PM
To: Ben Peters
Cc: Ryosuke Niwa; public-webapps
Subject: RE: [selection] Selection.setBaseAndExtent
