On Tue, 08 May 2012 18:59:29 +0200, Ian Hickson i...@hixie.ch wrote:
On Thu, 18 Aug 2011, Philip Jägenstedt wrote:
This is true, but as long as a few big browsers implement e.g.
preload=none in a somewhat compatible way, it's hard to imagine page
authors not coming to depend on that behavior
On Wed, 09 May 2012 03:56:29 +0200, James Greene
james.m.gre...@gmail.com wrote:
Full proposal details:
https://gist.github.com/3ded0f6e7f0a658b9394
P.S. I had no idea what product to file this under in the W3C Bugzilla,
so it has NOT been filed there.
On Wed, 09 May 2012 03:56:29 +0200, James Greene
james.m.gre...@gmail.com wrote:
Full proposal details:
https://gist.github.com/3ded0f6e7f0a658b9394
quoting the above (revision
https://gist.github.com/3ded0f6e7f0a658b9394/51e980f0474c255738a3b6ecf003bb6cb30db49c
):
# Proposal:
On Wed, May 9, 2012 at 5:59 AM, Doug Turner do...@mozilla.com wrote:
Where was that discussion?
This came up at the WebApps F2F and there was general agreement that
if we added new events adding new event handler attributes would make
sense. Feature detection of some kind is useful as forcing
Scott González wrote:
On Tuesday, May 8, 2012, Doug Turner wrote:
You don't. This API doesn't have device detection. Don't assume that
onXXX means that the UA supports an event.
I thought this was the preferred way to check. I seem to recall a
discussion about this and agreement that this
On May 9, 2012, at 3:14 AM, Anne van Kesteren wrote:
On Wed, May 9, 2012 at 5:59 AM, Doug Turner do...@mozilla.com wrote:
Where was that discussion?
This came up at the WebApps F2F and there was general agreement that
if we added new events adding new event handler attributes would make
There was a related discussion on the mailing list:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-November/029252.html
I also found a message from Hixie to me, related to that thread: I agree
entirely that if an event has a use case, it makes sense for it to have an
event handler
There is a discussion on the DAP WG, we like the simplicity of the proposal
however there is an important feature that is missing which is ability to set
the report interval and threshold.
Thanks
Dzung Tran
-Original Message-
From: whatwg-boun...@lists.whatwg.org
That is different -- Hixie can chime in.
I think the idea is that if you have and dom event handler, you should also
have an on event handler attribute. Its meaning is less defined. I do not
think it means that if ondevicemotion exists, that means you will always see
device motion
The original question was How do you detect if the UA supports each of
these sensor?
I don't think we're asking whether you'd get events, but whether you can
detect that the UA actually supports the event. I would think the UA should
expose support (via onxxx attributes) if the UA and device
10 matches
Mail list logo
