On 3/13/14 10:59 AM, Mounir Lamouri mou...@lamouri.fr wrote:
I recently landed a usage counter for window.orientation. It will take
some time to roll to Chrome Android stable but hopefully we will find
out if window.orientation is actually used a lot. If that's the case and
other UA want to
What happened to the initiative done to take a holistic view on all
orientation related specs and make them seem like they come from the same
entity (Device Motion, Media Queries, Orientation Lock, ...)?
The confusion grows when we have e.g. different primary orientations
(landscape, portrait) -
Original Message
Subject: [admin] Please register for WebApps 10-11 April 2014 f2f
meeting; deadline March 28
Resent-Date:Mon, 17 Feb 2014 13:51:50 +
Resent-From:public-webapps@w3.org
Date: Mon, 17 Feb 2014 08:50:41 -0500
From: ext Arthur Barstow
3.1.3 Keys
(...)
Operations that accept keys must perform as if each key parameter value, in
order, is copied *by the by the* structured clone algorithm [HTML5] and the
copy is instead used as input to the operation, before proceding with rest
of the operation.
Link:
On 3/13/14 7:43 PM, ext Ryosuke Niwa wrote:
Hi,
It appears that there is a lot of new features such as CSS regions and shadow
DOM that have significant implications on selection API, and we really need a
spec. for selection API these specifications can refer to.
Thankfully, Aryeh has done a
On Fri, 14 Mar 2014, at 6:44, Kenneth Rohde Christiansen wrote:
I am cc'ing Wonsuk and Christophe as Tizen is currently implementing (and
shipping?) the API as well; it's even unprefixed.
We are also supporting the current API in Crosswalk, but I am OK with the
change as most of our current
On Fri, 14 Mar 2014, at 16:09, Jonas Sicking wrote:
However it does mean that we need to also have a way to define that
orientation should be completely unlocked. This is needed since the
manifest spec allows overriding the default unlocked orientation. I.e.
it should be possible to use the
I agree, and it was also a surprise to me when I first noticed that. I
believe Wonsuk might know the history behind that decision.
Kenneth
On Fri, Mar 14, 2014 at 2:55 PM, Mounir Lamouri mou...@lamouri.fr wrote:
On Fri, 14 Mar 2014, at 6:44, Kenneth Rohde Christiansen wrote:
I am cc'ing
On March 14, 2014 at 9:58:59 AM, Mounir Lamouri (mou...@lamouri.fr) wrote:
On Fri, 14 Mar 2014, at 16:09, Jonas Sicking wrote:
However it does mean that we need to also have a way to define that
orientation should be completely unlocked. This is needed since the
manifest spec allows
On 3/11/14 5:45 PM, ext Mounir Lamouri wrote:
FYI. For those not used to Blink's process, that doesn't mean the
feature is planning to ship yet but Google is working on this. The API
we are aiming for is a bit different from what the specification
currently describes as mentioned in the original
On Fri, Mar 14, 2014 at 2:23 PM, Arthur Barstow art.bars...@nokia.comwrote:
On 3/11/14 5:45 PM, ext Mounir Lamouri wrote:
FYI. For those not used to Blink's process, that doesn't mean the
feature is planning to ship yet but Google is working on this. The API
we are aiming for is a bit
Perhaps I'm missing some context. What issue are you raising that isn't
handled by the gamepad API [1]?
[1] https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html
On Fri, Mar 14, 2014 at 1:35 AM, Patrick H. Lauke re...@splintered.co.ukwrote:
No takers on the idea of having some form of
On Fri, 14 Mar 2014, at 19:07, Lars Knudsen wrote:
What happened to the initiative done to take a holistic view on all
orientation related specs and make them seem like they come from the same
entity (Device Motion, Media Queries, Orientation Lock, ...)?
Device Motion is about the device angle
On 14/03/2014 15:29, Vincent Scheib wrote:
Perhaps I'm missing some context. What issue are you raising that isn't
handled by the gamepad API [1]?
[1] https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html
The issue is perhaps hypothetical at the moment, but: the spec currently
does
On 3/14/2014 11:36 AM, Patrick H. Lauke wrote:
On 14/03/2014 15:29, Vincent Scheib wrote:
Perhaps I'm missing some context. What issue are you raising that isn't
handled by the gamepad API [1]?
[1] https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html
The issue is perhaps
On 14/03/2014 15:52, Ted Mielczarek wrote:
After ruminating, though, my thought was that an explicit API is
probably not necessary--if a web page accesses the Gamepad API at all
then the browser can relinquish using the controller as navigation to
allow the page to do its thing.
Yes, that sort
Thanks, fixed.
On Thu, Mar 13, 2014 at 2:42 PM, Danillo Paiva
danillo.paiva.tol...@gmail.com wrote:
3.1.3 Keys
(...)
Operations that accept keys must perform as if each key parameter value,
in order, is copied *by the by the* structured clone algorithm [HTML5]
and the copy is instead
Agreed. any sounds the most descriptive.
/ Jonas
On Fri, Mar 14, 2014 at 7:01 AM, Marcos Caceres w...@marcosc.com wrote:
On March 14, 2014 at 9:58:59 AM, Mounir Lamouri (mou...@lamouri.fr) wrote:
On Fri, 14 Mar 2014, at 16:09, Jonas Sicking wrote:
However it does mean that we need to also
On Mar 14, 2014, at 5:58 AM, Arthur Barstow art.bars...@nokia.com wrote:
On 3/13/14 7:43 PM, ext Ryosuke Niwa wrote:
Hi,
It appears that there is a lot of new features such as CSS regions and
shadow DOM that have significant implications on selection API, and we
really need a spec. for
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24703
Mounir Lamouri mou...@lamouri.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24695
Mounir Lamouri mou...@lamouri.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24700
Mounir Lamouri mou...@lamouri.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24699
Mounir Lamouri mou...@lamouri.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25053
Bug ID: 25053
Summary: Specify clear security requirements
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25054
Bug ID: 25054
Summary: Should the API be exposed to non-Mobile?
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24702
Mounir Lamouri mou...@lamouri.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
Great. I applied those changes to the current ED. It might lack a bit of
clarity but I will integrate Promises soon so I will likely revisit the
language later.
-- Mounir
On Sat, 15 Mar 2014, at 5:36, Jonas Sicking wrote:
Agreed. any sounds the most descriptive.
/ Jonas
On Fri, Mar 14,
On Mar 12, 2014, at 6:54 PM, Ian Hickson wrote:
For blob: URLs we agreed to make this pretty explicit:
http://dev.w3.org/2006/webapi/FileAPI/#originOfBlobURL
Unfortunately, scripts don't have origins these days, so this definition
doesn't really work.
It didn't work since it wasn't
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25061
Bug ID: 25061
Summary: [Shadow]: Minor grammatical quibble
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: trivial
On Fri, 14 Mar 2014, Arun Ranganathan wrote:
On Mar 12, 2014, at 6:54 PM, Ian Hickson wrote:
For blob: URLs we agreed to make this pretty explicit:
http://dev.w3.org/2006/webapi/FileAPI/#originOfBlobURL
Unfortunately, scripts don't have origins these days, so this
definition
On 3/13/14 10:59 AM, Mounir Lamouri mou...@lamouri.fr wrote:
I recently landed a usage counter for window.orientation. It will take
some time to roll to Chrome Android stable but hopefully we will find
out if window.orientation is actually used a lot. If that's the case and
other UA want to
31 matches
Mail list logo
