I totally understand, I have some very critical things happening here, for now I can can provide you with some very helpful links that explain it well.
textContent is a DOM3 property
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-...
http://www.quirksmode.org/dom/w3c_html.html#t07
just click the test page on that second link and you'll see.

Keep up the good work! I absolutely forgot websites had text ads until i came across the bookmark to this website as i was reorganizing my bookmarks. It reminded me to update your awesome script. I appreciate this script so much!!!

I was wondering why you don't use the textContent property. I think many script writers either don't know about it or don't want to remove BR tags. Since TextAd scripts replace text which should never have any BR tags, I can't imagine why it would ever be a problem here.

Thanks Grant, I'll certainly check it out.

I wasn't upset because you didn't reply, I was frustrated because I couldn't get any definite answer as to whether DOMNodeInsertedIntoDocument fires or when it fires. I know what the W3C says but Mozilla says nothing.

Your comment led me to a different solution.

That doesn't indicate if you even considered my suggestions at all, and you left DOMNodeInsertedIntoDocument in while nobody at all complained that it didn't work, (for a week from Feb 21 there are no comments between mine and yours).

I'm glad you cleared that all up. And you explained the situation nicely. Perhaps I just lost patience too soon.

I forgot about that issue with iterators, but I wasn't really looking at that part yet - I was looking at what I noticed wasn't working. You can certainly just use ORDERED_NODE_SNAPSHOT_TYPE and create a loop getting each snapshotItem()

Your EchoTopic code works fine, I just noticed that you could do it in one line.

The code I posted using document.createTextNode mostly saves you the trouble of trying to figure out which node the text is in. Seems more strait-forward to me.

I discovered Greasemonkey because of this script, and I can't remember the trouble I had to go through to find greasemonkey-mod which works in SeaMonkey.
I stayed here and became a member to offer some support. If anyone doesn't want my help then I just leave, I could care less what any users think, especially those that continue to support sites which insist on flooding their screen with ads they don't want.

Thanks for the great update Grant. Life would be unbearable without my Grease Monkey and your script.

@Descriptor
Glad to see you are gone. Grant has always been reliable and kind. If you come here without patience, make demands and basically act like an A$$#ol3, then good riddance. We all celebrate your departure.

Thanks, Grant!

I am very relieved to see the this update. These ads are spreading fast and they're really annoying. A forum I read uses a "free" host that just added text ads. So every post on the forum has random double-underlined links sprinkled through it!

Total eyeball abuse.

Well, I'm though commenting here. I upgraded SeaMonkey and 'DOMNodeInsertedIntoDocument' still does not fire, while 'DOMNodeInserted' works fine. I knew upgrading wouldn't make any difference because it uses the same Gecko version as Firefox.
Since you don't seem to want to discuss why you used that, or verify that is works... I'm gone... I can make it work on my own.

  // This seems to work for EchoTopic
  unsafeWindow.tf_maxKeywords = 0;

Tried it here: http://www.gamershell.com/news/45382.html

While researching this I (we) discovered a (new?) bug: in DOMNodeInsertedIntoDocument

DOMNodeInsertedIntoDocument does not work at all.
If the text ad is two words like Windows <nobr>XP<img..., then the former code works correctly.
If it is one word, no event is fired.
It may be because DOMNodeInserted is not fired by innerHTML, but I haven't yet found the intelitext script that adds the link. Still looking, there's a bunch. Also the ads appear randomly, and are kinda hard to find, sometimes there are none anywhere.
You can use this, which is helpful

document.addEventListener("DOMNodeInserted", function(){document.title="DOM Changed at " + new Date()}, false);

OK, I haven't checked this yet, but the reason I wrote it the way I did is because they add a nobr and an image tag to the text node, the nobr is the first child - you can see it isn't there if you look at the page source.
I don't know when they added support for DOMNodeInsertedIntoDocument or if that works yet in Seamonkey. I'm no expert with Events, but I'm learning. I'll let you know...

I just updated to version 8.0 yesterday, because of Linkworth text ads. However, on this page:
http://donthatecasey.blogspot.com/

I see that the first link is removed, but all subsequent links are not (i.e. the word job in strikeout text is removed, but the next paragraph still has the word 'funny' as a linkworth text ad.) Is there any way to fix the script for this case?
Thanks... keep up the good work.

In case it isn't obvious, that should be inside the load event handler.

No, it doesn't work there, another good reason not to visit that site. The DOMNodeInserted event isn't fired until after the intellitxt script has already run, you can see it fire when you mouse-over, so those links aren't removed. I didn't look at their script to see why.

var itxtdid = document.evaluate("//a[@itxtdid]", document, null, 6, null);
for(var i=0; i < itxtdid.snapshotLength; i++){
itxtdid.snapshotItem(i).parentNode.replaceChild(
    document.createTextNode(itxtdid.snapshotItem(i).textContent), 
    itxtdid.snapshotItem(i));
}

I just went back the PC Mag link and they have added this now: and the word HDTV shows an ad if you mouse over it.
I think this is what you refer to as a text link ad.

Thanks,
Stan

Thanks for checking. Yes, the text ad on the PC Mag site is now gone. The OpenAds seemed like a text ad as it came up when I move the mouse over the text. It must have just been a timing thing.