Comments on: DOM & Prototype: now even faster http://ajaxorized.com/dom-prototype-now-even-faster/ Web Innovation Fri, 21 Nov 2008 05:02:37 +0000 http://wordpress.org/?v=2.1.3 By: Daniel http://ajaxorized.com/dom-prototype-now-even-faster/#comment-3 Daniel Tue, 25 Sep 2007 08:50:52 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-3 I couldn't understand some parts of this article o.us poetry, but I guess I just need to check some more resources regarding this, because it sounds interesting. I couldn’t understand some parts of this article o.us poetry, but I guess I just need to check some more resources regarding this, because it sounds interesting.

]]> By: admin http://ajaxorized.com/dom-prototype-now-even-faster/#comment-4 admin Tue, 25 Sep 2007 08:59:50 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-4 Hi Daniel, The functions above are based on the javascript prototype framework, maybe you should take a look at this at prototypejs.org . Cheers Hi Daniel,
The functions above are based on the javascript prototype framework, maybe you should take a look at this at prototypejs.org .

Cheers

]]> By: zack http://ajaxorized.com/dom-prototype-now-even-faster/#comment-5 zack Tue, 25 Sep 2007 20:55:03 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-5 that's nice, but aren't you duplicating the functionality of Builder? that’s nice, but aren’t you duplicating the functionality of Builder?

]]> By: All in a days work… http://ajaxorized.com/dom-prototype-now-even-faster/#comment-6 All in a days work… Wed, 26 Sep 2007 01:29:19 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-6 [...] DOM and Prototype: now even faster Using these functionse, you will be able to create HTML structures on the fast DOM-lane. [...] […] DOM and Prototype: now even faster Using these functionse, you will be able to create HTML structures on the fast DOM-lane. […]

]]> By: Martijn de Kuijper http://ajaxorized.com/dom-prototype-now-even-faster/#comment-7 Martijn de Kuijper Sun, 30 Sep 2007 19:37:54 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-7 Builder is from scriptaculous, so that's a different framework ;) Builder is from scriptaculous, so that’s a different framework ;)

]]> By: Marshal http://ajaxorized.com/dom-prototype-now-even-faster/#comment-28 Marshal Tue, 06 Nov 2007 14:56:53 +0000 http://ajaxorized.com/dom-prototype-now-even-faster/#comment-28 it is definately quick, but users should keep in mind some of the gotcha's that will bite them if they aren't careful! Microsoft Internet Explorer has a LOT of DOM bugs that will cause failure in you functions (if no precautions are taken). 1.) Adding any inline events (e.g. onclick) will work in all browsers *EXCEPT* IE Bug Link: http://webbugtrack.blogspot.com/2007/08/bug-242-setattribute-doesnt-always-work.html 2.) Setting attributes in IE requires sending in the CaMeLcAsE version of the property name. e.g. 'cellPadding', 'frameBorder', 'colSpan' Bug Link: http://webbugtrack.blogspot.com/2007/08/bug-242-setattribute-doesnt-always-work.html 3.) Setting attributes in IE like 'for' or 'style' won't work either. Bug Links: http://webbugtrack.blogspot.com/2007/09/bug-116-for-attribute-woes-in-ie6.html http://webbugtrack.blogspot.com/2007/10/bug-245-setattribute-style-does-not.html 4.) Setting the 'type' or 'name' attributes in IE will also fail. Bug Links: http://webbugtrack.blogspot.com/2007/09/bug-237-type-is-readonly-attribute-in.html http://webbugtrack.blogspot.com/2007/10/bug-235-createelement-is-broken-in-ie.html Just an FYI! ;-) it is definately quick, but users should keep in mind some of the gotcha’s that will bite them if they aren’t careful!

Microsoft Internet Explorer has a LOT of DOM bugs that will cause failure in you functions (if no precautions are taken).

1.) Adding any inline events (e.g. onclick) will work in all browsers *EXCEPT* IE
Bug Link:
http://webbugtrack.blogspot.com/2007/08/bug-242-setattribute-doesnt-always-work.html

2.) Setting attributes in IE requires sending in the CaMeLcAsE version of the property name. e.g. ‘cellPadding’, ‘frameBorder’, ‘colSpan’
Bug Link:
http://webbugtrack.blogspot.com/2007/08/bug-242-setattribute-doesnt-always-work.html

3.) Setting attributes in IE like ‘for’ or ’style’ won’t work either.
Bug Links:
http://webbugtrack.blogspot.com/2007/09/bug-116-for-attribute-woes-in-ie6.html

http://webbugtrack.blogspot.com/2007/10/bug-245-setattribute-style-does-not.html

4.) Setting the ‘type’ or ‘name’ attributes in IE will also fail.
Bug Links:
http://webbugtrack.blogspot.com/2007/09/bug-237-type-is-readonly-attribute-in.html

http://webbugtrack.blogspot.com/2007/10/bug-235-createelement-is-broken-in-ie.html

Just an FYI! ;-)

]]>