This problem still exists in 1.4.5 so I have logged it as an issue in github:
https://github.com/mootools/mootools-core/issues/2362 I was going insane trying to find out where this "foo</foo></" junk was coming from... never occurred to me that mootools would be doing it until logic determined only javascript could reliably create the exact same garbage injection that isn't present when viewing source... and google hit this thread! I guess you could just test for IE by another method first and skip these IE behavioral tests when it's not even a candidate. But probably there are more elegant ways of reworking all that testing for mootools people who know about all these browser differences. Sadly, I don't know enough about cross-browser differences and how best to test them, but I could probably submit some kind of clumsy patch if nobody else wants to fix this. I understand that most people care more about telling humans their markup is XHTML with little badges, than telling the browser and letting it parse it as such. But injecting invalid markup into an XML DOM is unforgivable; this is a serious issue for us XHTML pedants :P Cheers! -Will On Sunday, 27 February 2011 15:09:35 UTC, rpflo wrote: > > I looked last night, it's still there in 1.3.1. Looks like it's > mitigating IEs selection of closing tags without open tags. > > If that's the case (which it might not be) seems like its value is > debatable. > > On Feb 27, 2011, at 7:14 AM, Fábio M. Costa <fabio.co...@corp.globo.com> > wrote: > > @Garret, > > Did you try mootools 1.3.1 and got the same error? > > > -- > Fábio Miranda Costa > frontend@portalpadroes > Globo.com > *github:* fabiomcosta > *twitter:* @fabiomiranda > *ramal:* 6476 > > > > On Sun, Feb 27, 2011 at 10:55 AM, Christoph Pojer < > christoph.po...@gmail.com> wrote: > >> @Garret please wait for an answer from Fabio or someone else on the >> MooTools team familiar with this issue and don't get distracted by random >> comments. I don't have any clue or the time currently to look into this >> issue. If you could put up a simple example site that highlights the issue >> that would help too. > > >
