-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 12, 2008, at 8:46 AM, liorean wrote:
On 12/03/2008, Boris Zbarsky [EMAIL PROTECTED] wrote:
I guess I could do the two interfaces, but I'm having a hard time
seeing
different extensions being made to these two interfaces (as
opposed to
On 12/03/2008, Boris Zbarsky [EMAIL PROTECTED] wrote:
I guess I could do the two interfaces, but I'm having a hard time
seeing
different extensions being made to these two interfaces (as
opposed to wholly
new interfaces being invented, as was done here).
On Mar 12, 2008, at
Sorry, I didn't know what mailing list to send this to, hopefully I
caught some knowledgable people with this:
html
object data=http://some.other.domain/example.svg; param
name=foo value=bar//object
/html
From within foo.svg, shouldn't I be able to get access to the
parameters sent to the
On Thu, 13 Mar 2008 19:03:27 +0100, Jeff Schiller [EMAIL PROTECTED]
wrote:
html
object data=http://some.other.domain/example.svg; param
name=foo value=bar//object
/html
From within foo.svg, shouldn't I be able to get access to the
parameters sent to the object? This fails when the SVG
Jeff Schiller wrote:
Fx3 does not allow you to do this:
setting a property that has only a getter
That's because per the spec document.domain is readonly. See
http://www.w3.org/TR/SVG11/struct.html#InterfaceSVGDocument.
There is a workaround in place for HTML documents (even though the
On Thu, 13 Mar 2008 19:41:56 +0100, Boris Zbarsky [EMAIL PROTECTED] wrote:
That's because per the spec document.domain is readonly. See
http://www.w3.org/TR/SVG11/struct.html#InterfaceSVGDocument.
There is a workaround in place for HTML documents (even though the
property is readonly per
Jeff Schiller wrote:
I'm not well-versed on the history behind document.domain and how the
web depends on it being writable. Can someone send me a pointer?
I can understand not letting the embedded object get at the elements
outside of the HTMLObjectElement, but this seems like a weird design
I agree with Jonas that something on the Windows object would be the
best way to go. Boris suggested a set of key/value string pairs.
Would it be an associative array?
http://www.w3.org/TR/Window/#window-embedding - for window.name, I
note that it says Need to describe how this could come from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So just to clarify:
Your expectation is that the querySelectorAll API will be wrapped by
JavaScript libraries for the foreseeable future?
As a JS library author, it was my sincerest hope that I could get out
of this particular pool.
Regards
On Wed, 12 Mar 2008, Boris Zbarsky wrote:
javascript:var n =
document.createElement(div);n.appendChild(document.createElement(span));alert(n.querySelector(:root
span));
Webkit nightly returns null. IE throws (no :root support). Gecko
prototype implementation returns the span,
On Fri, 14 Mar 2008 05:24:45 +0900, Jonas Sicking [EMAIL PROTECTED] wrote:
I can understand not letting the embedded object get at the elements
outside of the HTMLObjectElement, but this seems like a weird design
flaw - the object parameters should be accessible to the embedded
object,
Ian Hickson wrote:
Webkit is correct. The Selectors spec defines :root as:
The :root pseudo-class represents an element that is the root of the
document.
OK. It wasn't obvious to me whether that was because people hadn't considered
matching against disconnected subtrees or whether
Hi, Folks-
Hallvord R. M. Steen wrote (on 3/13/08 10:08 PM):
On Fri, 14 Mar 2008 05:24:45 +0900, Jonas Sicking [EMAIL PROTECTED] wrote:
The proper fix here is IMHO to add something to the window object. So
that you don't have to reach out into documents that are from a
different domain.
On Thu, 13 Mar 2008, Boris Zbarsky wrote:
Ian Hickson wrote:
Webkit is correct. The Selectors spec defines :root as:
The :root pseudo-class represents an element that is the root of the
document.
OK. It wasn't obvious to me whether that was because people hadn't
considered
On Thu, Mar 13, 2008 at 11:24 PM, Ian Hickson [EMAIL PROTECTED] wrote:
Yeah, I was just jumping in to clarify the :root thing. Personally I think
you're right, it would be useful to have the method on DocumentFragment,
I agree.
but that's up to Lachlan. :-)
Fully disagree.
--
Robert
Hi, Takeshi-
Thanks for your feedback.
KUROSAWA, Takeshi wrote (on 3/12/08 9:10 AM):
Element Traversal Spec uses attribute word at ECMAScript Language Biding[1].
firstElementChild
This read-only attribute is of type Element.
But it is prefered to use property rather than attribute in
Boris Zbarsky wrote (on 3/13/08 3:11 PM):
It would have
been great if HTMLObjectElement had an accessible params NodeList
readonly attribute :(
Yes, indeed. It's not too late to add that!
Boris, do you mean that it's not too late to add that to Fx3? What
about window.paramList?
It's
How do you define the Intranet, Internet, Restricted etc zones?
Without correct definitions for these zones it seems possible to attack
intranet servers by sending unsafe (such as POST or DELETE) requests to
intranet servers from internet pages.
I'd also recommend sending this to the web
www-style: the discussion is about the :root selector in the Selectors
specification.
Yeah, it really should say a document.
That doesn't solve the problem, in some ways, since it might mean that multiple
nodes being rendered in the same window match :root, depending on what
transclusion
19 matches
Mail list logo
