On Sun, Oct 31, 2010 at 12:04 AM, shoplifter <[email protected]>wrote:
> I don't understand your concerns with the DOM though, you got 'buffer' > in the DOM with your solution too (in fact nothing more than a global > js var) and addEvent is overwritten anyway when loading mootools. > You're mixing between the DOM and the global object. The DOM is the Document Object Model. It includes, among others, the window and document objects. Modifying the window means that when mootools tries to create the addEvent on the window, It might try to preserve the old one for cross-lib compatibility. Not sure if this is actually the case, but the point is, we shouldn't mix DOM modifing code. Personally, I always make sure that if I do add features to the DOM, I do it with mootools, to make sure I'm not stepping on anyone's toes. The buffer registers on the global object, which is by itself harmless, though should be kept to a minimum. And if you're that concerned, you can create your own mootools build, split up to 2 chunks - the first only containing domready, and the second everything else. -- Arieh Glazer אריה גלזר 052-5348-561 5561
