The SitePoint News Wire returns Monday, but I couldn’t wait to post this link.
Microsoft has provided a detailed list of CSS changes in the upcoming Internet Explorer 7 (the release candidate for which is believed to be imminent).
Related posts:
- How to Override Inline CSS Styles Inline CSS can be applied to any HTML element using...
- Techy Treasures #5: Fudging CSS Counters in Internet Explorer CSS Counters are a useful but under-used feature of CSS2...
- Introducing CodeBurner: the SitePoint HTML & CSS Reference Tool for Firebug CodeBurner is a new Firefox addon from SitePoint that integrates...
- Google Chrome Frame: the Technical Details Google's Chrome Frame announcement has been surrounded by hype, fabrication,...
- Will IE8 Be Enough to Save Internet Explorer? Internet Explorer's share of the browser market has slipped each...
Cue the sarcastic applause for Microsoft.
August 24th, 2006 at 1:39 pm
Meh. Microsoft. So 1990’s. FireFox all the way!
August 24th, 2006 at 5:32 pm
meh… firefox… so yesterday. safari all the way!
August 24th, 2006 at 6:48 pm
goddamn mac fanboys, theyre everywhere!
August 24th, 2006 at 11:00 pm
hmm i read thru the blo post, its quit an impressive list, nice to know MS are making steps in improoving IE which will make our life easier down the road as IE7 will be a force upgrade for most users
August 24th, 2006 at 11:08 pm
Who wants to bet that with all these fixes that new and unique bugs will surface.
August 25th, 2006 at 12:51 am
Actually, I will applaud for Microsoft, unsarcastically.
This is a great list to see. Would all of us like to see more? Sure. But the list of render bugs fixed is impressive, and there’s some key CSS features I’m stoked about. PNG support, min/max width/height, fixed positioning, :hover for arbitrary elements – these are great!
August 25th, 2006 at 1:38 am
I’m glad that IE7 will be an forced auto-update, will probably make our lifes a lot easier.
What missing features would you like to see implented in IE7?
I’d like to see more selectors in the CSS parser, more accurately more pseudo-classes, like :before :after (and if not already implented) :first- and :last-child
August 25th, 2006 at 2:07 am
I’d like to see the :first and :last child selector issue too. I think that could provide all sorts of advantages. Is there a reason it wasn’t ever done (please refrain from offensives…)?
August 25th, 2006 at 11:40 pm
If you look at the list and think about it and then you look back at the old beta before the RC1 which could be release build of horror…
Come on ppl, its a small step for browser mankind but huge leap for “70% of market share will force of update”.
That was the best news in a month.
August 29th, 2006 at 8:35 am
Oh man! No way, just FireFox for me.
August 29th, 2006 at 6:54 pm
Critical, but not forced, hannson. And certainly not for anyone pre- XP SP2. There are even still a good many ‘98 users still out there. I’m also glad for the upgrade in their urgency, but mass adaptation could still take a while.
September 14th, 2006 at 2:06 pm