Comments on: DOM Traversal in Firefox 3.5

By: Mozilla Hacks: Przechodzenie po drzewie DOM w Firefoksie 3.5 « marcoos.techblog

Wed, 29 Jul 2009 11:32:25 +0000

[...] serii tłumaczeń artykułów z bloga Mozilla Hacks, przedstawiam dzisiaj tłumaczenie artykułu DOM Traversal in Firefox 3.5 autorstwa Johna Resiga (znanego m. in. jako twórca biblioteki [...]

By: MJiA

MJiA — Mon, 22 Jun 2009 08:13:50 +0000

Should “this.nextSiblingElement.style.display = “block”;” in first code snippet be “this.nextElementSibling.style.display = “block”;
“?

By: 颠覆网络35天 ─ Firefox 3.5中的DOM遍历 < MJiA

颠覆网络35天 ─ Firefox 3.5中的DOM遍历 < MJiA — Mon, 22 Jun 2009 07:41:20 +0000

[...] 原文地址：DOM Traversal in Firefox 3.5 系列地址：颠覆网络35天 [...]

By: Erik

Erik — Sat, 20 Jun 2009 10:07:20 +0000

In the list of API functions you call a function ‘nextElementSibling’, but in the example it is ‘nextSiblingElement’. Which one is correct?

By: Ajaxian » NodeIterator.areYou(IMPRESSED | WHOCARES | WHA?)

Ajaxian » NodeIterator.areYou(IMPRESSED | WHOCARES | WHA?) — Fri, 19 Jun 2009 19:05:58 +0000

[...] Resig has posted on the DOM traversal methods now in Firefox 3.5 and then a spin out post on the merits of the NodeIterator API. He isn’t impressed: This API is, [...]

By: Илья Казначеев

Илья Казначеев — Fri, 19 Jun 2009 16:16:34 +0000

“This has long been a bane of web developers” until there were Prototype, and now it’s down().
Why bother bloating DOM when it’s already figured out?

By: Elijah Grey

Elijah Grey — Fri, 19 Jun 2009 16:05:19 +0000

Should the document type only have a .nextSibling property and not a .nextElementSibling property? document.firstChild.nextSibling === document.documentElement and document.firstChild.nextElementSibling === undefined for me.

By: John Resig - Unimpressed by NodeIterator

John Resig - Unimpressed by NodeIterator — Fri, 19 Jun 2009 15:53:01 +0000

[...] just posted a run down of some of the new DOM Traversal APIs in Firefox 3.5. The first half of the post is mostly a recap of my old Element Traversal API [...]

By: Gilberto Ramos

Gilberto Ramos — Fri, 19 Jun 2009 14:43:03 +0000

looks very useful!

By: steve

steve — Fri, 19 Jun 2009 14:38:55 +0000

yikes! ignore me… I somehow read that all wrong… pulling in the word “all” from elsewhere in the sentence… oh Internet Eraser.. where are you when I need you!

By: Horia Dragomir

Horia Dragomir — Fri, 19 Jun 2009 14:38:47 +0000

I remember these issues with Nodes vs. Elements used to be a great pain back before the great frameworks rules the internet. Oh, I remember them well…

Aside from the comfort that comes with this enhancement, I’m guessing there might be an increase in speed and dependability too, right?

Let’s just see how fast the other browsers implement this.

By: steve

steve — Fri, 19 Jun 2009 14:36:31 +0000

I thought that the document.all collection in IE wasn’t a live collection? e.g. when I add new elements to the DOM (after page load) with id/name attributes they aren’t necessarily added to the collection.

Or am I missing something with regards to how IE is being handled before fully supporting this?