Quote:
Originally Posted by MetaMan
No you are missing the point, it is guaranteed a combination of poorly coded CSS WITH your unclosed tag. 1 unclosed H2 tag is not going to send things into haywire.
the bigger picture is a lot of people claim to be able to code in CSS when they really have no business doing so in the first place.
you are cussing out a browser that works perfectly fine and is actually an advancement of IE7 instead of placing blame where it belongs. that is what i am trying to explain.
"ie8 REALLY this shitty?" no it is not, coders who dont know what they are doing are.
|
No, it's still you missing the point man.
Shit css and unclosed tags should cause the page to render fucked, not completely crash the browser. No matter what i do, i should not be able to crash the browser with html code. I should be able to shit on my scanner, smear it around, put it through an OCR program to convert it to text, and load that as html in the browser without crashing it if i wanted to.
Do you not realize the implications of this? A fucked up iframe or rogue piece of javascript that ie8 suddenly decides it does not like (despite working in ie7 and other browser) completely locking up IE8? One bad iframe on your site could be crashing users computers because of 'invalid html' or 'poor css'.