Nicolás Lichtmaier wrote:
Quote:
Hi, some time ago I've written an article about this issue. It explain
some differences in Explorer's and Mozilla's JavaScript/DOM. It has
recently changed its URL, This is the new one: http://www.reloco.com.ar/mozilla/compat.html
Bye!
PS: I hope it's useful to someone. I would appreciate any comments and
suggestions! |
I read some more your page. Here are additional comments and suggested
improvements or corrections.
1- "and will narrow the posibility of leaving a browser unsupported."
possibility 2 "s"
2- "Another common error is to check if the browser has something, and
if it doesn't to assume that it has another thing."
Suggestion: "Another common error is to check if the browser supports a
method, and, if it doesn't, to assume that it supports a particular method."
Notice the comma ","
3- "This cannot be relied upon. It's better to directly test what one is
going to use." Here, at that point, I would give a "more info" link on
this for visitors willing to know more on the subject, say:
<a href="http://jibbering.com/faq/#FAQ4_26">More info</a>
4- I would avoid negative pejoratism in expressions which do not serve
the purpose of your document.
"the ugly window.event was born", "This window.event, in addition to
being a terrible idea", "let's not forget poor Explorer"
Remember that when event as an object was introduced, there was no W3C
DOM standard and we were in browsers war. The W3C could have chosen for
the MSIE DOM event object but did not. The W3C could have chosen to
support <layer> instead of <div>. There is nothing intrinsically bad,
ugly or terrible about the MSIE event object; it's just that *now* such
event object is not part of W3C web standard DOM 2 event. And we know
that MSIE dev. team would have been happy to implement DOM 2 events but
real os dependent limitations prevented such implementations.
5- Everywhere you use "the same thing" expression, I think you should
look for a more meaningful way to explain things or re-word your sentence.
6- In your bibliography, you give Gecko DOM reference but that
documentation is IMO so poorly written, so weakly written that I would
hesitate *a lot* before giving such reference. How about giving a link to
Using Web Standards in Your Web Pages
http://www.mozilla.org/docs/web-deve...upgrade_2.html
this newsgroup FAQ,
http://jibbering.com/faq/
Peter-Paul Koch cross-browser DOM compatibility page
http://www.quirksmode.org/dom/contents.html#link2
Using the W3C DOM Level 1 Core (about DOM tree, text nodes, etc)
http://www.mozilla.org/docs/dom/technote/intro/
and maybe my own window, event property page?
http://www10.brinkster.com/doctorunc...dowsMSIE6.html
DU