On Wed, 26 Sep 2007, Dan Mosedale wrote:
The escaping specified in
http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers is
slightly different than the escaping done by encodeURIComponent (as
described at
On Mon, Aug 4, 2008 at 3:17 PM, Thomas Broyer [EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 8:33 AM, Garrett Smith wrote:
(3) There is no specification for a special [[Get]] for the elements
HTMLCollection as a shortcut to namedItem, either (though this would not
seem to be a problem,
On Mon, Aug 4, 2008 at 8:24 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
The overall concern is that I think the spec is unnecessarily
complicated. I'll comment in detail below on specific features. An
overall requirement for mozilla is that we are very selective about
which features are exposed
On Mon, 23 Jun 2008, Frode Børli wrote:
1. Which readystate does an img object have, before it is added to the
DOM? Example:
var i = document.createElement(IMG);
alert(i.readystate); // afaict the state SHOULD be uninitialized here...
I would like some input from browser vendors.
Right now, if you navigate an iframe to a document, and take a
reference to a method defined in that document, and then navigate that
iframe to another document, and then call the method, browsers differ in
what they do.
There are several
On Tue, Aug 5, 2008 at 1:12 AM, Ian Hickson [EMAIL PROTECTED] wrote:
Right now, if you navigate an iframe to a document, and take a
reference to a method defined in that document, and then navigate that
iframe to another document, and then call the method, browsers differ in
what they do.
By
On Fri, 13 Jun 2008, L. David Baron wrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas.html#text
has the following bullet point:
# Form a hypothetical infinitely wide CSS line box containing a
# single inline box containing the text text, with all the
#
On Tue, 5 Aug 2008, Aaron Boodman wrote:
On Tue, Aug 5, 2008 at 1:12 AM, Ian Hickson [EMAIL PROTECTED] wrote:
Right now, if you navigate an iframe to a document, and take a
reference to a method defined in that document, and then navigate that
iframe to another document, and then call the
Blarg forward to list.
-- Forwarded message --
From: Tab Atkins Jr. [EMAIL PROTECTED]
Date: Tue, Aug 5, 2008 at 9:15 AM
Subject: Re: [whatwg] Nested lists
To: noclip [EMAIL PROTECTED]
On Mon, Aug 4, 2008 at 8:15 PM, noclip [EMAIL PROTECTED] wrote:
Are there plans to natively
Ian Hickson wrote:
But, oddity is par for the course in DOM, so I guess we'll just follow
the HTML 5 spec as-is, initialize readyState to loading in the object
constructor, and keep our fingers crossed.
If you find any problems with doing this, please let me know, so we can
update the spec!
2. How can we listen to the onreadystatechange, if we want to trigger an
event when the object starts loading? It will not change readystate
since it was already in the state loading.
In HTML5 there's no way to get an event when an img begins loading. It
begins loading when the src= is set.
I'm still digesting the Web Worker proposal, but here is some
feedback. Sorry it is a bit long.
Structural API stuff:
- I still haven't really internalized the need to either have workers
speak directly to anyone other than the person who created them, or
the other use cases that
On Mon, 2 Jun 2008, Matthew Paul Thomas wrote:
The disadvantage of using a data-* attribute is that more kinds of
mistakes would be undetectable by a validator. It would have no idea
that (a) the value of the attribute must be the ID of an element
elsewhere in the document, and (b) each
On Tue, 5 Aug 2008, Jonas Sicking wrote:
2. How can we listen to the onreadystatechange, if we want to
trigger an event when the object starts loading? It will not change
readystate since it was already in the state loading.
In HTML5 there's no way to get an event when an img
On Tue, 5 Dec 2006, Rohan Prabhu wrote:
Dear all,
i was just wondering, that in the Web Controls 1.0 specifications, in
the psuedo classes specifications, could it be that the psuedo classes
could also be the DOM Events which would modify the style information
attached to it. Like for ex:
Aaron Boodman wrote:
I'm still digesting the Web Worker proposal, but here is some
feedback. Sorry it is a bit long.
Structural API stuff:
- I still haven't really internalized the need to either have workers
speak directly to anyone other than the person who created them, or
the other use
Thanks for the quick reply...
On Tue, Aug 5, 2008 at 2:52 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
I know this is weird wrt GC when combined with MessagePorts, and I
don't have a proposed solution.
I don't think we should say much regarding GC at all. All we should say is
that GC should
Ian Hickson wrote:
On Tue, 5 Aug 2008, Jonas Sicking wrote:
Ian Hickson wrote:
But, oddity is par for the course in DOM, so I guess we'll just follow the
HTML 5 spec as-is, initialize readyState to loading in the object
constructor, and keep our fingers crossed.
If you find any problems with
On Tue, Aug 5, 2008 at 8:03 AM, Garrett Smith wrote:
On Mon, Aug 4, 2008 at 3:17 PM, Thomas Broyer wrote:
Actually, there is:
http://www.w3.org/TR/html5/dom.html#htmlcollection
and I believe the elements property of HTMLFormElement is actually
an HTMLFormControlsCollection:
Simon Pieters wrote:
On Mon, 04 Aug 2008 20:21:01 +0200, Jonas Sicking [EMAIL PROTECTED]
wrote:
However if we want to add support for the long list of JS attributes
that exist on a elements today on each and every HTML element I
suspect that is going to get messier. Especially considering
20 matches
Mail list logo
