is ie8 REALLY this shitty?
 

My worker was just doing some css for me, and a very simple page was crashing IE8 completely on both my computer and his (no plugins running on either). It turned out that it was being caused by an unclosed h2 tag... I can understand it rendering incorrectly, but completely crashing the browser on two computers? Putting it into quirks mode crashed it was well on both.

Anyone else run into any issues like this? This was not complicated javascript/css/jquery etc. This was just very simple vanilla css.

Yes... it's that shitty and FF is working hard to compete with it for the shittiest browser title. :P

What's wrong with FF? I never have any problems with it.

I've had issues with it taking up alot of ram, and stuff like that but never crashing because of an unclosed h2 tag... Microsoft should just give up on IE. They can't seem to get it right. As much as it hurts to say, IE7 rendered CSS the best out all the versions of IE and they just it alot worse with IE8. There is of course the emulate ie7 mode in ie8 which you can set with a meta tag or head tag in htaccess, but that crashes ie8 half the time to begin with.

Yes IE8 is really that shitty.

IE8 is the largest single handed piece of anything that holds back progress on the Internet for developers... Just ask any dev or (X)HTML/CSS guy about IE6...

Then take a look at this:

http://a.deveria.com/caniuse/

Scroll to the bottom and you'll see IE8 comes in at a whopping 28% by FAR the lowest score...

Internet Explorer sucks... period.

Use Chrome, it's the fastest browser with the fastest JS parsing times. JS Animations look the smoothest hands down...

i also found ie8 was crashing many times per day, it seems it was the flash component it tries to automatically install when visiting a site with flash, had to uninstall, and goto adobe.com and install it, fixed the issue.

I don't think I've seen IE8 crash due to an unclosed tag. I also use the IE7 render meta tag in all of my sites and none crash in IE8. It's not my browser of choice but it's the browser I use when debugging asp.net applications and I rarely have any problems with it. And then it's just a quick check to see if everything is fine in FF and it usually is. I'm curious to see the markup which caused the crash.

Yes :)

I will try to get my worker to recreate the issue tomorrow, but it was definately consistant. It crashed ie8 on his computer, my computer, and my laptop as well.

Yup, IE8 is shit. But better make sure your sites fly on it cuz surfers don't know about how much shity it is.

ie8 also blows up images a little and makes them smoother..... i noticed it when i was testing a new site... i never use IE8 so thats why i never knew... but why do they do this? They also smoothen text, i did know that, but i never noticed the images... it slightly fucks up a design when its background images with real text on them.

IE sucks, all versions!

FF is going down the shitter too. It'll always be better than IE but it looks like Chrome is about to take the lead.

IE8 sucks, but it got zoom option for a bigger font, it's nice when you on a laptop... chrome doesn't have that (at least I didn't find it)

No it is not IE8 it 100% has to do with the way your site is coded. if it is done properly then there is no reason for an <h2> tag to crash.

If a site is done 100% properly it will look the same in all browsers also.

i do not know why people blame browsers when their site is not coded properly.

You are missing the point man. People make mistakes, like forgetting to close a tag.

I absolutely understand if the site were to render incorrectly.

However, in this case this unclosed tag completely froze up and crashed IE8 on 3 different computers. This means that it is a bug in IE. Screw my site, the bigger picture here is that an invalid tag or quirks mode any little bullshit that should just be ignored by the browser completely locks it up and makes the program crash.

ie8 is pretty good.

id say fast and very safe.

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.

Since the day I took my computer out of the box IE has never worked right and would crash/freeze the browser upon opening it.

You think so? i prefer FF

:helpme no it won't because none of the browsers agree on what 100% proper is. You can downgrade your site so it looks similar on all browsers.

Btw all ie versions starting from version 6 can produce same problem.For example i had once aliment totaly screwed in IE beacuse i had <div align="center" >instead <center>.There is plenty of examples where html/css code works perfectly fine in FF/Opera while is screwed in IE.

I still use FF because it rocks for developers, but for just browsing I'd definitely prefer Chrome. It's a LOT faster and doesn't crash at all, at least on my system.

It's probably shittier.

I love Chrome and use it as my primary browser, but it seems to struggle / glitch hard while
a) downloading items
b) with youtube

Anyone else see this? I haven't seen anything in the bug forums about it, and I've upgraded everything I can.

never use IE, just a tip...

:2 cents::2 cents:

you can code in strict and there is certain ways of adjusting CSS to fit in all browsers.

there is multiple ways to do code. when you use different combos you end up with a perfect site in all browsers.

even for ie6 (i would rather pull in another style sheet) you can use padding instead of margins and it should be the same. <<this part i am not 100% as i said i normally call in a seperate style sheet to changes parts because its easier if i do ie6 at all.

its small things like margin bottom not working in IE so you add padding top to the element below.

what do you do you mean "downgrade"?

then it's not the same . strict html will result in different look in diff browsers unless you make specific changes for certain browsers.
features in browsers that are not strict html compliant. You have to give those up in order to have strict compliance, i.e downgrading your site so it looks the same if you follow strict html.

Ok, I will try it

i've been using chrome for the past 3 weeks and i think im falling in love with it.

they dont make that shit for surfers anymore

I feel you pain. The sooner people leave IE version whatever (and after IE6 tons left) the better for the global Web community.

Why can't MS get their shit straight? IE is 'something like a big deal' you would think they would get a team of people with a brain to remodel it or something.. is there some kind of benefit they're getting from not validating like every other modern browser?

FF is turning into a mem hog but I still like it better than rest of the browsers.

BS. I make sure all my code is perfect and validates and often there are issues when viewed in more than once browser they do not render the same - especially heavy XHTML and CSS.

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'.