[woodcreeker]

Okay the string does cause validation errors. (I checked an XHTML Markup Validator)

All those errors are refering to is "...this error can create cascading effects" This is more of a warning than a real error, I firmly believe that, but it could cause parsing errors for just a few, but most can safely run this on their forums with no ill effects.

I know you guys are pure coders, and that is awesome. (I wish I had the time, been programming my whole life, off and on, about 30 yrs). I interpret that error "flag" as a warning, and this may be the actual nature of how this hack works. I actually forgot about it for a couple of years!

Ol' Wise One, like I said above, Boofo (and I am acknowledging you, too, Jase2 and djpassion) I still do hear you guys!! You guys deserve a lot of respect. There is so much wrong in a lot of the code we work with in the first place when it comes to XHTML, it takes numerous hours to hunt it all down and fix all of it.

If anyone on my forums complains, I will just pull it back out. I doubt it, but I only make small changes here and there, so I can easily go back and fix any problems that crop up. For now, I am leaving it in, and I am sure it will work fine. Takes just a second to pull it out, anyway.

My final code on this hack to eliminate most (if not all) XHTML validation errors.

<meta http-equiv="page-enter" content="blendTrans(Duration=0.2)"/>
<meta http-equiv="page-exit" content="blendTrans(Duration=0.2)"/>

Some Validators may simply warn you about these statements, and not give you true errors. I am not going to go through a bunch of those code debuggers, anyway, to get to the heart of the problem, if there is one.

Boofo, I wasted an hour screwing around (LOL) and I didn't really want to on this, but that is okay. Sometimes I like to putz around. I actually found a couple of errors I forgot to double-check !

Hang In There, Good Luck and Stay Cool Guys !!