IE7 browser share and IE8 hints
Apologies to all for the delay between posts, the site authors are busy with jobs, family and holidays. We’ll have some new content very shortly. In the meantime, here’s a quick browser update.
Based on my own statistics - and these are not, of course, meant to be in any way representative - April saw a pretty decent leap for IE7; its share of the market rose to 21.1%, up from 18.6% the month before. Even more encouraging, IE6 fell to 46.5% after its shock rise to 50.6% last month.
Firefox’s share continues on a slow decline since I began my figures; from a high of 16.9% in November, it falls to 14.8% in the latest figures.
Microsoft were noticeably guarded with details of changes in future versions of IE at their recent MIX event, although hints were dropped that we’d see improvements to CSS, RSS, and AJAX, and that Microformats could be on their way.
In an effort to tie this post to the theme of this blog, let me ask a question: what three CSS3 features would you most like to see in IE8?
Update: Maybe I should reword the question: With the presumption that all outstanding CSS2 bugs are removed, and all remaining CSS2 declarations implemented, what CSS3 features would you most like to see in IE8?
Is it Christmas ?
3 features…mmm :
- Multiple Background Image
- CSS3 selectors
- Opacity (to finally drop filter:Alpha…)
And can I have a little CSS2 feature ?
- display: table/table-cell …
It would be great.
I’ve noticed IE7 to be about 35%+ on some rather big sites. I’m surprised your IE stats are that high for a blog about CSS. Slashdot’s has something like 66% using FireFox, another 5% Safari and I’m not sure about Opera, Konquerer and IE.
Actually, I’d like the CSS *2* features of generated content and tables. It’ll be the nine year anniversary of CSS 2 next Saturday. It would be nice to get a reasonable implementation of it Internet Explorer before the specification is a decade old.
I wish they’d just fix the bugs. IE 7 is full of bizarre render bugs that show up in unpredictable situations, and in different ways than IE 6.
Working around three bug-ridden browser versions would be too much for me. I’d rather it be two bug-ridden browsers and one bug-free browser even if it means worse CSS support.
Mind you, Microsoft had the resources to make a bug-free, CSS 2 compliant browser 5 years ago. The fact that they haven’t yet shows they really don’t take much pride in IE and are content to coast with their near-monopoly.
*All* the selectors, multiple backgrounds and rounded corners. This will make my HTML much cleaner. (and of course, as Country said, everything css2).
I don’t think IE will ever fully support CSS; there are some things, such as generated content, they just don’t seem to be interested in. Plus, if your browser supports the same standards as everyone else, why would someone choose yours? Better to support standards up to a point and then ignore the rest and create your own…
@zest: Those stats aren’t from CSS3.info, they’re an average from eight different websites I manage, from a personal blog to a large international company. Two of those sites have very high IE usage, as most big businesses still install IE by default.
multiple backgrounds
selectors
calc values
Real opacity (not based on filters, because they sometimes make text go blurry) and Generated Content.
And I don’t understand why do you ask for features that are not available even in Firefox / Opera or even in Safari (Webkit). First things first, eh? ;)
- Multiple backgrounds
- Css 3 selectors (especially the form-specific pseudo-selectors, :checked, :disabled, etc.)
And I’ve become very excited to calculated values after your previous article, I can’t wait to see that in action.
On another note; it would be nice to FINALLY see some support for the ABBR and Q elements.
Don’t see it as important to ask for CSS3 features that exists in other browers because they are more likely to quickly follow up.
Better that a browser that doesn’t get updated that freaquently pushes the adaptation forwards then allways doing catchup two years later than the rest.
* not buggy all CSS 3 selectors
* fix most CSS issues
* implement CSS 2.1 fully
: Fix current CSS inconsistencies
: Flow text onto multiple columns
: Make all selectors work
1. full, non-buggy support for :nth-child in all its forms
2. opacity
3. display: icon
that’d sort out many things, at the very least: data table background shading on alternate rows; use of 24-bit png graphics for drop shadows on container edges against a patterned background image; better image replacement techniques.
the :nth-child() could be used in so many other ways. Possibly leading to a sudden surge in complex CSS modules, no doubt! the ability to get rid of inline classes and more ids would make HTML coding practice map to HTML coding ideals.
Microsoft show us their true face in their ignorance, their biggest mistake was to abandon their browser.
Their users want them to fix their browser, if not… Well lets make them want it, by eliminating support for outdated browsers.
[...] last time I conducted a poll like this, back in May 2007, the total market share of all versions of IE stood at approximately 68%. According to my new [...]
[...] Поменялись доли версий браузеров в общем объеме. В прошлом году IE6 составлял 46,5%, а IE7 – 21,1% от общего объема рынка [...]
1) Rounded corners
2) CSS Selectors
3) Opacity
1) CSS3 selectors
2) Rounded corners
3) multiple backgrounds and/or border-image