Ok, then issue 1 is unresolved. I like the :scope idea, but then the UA
could imply :scope before each selector.
Thank you all.
Na , Lachlan Hunt [EMAIL PROTECTED] escreveu:
João Eiras wrote:
1) How do we deal with node.querySelectorAll(foo) ?
should this be considered a valid
Unless the page raises another dialog of course
For that there are popup blockers.
The user must click something for another popup to open.
2008/4/29, Bjoern Hoehrmann [EMAIL PROTECTED]:
* João Eiras wrote:
The user can easily and quickly close the dialog and then the main
tab. Two
Na , Ian Hickson [EMAIL PROTECTED] escreveu:
This is a first draft. It has issues, I'm sure. Let me know what I should
fix...
Hi!
What happened to the 3rd parameter (sFeatures) ?
http://msdn2.microsoft.com/en-us/library/ms536759.aspx
This parameter is needed to specific the window
I think you're making a big effort trying to come up with a meaningful
solution. However, it can get much complicated than that.
Lets say you magically implement a solution which would be impossible
for a client side script to detected if any 3rd party website was
accessed.
I still can do the
Hi.
You can make a huge effort specifing and implementing such behavior
for the selectors API. But then getComputedStyle is simultaneously
affected by this issue, so either the behavior for both APIs has to be
specified, or we're simply wasting our time and bandwidth.
2008/4/16, Stewart
It does not make sense to be only an object, because you can only have
instances of functions and the instanceof operator requires a function
on the right hand side. That ff3 thing might be a regression.
2008/3/18, Travis Leithead [EMAIL PROTECTED]:
From the spec...
4.2.1. Interface object
For Opera you can use a mix of css content rules with data urls, to
load content inside an element, and keeping it hidden from the dom. I
don't know however, if it'll fit your usecases.
2008/3/7, laurent [EMAIL PROTECTED]:
Hi Sergey,
This is a great work, congratulation !
However, your
if (document.querySelector) {
// Supported
} else {
// Not suported
}
Too bad that only works with ecmascript.
Such syntax is not valid in other languages.
It would probably be better to add the event listeners before setting the
href attribute, because if the image is cached, the UA might very well
load it synchronously, or the load timeout might not be enough until the
load listener is added.
Garrett Smith [EMAIL PROTECTED] escreveu:
2007/8/21, liorean [EMAIL PROTECTED]:
On 21/08/07, Simon Pieters [EMAIL PROTECTED] wrote:
We'd rather have the members of HTMLDocument that are useful for all
types
of documents to be moved to the Document interface. This would probably
be:
* location
* URL (also present in
Is there any proposed API to get information about installed fonts in the
client at runtime ? something like navigator.plugins or navigator.mimeTypes
The current XMLHttpRequest WD states that the XMLHttpRequest interface
implements the EventTarget interface
http://www.w3.org/TR/XMLHttpRequest/#xmlhttprequest
In DOM 3 Events, the EventTarget interface defines 5 methods
http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTarget
Na , Anne van Kesteren [EMAIL PROTECTED] escreveu:
On Tue, 13 Feb 2007 20:08:53 +0100, João Eiras [EMAIL PROTECTED]
wrote:
The current XMLHttpRequest WD states that the XMLHttpRequest interface
implements the EventTarget interface
http://www.w3.org/TR/XMLHttpRequest/#xmlhttprequest
In DOM
I too have a question.
If I'm downloading say 50kb, how many times will the progress event fire ?
Now if I'm downloading 1MB how many times will it fire ?
I doubt it'll fire every byte, else listening for this event will consume
enormous amounts of cpu. I too doubt it'll fire every kilobyte,
Maciej Stachowiak [EMAIL PROTECTED] escreveu:
and somewhat unclear about what the method really does (sounds like
Selectors would mean you give it an array of selectors or otherwise
pass more than one).
Excuse me, but get/getAll falls deeper in this category.
Na , Simon Pieters [EMAIL PROTECTED] escreveu:
Hi,
On Thu, 25 Jan 2007 19:26:38 +0100, Anne van Kesteren [EMAIL PROTECTED]
wrote:
So the WG just discussed in a little over an hour a counter proposal to
the current naming[1] and came up with:
* getElementBySelectors()
*
Shadow2531 [EMAIL PROTECTED] escreveu:
On 12/31/06, João Eiras [EMAIL PROTECTED] wrote:
So, my question is, what's the reason for not wanting win t+b(2) to
fire?
The load event doesn't bubble, so it fires with the Document as
target, and doesn't go up. But compatibility with the current web
So, my question is, what's the reason for not wanting win t+b(2) to
fire?
The load event doesn't bubble, so it fires with the Document as
target, and doesn't go up. But compatibility with the current web
demands this.
2006/12/31, Shadow2531 [EMAIL PROTECTED]:
On 12/29/06, Bjoern Hoehrmann
Thank Bjoern,
so, so far I've undestood this, regarding the load event:
1) the window is a target to which event listeners can be dispatched,
different from the document
2) a capturing load event listener in the window will only fire once,
during the load event dispatch for the document
3) a
Hallvord R. M. Steen [EMAIL PROTECTED] escreveu:
On Thu, 28 Dec 2006 16:33:43 +0100, Bjoern Hoehrmann [EMAIL PROTECTED]
wrote:
It also means that a
window.addEventListener('load', func, true);
listener would never be triggered. Presumably that should be changed
to say that it would be
20 matches
Mail list logo
