Standards and CSS in IE


Recommended Posts

I found this today on IE blog ....

In IE7, we will fix as many of the worst bugs that web developers hit as we can, and we will add the critical most-requested features from the standards as well. Though you won?t see (most of) these until Beta 2, we have already fixed the following bugs from PositionIsEverything and Quirksmode:

Peekaboo bug

Guillotine bug

Duplicate Character bug

Border Chaos

No Scroll bug

3 Pixel Text Jog

Magic Creeping Text bug

Bottom Margin bug on Hover

Losing the ability to highlight text under the top border

IE/Win Line-height bug

Double Float Margin Bug

Quirky Percentages in IE

Duplicate indent

Moving viewport scrollbar outside HTML borders

1 px border style

Disappearing List-background

Fix width:auto

In addition we?ve added support for the following

HTML 4.01 ABBR tag

Improved (though not yet perfect) <object> fallback

CSS 2.1 Selector support (child, adjacent, attribute, first-child etc.)

CSS 2.1 Fixed positioning

Alpha channel in PNG images

Fix :hover on all elements

Background-attachment: fixed on all elements not just body

I want to be clear that our intent is to build a platform that fully complies with the appropriate web standards, in particular CSS 2 ( 2.1, once it?s been Recommended). I think we will make a lot of progress against that in IE7 through our goal of removing the worst painful bugs that make our platform difficult to use for web developers.

Full Article : http://blogs.msdn.com/ie/archive/2005/07/29/445242.aspx

Sounds great!

Link to comment
Share on other sites

This is great news. I'm not sure why they waited until after the release of IE7 beta1 to clarify their position on CSS2 support.

In previous comments they've always been guarded about their precise intentions in complying to CSS standards.

I'm looking forward to being able to use CSS's more advanced features. I can see light at the end of the tunnel.

Link to comment
Share on other sites

I'm very glad to hear this. Now maybe everyone who was bashing IE7 because of it's continued problems can just SHUT UP. As I (and many other people) have said from the beginning, this is beta 1!

Everyone started crying and saying "this is all we're going to see, IE sucks, it'll never support the standards!" but you were all wrong. :laugh:

Link to comment
Share on other sites

This should probably be in BPN because... let's see...

It just made 1000's of web designer's lives easier.

586300136[/snapback]

:yes:

Very good news. :D Now my theory on "When you get two browsers working the other one breaks" theory won't be as true. ;)

This will make coding much easier. :D

Link to comment
Share on other sites

What will people say when IE7 ends up being more compliant than Firefox?  Oh, what a great day that will be!  :yes:

586300266[/snapback]

Either way, any improvement in IE's page rendering is a good thing. ;P

Link to comment
Share on other sites

Couldn't they release an update tot he IE6 engine as well for CSS 2.0 support?

586300277[/snapback]

IE 7 will be an update to IE6. :D

Link to comment
Share on other sites

I'm sure it would be possible, but there is really no reason to do so.

586300448[/snapback]

Yes, but think about all the windows users who have IE 6, and won't be getting an IE7 upgrade, they would all have browsers that aren't compliant with CSS 2.0.

Link to comment
Share on other sites

Yes, but think about all the windows users who have IE 6, and won't be getting an IE7 upgrade, they would all have browsers that aren't compliant with CSS 2.0.

586300534[/snapback]

You're exactly right. But the fact is, they're using unsupported software. If they want CSS 2.0 compliance, they need to either get with the times, or use a different browser.

Link to comment
Share on other sites

You will comply IE7. Then Ill consider switching back from FF.

586300578[/snapback]

So IE7 needs to comply, before you will consider switching back from a browser that's currently non-compliant? :unsure:

Link to comment
Share on other sites

You're exactly right.  But the fact is, they're using unsupported software.  If they want CSS 2.0 compliance, they need to either get with the times, or use a different browser.

586300569[/snapback]

So i suppose it's feasible to just upgrade a organization's computers to XP or greater, just so they can get the new version of IE? When everything is working perfectly fine with the OS and that's all they need?

Link to comment
Share on other sites

So i suppose it's feasible to just upgrade a organization's computers to XP or greater, just so they can get the new version of IE? When everything is working perfectly fine with the OS and that's all they need?

586300670[/snapback]

Why would anyone upgrade just for IE? If the browser is that big of a deal, then use Firefox or something.

Link to comment
Share on other sites

Umm... IE 7 is exclusively for XP and 2k3.

586300529[/snapback]

Oh yeah huh. I forgot. :whistle:

But people should be using XP now. I mean its been out since 2001.

Link to comment
Share on other sites

Why would anyone upgrade just for IE?  If the browser is that big of a deal, then use Firefox or something.

586300772[/snapback]

It's not only that, think about all the home users out there, the ones who won't upgrade, or god knows how to upgrade to firefox or is aware of another browser (we're talking about people who really know nothing about computing).

If you were a web developer, awesome IE7 is out, CSS 2.0 compliant, and web developers take the step to developing sites that are fully CSS 2.0 without their hacks, then what about their viewers? They'll still have to apply those hacks or do some browser detection just to support for those IE 6.0 users.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.