Dean Edwards wrote:
It would be great if NodeLists were subclasses of JavaScript Array
objects (especially with the introduction of Mozilla's Array Extras
[1]). This makes iteration over DOM queries more flexible.
It sounds like a nice idea, but there are some problems with it that I
can
On 5/11/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Shadow2531 wrote:
object type=text/html data=about:blank
scriptalert('You should not see this!');/script
/object
What should happen in situations like that?
The script element is alternate content.
The object is rendered.
The script
On 11/05/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Dean Edwards wrote:
It would be great if NodeLists were subclasses of JavaScript Array
objects (especially with the introduction of Mozilla's Array Extras
[1]). This makes iteration over DOM queries more flexible.
It sounds like a nice idea,
Quoting Dean Edwards [EMAIL PROTECTED]:
On 10/05/06, Jorgen Horstink [EMAIL PROTECTED] wrote:
I just had a little chat with Anne and he thinks a rendering change
event (ie: before printing, generate a table of contents) will be usefull.
I think he is right.
I suggested
Shadow2531 wrote:
That problem could be avoided by authors making sure each
document.write() wrote complete element markup instead of splitting it
up like in your example.
The problem could be avoided by not using document.write() at all, but
in reality that's not going to happen any time
Some code to illustrate:
// old way
var isChecked = false;
var inputs = document.getElementsByTagName(input);
for (var i = 0; i inputs.length; i++) {
if (inputs[i].type == checkbox inputs[i].checked) {
isChecked = true;
break;
}
}
// better (using iterators on NodeList)
var isChecked =
On 11/05/06, Anne van Kesteren [EMAIL PROTECTED] wrote:
My suggestion would be to have a renderingMode event (or something
like that) which in some way exposes a mediaList of the current
rendering modes (mostly just one). If you go to print preview mode for
example the event is dispatched and
On 5/11/06, Dean Edwards [EMAIL PROTECTED] wrote:
On 11/05/06, Anne van Kesteren [EMAIL PROTECTED] wrote:
My suggestion would be to have a renderingMode event (or something
like that) which in some way exposes a mediaList of the current
rendering modes (mostly just one). If you go to print
On 11/05/06, Anne van Kesteren [EMAIL PROTECTED] wrote:
My suggestion would be to have a renderingMode event (or something
like that) which in some way exposes a mediaList of the current
rendering modes (mostly just one). If you go to print preview mode for
example the event is dispatched and
On May 10, 2006, at 11:47, Jorgen Horstink wrote:
I just had a little chat with Anne and he thinks a rendering change
event (ie: before printing, generate a table of contents) will be
usefull. I think he is right.
Such a thing (as well as print CSS) can be used in an obnoxious way
to
- Original Message -
From: Dean Edwards [EMAIL PROTECTED]
To: whatwg [EMAIL PROTECTED]
Some code to illustrate:
// old way
var isChecked = false;
var inputs = document.getElementsByTagName(input);
for (var i = 0; i inputs.length; i++) {
if (inputs[i].type == checkbox
11 matches
Mail list logo
