Lachlan Hunt:
> It seems from the Java bindings section of Web IDL that the way to
> define modules and how they're mapped to Java packages isn't yet very
> stable.
>
> http://dev.w3.org/2006/webapi/WebIDL/#java-modules
Right, it’s not stable yet.
> I'm hesitant to include the module declara
On Fri, 21 Nov 2008 17:28:34 +0100, Hallvord R. M. Steen
<[EMAIL PROTECTED]> wrote:
var xhrConstructor = iframe.contentWindow.XMLHttpRequest;
iframe.src='http://attackee.example.com/';
.
.
var xhr = new xhrConstructor();
When the constructor is invoked here, the associated document of its
a
http://www.w3.org/TR/XMLHttpRequest/#document-pointer says
When the XMLHttpRequest() constructor is invoked a persistent pointer to
the
associated Document object is stored on the newly created object. This
is the
Document pointer. The associated Document object is the one returned by
the
Cameron McCormack wrote:
Kartikaya Gupta:
What namespace does the Selectors-API IDL belong to? This determines
the java package (org.w3c.dom.???) that the NodeSelector interface
will go in, and is needed for java implementations. Even if it's just
the top-level namespace (i.e. the org.w3c.dom p
Stewart Brodie wrote:
This is considered to be a bug in the DOM Core specs, which will
hopefully be fixed by Web DOM Core, which is a proposal Simon Pieters is
working on.
You will still need a new type, as I don't see how you can possibly change
the existing behaviour so dramatically under th
Stewart Brodie wrote:
You will still need a new type, as I don't see how you can possibly change
the existing behaviour so dramatically under the feet of existing content.
I would not like to lose the liveness property of node lists, as it would
make NodeList objects incredibly memory ineffici
Gavin Kistner wrote:
I find these names rather cumbersome and not very self-explanatory.
I agree.
Though it may be far too late for this suggestion, I would suggest that
they should be something such as:
findNode()/findNodes() or findNode()/findAllNodes()
selectNode()/selectNodes() or sele
Lachlan Hunt <[EMAIL PROTECTED]> wrote:
>
> Gavin Kistner wrote:
> > DOM Level 2 Core and DOM Level 3 Core both say:
> > "The NodeList interface provides the abstraction of an ordered
> > collection of nodes, without defining or constraining how this
> > collection is implemented. NodeList objec
Gavin Kistner wrote:
On Nov 19, 2008, at 11:02 AM, Boris Zbarsky wrote:
Gavin Kistner wrote:
Section 6 states:
"The querySelector() method ... must ... return the first matching
Element node ***within the node’s subtree***." [1]
"Even though the method is invoked on an element, ***selector
Gavin Kistner wrote:
The second example in section 8 uses the following code:
var x = document.querySelector("#foo, #bar");
It goes on to rather explicitly state, "In the sample document above, it
would select the div element with the ID of foo because it is first
***in document order***" (
Gavin Kistner wrote:
DOM Level 2 Core and DOM Level 3 Core both say:
"The NodeList interface provides the abstraction of an ordered
collection of nodes, without defining or constraining how this
collection is implemented. NodeList objects in the DOM are live." [1] [2]
" NodeList and NamedNod
Gavin Kistner wrote:
The Selectors API document, section 8, has this example code:
var div = document.getElementById("bar");
var p = bar.querySelector("body p");
I assume that is supposed to be either...
var div = document.getElementById("bar");
var p = div.querySelector("body p");
...o
Hi Larry,
On Fri, Oct 31, 2008 at 3:01 PM, Larry Masinter <[EMAIL PROTECTED]> wrote:
> Hi all,
> I think there is considerable interest in a broad community in the topic of
> ZIP based packages, specifically MIME types for them and intra-package URI
> references within them, and possibly for stand
13 matches
Mail list logo
