Comments on: Operator and DOM Mutation Events http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/ Mozilla, money, microformats and more Tue, 15 May 2012 05:27:48 +0000 hourly 1 http://wordpress.org/?v= By: Daniel E. Renfer http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/#comment-248 Daniel E. Renfer Sat, 24 Mar 2007 02:32:04 +0000 http://www.kaply.com/weblog/2007/03/22/operator-and-dom-mutation-events/#comment-248 This is really great. I've been toying around with the idea of writing a few greasemonkey scripts to "inject" microformats into pages that didn't already mark their data up as such. I wasn't sure if Operator would be able to detect those changes or not. Now I know. I guess it's time to start hacking up some javascript. This is really great. I’ve been toying around with the idea of writing a few greasemonkey scripts to “inject” microformats into pages that didn’t already mark their data up as such.

I wasn’t sure if Operator would be able to detect those changes or not. Now I know. I guess it’s time to start hacking up some javascript.

]]> By: mkaply http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/#comment-247 mkaply Fri, 23 Mar 2007 14:30:32 +0000 http://www.kaply.com/weblog/2007/03/22/operator-and-dom-mutation-events/#comment-247 With Firefox 3, there will obviously have to be some better solution to this problem. There needs to be a better DOM message like "Ok it looks like things have settled down, update your content" The only other option is to check the page for changes on a timer... With Firefox 3, there will obviously have to be some better solution to this problem.

There needs to be a better DOM message like “Ok it looks like things have settled down, update your content”

The only other option is to check the page for changes on a timer…

]]> By: Axel Hecht http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/#comment-246 Axel Hecht Fri, 23 Mar 2007 13:28:29 +0000 http://www.kaply.com/weblog/2007/03/22/operator-and-dom-mutation-events/#comment-246 Actually, the events themselves only get generated when there are any listeners, so it's not only the handler code, but internal code that usually shouldn't run. See http://mxr.mozilla.org/mozilla1.8/source/content/base/src/nsGenericElement.cpp. If you already have an extension with mutation event listeners (not sure if firebug does), you'd hardly see. I'm particularly cautious here in the light of fx3' microformats support efforts. In which case, I'd expect you'd have to run Tp against a clean fx. Not that I have any alternative suggestion to using mutation events to have microformats work for ajax pages or something, you'd need content gods to advise there. Actually, the events themselves only get generated when there are any listeners, so it’s not only the handler code, but internal code that usually shouldn’t run. See http://mxr.mozilla.org/mozilla1.8/source/content/base/src/nsGenericElement.cpp.

If you already have an extension with mutation event listeners (not sure if firebug does), you’d hardly see.

I’m particularly cautious here in the light of fx3′ microformats support efforts. In which case, I’d expect you’d have to run Tp against a clean fx.

Not that I have any alternative suggestion to using mutation events to have microformats work for ajax pages or something, you’d need content gods to advise there.

]]> By: mkaply http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/#comment-245 mkaply Fri, 23 Mar 2007 12:53:10 +0000 http://www.kaply.com/weblog/2007/03/22/operator-and-dom-mutation-events/#comment-245 Axel: There does seem to be a slight slowdown with with DOMAttrModified. I might make that a preference so people can decide for themselves. It's difficult to tell though because the page I was messing with was getting slow and fast. Also, I can't see the DOMAttrModified case being as common, but it is extremely useful for debugging. Basically what I'm doing on DOMAttrModified is kicking off a half second time and then returning, and then if I get another event in that timeframe, I reset the timer. Axel:

There does seem to be a slight slowdown with with DOMAttrModified. I might make that a preference so people can decide for themselves. It’s difficult to tell though because the page I was messing with was getting slow and fast. Also, I can’t see the DOMAttrModified case being as common, but it is extremely useful for debugging.

Basically what I’m doing on DOMAttrModified is kicking off a half second time and then returning, and then if I get another event in that timeframe, I reset the timer.

]]> By: Axel Hecht http://mike.kaply.com/2007/03/22/operator-and-dom-mutation-events/#comment-244 Axel Hecht Fri, 23 Mar 2007 11:07:43 +0000 http://www.kaply.com/weblog/2007/03/22/operator-and-dom-mutation-events/#comment-244 Mutation events are said to make pages really slow, do you see that? In either page load or dhtml perf? Mutation events are said to make pages really slow, do you see that? In either page load or dhtml perf?

]]>