Content deleted Content added
m →Explaining what the DOM is without being vague: good stuff, though I don't have time to work on the whole article |
→Explaining what the DOM is without being vague: Back on this after a break |
||
Line 135:
::::But if you're alright with my latest revision of the introductory section, I'll go ahead and add it once I've found some references? The w3c document you linked might be useful for some of it, but unfortunately until HTML5 the specification didn't even address the inner workings I refer to.
::::--[[User:Qwerty0|Qwerty0]] ([[User talk:Qwerty0|talk]]) 06:01, 31 December 2011 (UTC)
===Break===
I've just found this again, having forgotten it for a few months. I see neither of us actually did much in the end at the time. I've just reverted an edit by {{user|TheBoothy}}. I'll explain why in steps as it's all pretty relevant to what we were saying above.
*'Web browsers '''usually''' use an internal model similar to the DOM' - there is no reason why they have to, internally, as long as they fulfil the DOM's interface when scripts make calls on it.
*'...and to inspect or modify a Web page using JavaScript code' Browsers don't 'inspect or modify' a Web page using JavaScript. The JavaScript is external to the browser, written by a web developer as part of some webpage, and ''it'' inspects or modifies the page's DOM.
*When we say 'JavaScript sees...', that isn't sloppy English for 'JavaScript inspects...'. The script 'sees' the page via its [[interface (Computing)]]; that is good technical grammar. It is not an inspector of things.
I hope this will be clearer when somebody has a good go at writing a proper clear explanation. --[[User:Nigelj|Nigelj]] ([[User talk:Nigelj|talk]]) 00:15, 18 March 2012 (UTC)
| |||