Navneet Kumar's Library tagged DOM → View Popular

Filter:
All
Annotated

19 Feb 09

John Resig - Talk: The DOM is a Mess

ejohn.org/the-dom-is-a-mess - Preview

DOM JavaScript Browser Cross-Browser

18 Feb 09

Migrate apps from Internet Explorer to Mozilla - MDC

differences between IE and FF
DOM, CSS, JS

developer.mozilla.org/...m_Internet_Explorer_to_Mozilla - Preview

Browser Browser_Issue Mozilla InternetExplorer DOM

JavaScript tutorial - DOM nodes and tree

www.howtocreate.co.uk/...dombasics - Preview

HTML DOM JavaScript

In Opera 7-9.2x, this maximum text node size is 32 KB. In Mozilla/Firefox/Netscape 6+, it is 4 KB. Although
the normalize() method of the parent node(s) should be able to replace the multiple text nodes with a single text node
containing all the text,

10 Feb 09

John Resig - XPath and CSS Selectors

ejohn.org/...xpath-css-selectors - Preview

XPATH CSS DOM DOM_Traversal

The biggest thing to realize is that CSS Selectors are, typically, very short - but woefully underpowered, when compared to XPath.

Native XPath is blazing fast
Internet Explorer is a dead-end.
1 more annotations...
- These implementations are black boxes that are unable to be modified by the developer (leaving them vulnerable to browser bugs)

DOM Parsing With XPath and JavaScript | Wed 20 Apr 2005 | Blog | CodeStore

dom node traversal in javascript using xpath

www.codestore.net/...BLOG-20050420 - Preview

JavaScript XPATH DOM

JavaScript XPath Implementation

dom node traversal in javascript using xpath

js-xpath.sourceforge.net/ - Preview

JavaScript XPATH Library DOM

document.evaluate method:
Msxml.DOMDocument

JavaScript-XPath – CodeRepos::Share – Trac

dom node traversal in javascript using xpath

coderepos.org/...JavaScript-XPath - Preview

JavaScript XPATH DOM

04 Feb 09

Building High Performance HTML pages

msdn.microsoft.com/...ms533020.aspx - Preview

DOM WebPage MSDN HTML Performance

Close Your Tags
will be parsed more quickly because it is well-formed and Internet Explorer doesn't need to look ahead to decide where the paragraph or list items end.

15 Jan 09

Looks Good Works Well: Measuring User Experience Performance

Web page load cycle
request - respose - load

looksgoodworkswell.blogspot.com/...er-experience-performance.html - Preview

Performance UX DOM JavaScript

01 Oct 08

XPCNativeWrapper - MozillaZine Knowledge Base

kb.mozillazine.org/XPCNativeWrapper - Preview

XPCNativeWrapper XPCOM Mozilla Firefox DOM

05 Sep 08

Gecko DOM Reference - MDC

developer.mozilla.org/...Gecko_DOM_Reference - Preview

Gecko DOM Reference MDC

DOM - MDC

developer.mozilla.org/DOM - Preview

Mozilla MDC DOM

31 Jul 08

Tutorial:DomQuery v1.1 Basics - Learn About the Ext JavaScript Library

css selectors

extjs.com/...Tutorial:DomQuery_v1.1_Basics - Preview

Javascript CSS DOM

11 Dec 07

Document Object Model Events

www.w3.org/...events.html - Preview

dom javascript w3c

28 Aug 07

John Resig - Bringing the Browser to the Server

ejohn.org/...ging-the-browser-to-the-server - Preview

dom javascript rhino

the full jQuery test suite is now automated and capable of running in Rhino
(passing all tests).
It's important that you do window.location = "some file" before loading any
DOM-dependent code (as the 'document' object doesn't exist before the location
request

21 Jun 07

DOM Scripting: The innerHTML dilemma

domscripting.com/35 - Preview

dom innerhtml javascript

innerHTML is very well-supported
It’s a super-simple way of taking the responseText property of the XMLHttpRequest object and slapping it into a specified part of a page.
5 more annotations...
- specific situation where innerHTML can let you down. If you serve up your XHTML with an XML mime-type, you can’t use innerHTML.
- MochiKit has a pretty nice functional system of shortcuts for generating DOM structures to replace those 20 lines of createElement() / appendChild() calls.
- Imagine XHTML with multiple namespace, I think innerHTML will fail to have consistent cross-browser output.
- innerHTML is faster than DOM "createElement" methods.
- Use of innerHTML is recommended if your need is one way. That is, you are just presenting content, after which you are "done." However, if you need to refer/traverse a DOM branch that you are changing, then you should use "createElement" DOM methods.