Content deleted Content added
→Break: case sensitive link, and clear up two uses of the word 'inspect' |
→Break: better example word |
||
Line 138:
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'' may (depending on the developer's intentions) inspect (or query, or read, or
*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, whether it is querying the page structure, or altering it. It is not, ''per se'' 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)
| |||