be nice for all methods that return NodeLists. As
NodeLists are live, adding a contains method, and a modification event
to the NodeList interface should cover all you need and much more.
--
Sjoerd Visscher
http://w3future.com/weblog/
should say PASS.
(Note that I'm ignoring that you say that you load this file though a
DATA attribute. I don't think it should matter how the markup has come
into existence.)
--
Sjoerd Visscher
http://w3future.com/weblog/
t's fine if this is supported, as long as
it can be turned off.
--
Sjoerd Visscher
http://w3future.com/weblog/
the
user, but please let is be up to de web developer to act responsible
with the features he has available. Who wants to annoy the customer anyway?
--
Sjoerd Visscher
http://w3future.com/weblog/
have different
types in different locations in the document.
--
Sjoerd Visscher
http://w3future.com/weblog/
t the
basic site framework, and the client will read the query string and go
to the sales department part.
--
Sjoerd Visscher
http://w3future.com/weblog/
Dean Edwards wrote:
Sjoerd Visscher wrote:
Sjoerd Visscher wrote:
Dean Edwards wrote:
Charles Iliya Krempeaux wrote:
To be honest, the think the idea of "drawing transactions" is
better. Here are the reasons:
#1: It makes it so, if the develop wants it, that they can have t
Sjoerd Visscher wrote:
Dean Edwards wrote:
Charles Iliya Krempeaux wrote:
To be honest, the think the idea of "drawing transactions" is better.
Here are the reasons:
#1: It makes it so, if the develop wants it, that they can have things
that are "drawn" show up immed
OK, I'll shut up about non scripting languages, I don't know anything
about them.
Charles Iliya Krempeaux wrote:
Hello,
On 6/15/05, Sjoerd Visscher <[EMAIL PROTECTED]> wrote:
Christian Biesinger wrote:
Sjoerd Visscher wrote:
Christian Biesinger wrote:
Sjoerd Vissche
Christian Biesinger wrote:
Sjoerd Visscher wrote:
Christian Biesinger wrote:
Sjoerd Visscher wrote:
This isn't needed. Just like in normal HTML a drawing transaction is
automatically started when the javascript code starts
Are the functions JavaScript-specific?
Ehm, no. Actuall
endering has been implemented for years. I don't think that will
change, and so canvas has to play with the same rules.
--
Sjoerd Visscher
http://w3future.com/weblog/
Christian Biesinger wrote:
Sjoerd Visscher wrote:
This isn't needed. Just like in normal HTML a drawing transaction is
automatically started when the javascript code starts
Are the functions JavaScript-specific?
Ehm, no. Actually the automatic drawing transactions story applies to
Dean Edwards wrote:
Charles Iliya Krempeaux wrote:
From what I undestood (from what Sjoerd Visscher was saying), is that
there is no need for "drawing transactions" because of the way things
are done with JavaScript and the DOM.
Thanks for the very good explanation o
is done. And this is how it is implemented in
Firefox (don't know about Safari).
Maybe the spec should describe this somewhere? Not specifically for
canvas, but for script in general: Changes on the DOM must be performed
instantly, and values like offsetWidth etc. must be recalculated, but
e something that requires authors to use it properly...
Why? People write browser/standard specific things all the time. If it
works for them, who cares?
I like this proposal because it actually solves the original problem,
without a need for Google to change their accelerator code.
--
Sjoe
hat it can be
cached. Setting the read state should be done seperately with POST.
Most e-mail clients only mark an item read when it's open for a few
seconds, it's a bonus that you can do that too.
--
Sjoerd Visscher
http://w3future.com/weblog/
.
Does this make any sense?
I think it does, I really like it. It is comparable with allowing the
src attribute on any element, as XHTML2 is doing.
--
Sjoerd Visscher
http://w3future.com/weblog/
17 matches
Mail list logo
