Comments on: DOM Scripting is brittle http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/ I have nothing to say and I say it. Fri, 03 Sep 2010 02:01:16 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Dustin Diaz http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/comment-page-1/#comment-13 Dustin Diaz Sat, 30 Sep 2006 23:22:44 +0000 http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/#comment-13 Threre was some talk about extending the DOM Collection util to have a getElementsBySelector or a getElementsByXPath. Both would be pretty nice. Threre was some talk about extending the DOM Collection util to have a getElementsBySelector or a getElementsByXPath. Both would be pretty nice.

]]> By: wioota http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/comment-page-1/#comment-11 wioota Sat, 30 Sep 2006 01:37:37 +0000 http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/#comment-11 Hi again Dustin, Not sure how its structured at Yahoo! but any number of developers at my company may edit the templates. The issue as I see it is there is low visibility on what DOM structures are dependencies for JS. This is rarely an issue for small teams but becomes an issue when a maintenance task can accidentally disable Javascript functionality. QA would find it but then we are back to writing more DOM search routines. Use of the 'getElements*' series of functions that the JS community has contributed allows us a bit more room to move but doesn't really guarantee that what we are looking for will still be found. The whole exercise seems unproductive and makes me think there has got to be a better way. Jquery has xpath support built in - its been awhile since I have played with XPath but maybe it has the simplicity and the expressiveness I am after? I guess it would be straight-forward to expand the YAHOO.util.Dom module to implement XPath as well. Hi again Dustin,

Not sure how its structured at Yahoo! but any number of developers at my company may edit the templates. The issue as I see it is there is low visibility on what DOM structures are dependencies for JS. This is rarely an issue for small teams but becomes an issue when a maintenance task can accidentally disable Javascript functionality. QA would find it but then we are back to writing more DOM search routines.

Use of the ‘getElements*’ series of functions that the JS community has contributed allows us a bit more room to move but doesn’t really guarantee that what we are looking for will still be found. The whole exercise seems unproductive and makes me think there has got to be a better way.

Jquery has xpath support built in – its been awhile since I have played with XPath but maybe it has the simplicity and the expressiveness I am after? I guess it would be straight-forward to expand the YAHOO.util.Dom module to implement XPath as well.

]]> By: Dustin Diaz http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/comment-page-1/#comment-10 Dustin Diaz Fri, 29 Sep 2006 17:31:31 +0000 http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/#comment-10 The best way to tackle these kind of routines is to target HTML collections. It is indeed tempting to put id's on everything, but it gets exhaustive and bloated. Try doing things like Dom.getElementsByClassName or just simply document.getElementsByTagName. Then again, you have to question who's messing with your template. If it is in fact the clients themselves... well that road gets scary even for the "internet savvy" folks who think they know what they doing. Once you give a client access to throw HTML into a content area - anything could happen. The best way to tackle these kind of routines is to target HTML collections. It is indeed tempting to put id’s on everything, but it gets exhaustive and bloated. Try doing things like Dom.getElementsByClassName or just simply document.getElementsByTagName.

Then again, you have to question who’s messing with your template. If it is in fact the clients themselves… well that road gets scary even for the “internet savvy” folks who think they know what they doing. Once you give a client access to throw HTML into a content area – anything could happen.

]]> By: John http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/comment-page-1/#comment-9 John Fri, 29 Sep 2006 05:30:30 +0000 http://blog.wioota.com/2006/09/28/dom-scripting-is-brittle/#comment-9 Thats the point, I agree. But realistic: "the pretty moving, pulsating, bevelled corner DIVs" making the world go round! Thats the point, I agree. But realistic: “the pretty moving, pulsating, bevelled corner DIVs” making the world go round!

]]>