We need to do what the xml-contentsink does and give special attention to <meta> tags. See above url for the content-sink code

I don't think we should fix this. The only thing that mozilla really handles is REFRESH, and I consider running XSLT on a refresh kinda harmful. And when should we fire the timer? on start of the transform, on end? Guys, XSLT === lag, this 'feature' can cause the app to hang.

I don't understand how this could be harmfull? I guess setting the timer to 0 and refreshing to the same url can make the app unresponsive, but that is effitiently the same as using the js-interface in a endless loop. Ideally I think we should start the timer once the document is fully loaded, but if we're so slow that it matters then we have bigger problems then this :-) Anyway, my patch in bug 123343 fixes this too

fixed with the checkin of the patch in bug 123343

we didn't verify for a long time. I really checked, so VERIFIED.