- Original Message -
From: Karl Dubost ka...@opera.com
it doesn't mean they are unhappy about it. Or more exactly that a fraction of
them can even look for such a feature.
In most cases ordinary users (not geeks) can not think of a feature, before
software developers provide it
Stan stas...@orc.ru schrieb am Fri, 14 Dec 2012 11:51:57 +0300:
[…]
The main point, if device ID could be available it would provide more
great possibilities for users and web-services.
From the top of my head, I can imagine the following possibilities:
- persistant device tracking
-
Last thing to remember: the device ID is not something secret and forbidden for
native applications. For example, Android provides Android ID and iOS
ASIdentifierManager,
which can be read by any installed application. Taking into consideration that
many
web-services do provide native clients,
Hi Stan,
From: stas...@orc.ru
...
Subject: Re: [whatwg] API for unique identification of devices
(mobile/tablet/pc)
...
First, I don't think it's convenient for users to register themselves
on many sites, which they visit occasionally. If most of the users do this
right now,
it
Stan stas...@orc.ru schrieb am Fri, 14 Dec 2012 11:51:57 +0300:
First, I don't think it's convenient for users to register themselves
on many sites, which they visit occasionally. If most of the users do
this right now, it does not mean they are happy with this, this is
bacause there is no
On 13 December 2012 20:20, Stan stas...@orc.ru wrote:
Hi,
I'd like to proprose an API to get a unique device's ID in HTML5.
What is a unique device ID? Do all devices have a unique ID? Which bit of
hardware is responsible for storing such a thing? Who guarantees it's
uniqueness, and how?
On 14 December 2012 08:51, Stan stas...@orc.ru wrote:
First, I don't think it's convenient for users to register themselves
on many sites, which they visit occasionally.
A device ID won't register a user. Where will the profile information come
from? If it comes from a web-based service
I don't know if this is relevant at all, but according to the spec
(section 4.4.1), The body element represents the main content of the
document. What would you say is the relation between this use of the
term main and your use of the term here? Might it perhaps be more
accurate to state, The body
Hi Cory,
I don't know if this is relevant at all, but according to the spec
(section 4.4.1), The body element represents the main content of the
document. What would you say is the relation between this use of the
term main and your use of the term here? Might it perhaps be more
accurate
Steve Faulkner faulkner.st...@gmail.com wrote:
Hi Cory,
I don't know if this is relevant at all, but according to the spec
(section 4.4.1), The body element represents the main content of the
document. What would you say is the relation between this use of the
term main and your
Steve Faulkner faulkner.st...@gmail.com wrote:
Stewart wrote:
It doesn't necessarily. I've come across pages that expect the head to be
displayed too. e.g. tests at http://meyerweb.com/eric/css/tests/css3/like
http://meyerweb.com/eric/css/tests/css3/show.php?p=caption-side
Is this a
On Fri, 14 Dec 2012, Mike Wilson wrote:
What events are supposed to be fired when the browsing context gets
navigated away before the current page has finished loading, ie before
the load event has been fired?
It's pretty complicated, but the short answer is beforeunload and
unload.
On Fri, 14 Dec 2012, Stan wrote:
First, I don't think it's convenient for users to register themselves on
many sites, which they visit occasionally. If most of the users do this
right now, it does not mean they are happy with this, this is bacause
there is no other, more simple way (as
On Fri, 14 Dec 2012, Stan wrote:
Last thing to remember: the device ID is not something secret and
forbidden for native applications. For example, Android provides Android
ID and iOS ASIdentifierManager, which can be read by any installed
application. Taking into consideration that many
Thanks Ian,
Ian Hickson wrote on 14 december 2012 19:22:
On Fri, 14 Dec 2012, Mike Wilson wrote:
What events are supposed to be fired when the browsing context
gets navigated away before the current page has finished
loading, ie before the load event has been fired?
It's pretty
On Fri, 14 Dec 2012, Mike Wilson wrote:
Anyway, the finding that originally got me started on looking at this
was that I received an unload event without a preceeding load event.
Naively this seems logically wrong, but I appreciate these are
complicated matters so I'm content with the
On Fri, Dec 7, 2012 at 6:38 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Fri, Dec 7, 2012 at 1:23 AM, Anne van Kesteren ann...@annevk.nl wrote:
Well, eventually we might want to merge the whole DOM part of Shadow
DOM and DOM I think, but for now my proposition was that dispatch
On Thu, 6 Sep 2012, Pierre Dubois wrote:
I developed a javascript table parser based on my research. The parser
is able to understand complex relationship in a data table. The
relationship association is based on the current algorithm and take in
consideration how the header cell (th) is
Ian Hickson wrote on 14 december 2012 21:11:
As a general rule, the intent of the spec is that you
get a load when all your scripts (and other resources)
have loaded, and you get an unload when the page is
going away. Thus if the page goes away before the page
has finished loading, you
There are also pageshow and pagehide events,
although the spec for them seems to be wrong.
They are fired always, not only when dealing with session history.
-Olli
On 12/14/2012 08:51 PM, Mike Wilson wrote:
Thanks Ian,
Ian Hickson wrote on 14 december 2012 19:22:
On Fri, 14 Dec 2012, Mike
On Sat, 15 Dec 2012, Olli Pettay wrote:
There are also pageshow and pagehide events, although the spec for them
seems to be wrong. They are fired always, not only when dealing with
session history.
Do you have a test case that shows when they are fired in a way that
doesn't match the spec?
On Thu, 6 Sep 2012, Simon Pieters wrote:
On Wed, 05 Sep 2012 22:47:07 +0200, Ian Hickson i...@hixie.ch wrote:
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1736
Webkit returns undefined, whereas IE, Gecko, and Opera all return an
HTMLCollection. (IE returns an
On 12/15/2012 01:52 AM, Ian Hickson wrote:
On Sat, 15 Dec 2012, Olli Pettay wrote:
There are also pageshow and pagehide events, although the spec for them
seems to be wrong. They are fired always, not only when dealing with
session history.
Do you have a test case that shows when they are
23 matches
Mail list logo
