Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: incrediBILL
Internet Explorer 9 Preview [winsupersite.com]
The company explained this week that it examined how similar sites actually tax browsers in different ways--some are script-heavy, for example, while others are not--and its architecting IE 9 to handle these different needs properly.
Microsoft has taken a lot of flak for its lackluster adherence to web standards, but the company appears ready to reverse that reputation in IE 9.
"We've moved the IE rendering engine from GDI to DirectX."
As an early Alpha build they still have a lot of work to do on this product. It is nice to hear that they are moving forward with IE development and not letting it stagnate like they did in the past. Standards compliance would be nice!
More specifically, this means adhering to the latest web standards, such as HTML 5 and CSS3 Selectors. At the keynote, there was a demo with CSS-based rounded corners in an element border. That's very specific, of course, but it's something that IE 8 doesn't do properly today. The current, very early IE 9 version correctly utilizes 41 of the 43 CSS Selectors and scores 574 out of 578 in its CSS3 Selectors test, a big improvement over IE8, which scored 330 out of 578.
It's not like Microsoft has a tradition to keep up in sticking with numbering releases: Win 3; win3.1; win95, win98, ME, NT3.5, NT4, 2000, XP, 2003, 2008, Vista, win7 (which identifies itself as ... 6.1 sigh).
Why not just call it IE8 build 9876.54 so people aren't afraid of upgrading.
Right now we're already forced to deal with 3 different versions of IE, each with their own unique set of bugs and features that never seem to get fixed.
unless they are ready to get rid of all of them out there, they should focus on fixing the old ones instead of adding a fourth to the list.
We've seen plenty of promises with every version it would be different this time, only to discover after a while it's going to be yet another instance of the same. Even IE8 still has "hasLayout" in IE8 mode: where is that property mentioned in the CSS2.1 standard over at w3.org?
On the list of HTML5, CSS3: add SVG, it's far more important than ActiveX, DirectX, VML, backward rendering modes and whatnot they stuffed in that browser!
Now Microsoft just appear to want to push out the numbers. I think someone in the marketing department wants IE X out asap because it sounds cool.
My personal view is that only major builds should get a whole number. And I don't mean the underlying technology, I mean how it looks and performs from an end user point of view. I think ie8 should still be ie6. Something.
IE8 should render a page the same way as IE6
IE8 should render a page the same way as IE6.
No! Browsers that render pages the same way as IE6 should DIE.
Maybe it's utopian, but browsers that respect standards will make things easier on us in the long run.
Microsoft has taken a lot of flak for its lackluster adherence to web standards, but the company appears ready to reverse that reputation in IE 9...
More specifically, this means adhering to the latest web standards, such as HTML 5 and CSS3 Selectors. At the keynote, there was a demo with CSS-based rounded corners in an element border.
My emphasis. You can't have it both ways and I for one would like to get rounded corners with .htc files (among other items on my IE laundry list).
Above all, I don't want four different box models and code riddled with conditional comments for IE. And yes, I understand, updates to IE mean *more* conditional comments in the short run.
Anyway, IE6 is finally dying. I just checked some stats for a site that was designed to render fine in IE6 and has a very non-techy demographic. IE6 is under 9% of visitors. A substantial number, but less than Safari. Almost that many Chrome users actually.
On a more tech-oriented site, I only have 3% IE6 visitors (and only about 8% IE7) and both Chrome and Safari are above that and Opera is close.
In other words, I'm not saying they will live up to the hype, just trying to answer the previous poster as to why there's no way future versions of IE should be rendering everything like IE6.
IE8 Acid3 test... 20%
IE9 Acid3 test... 32%
Google Chrome Acid3 test... 100%
I mean, come on!
General IE9 support specs...
Windows XP: Not confirmed
XHTML: Not confirmed
CSS3 Selectors: confirmed
CSS3 Properties: one property confirmed
Additionally any one who pays attention to Opera knows about Vega and thus any one who's read about Vega and noticed Microsoft showed up to an SVG event a couple months ago knows that we're likely to see additional CSS3 properties beyond border-radius.
90% of the complaints I've seen are not substantiated; the only thing any one has said that is agreeable at this point in regards to IE9 is that what we've been previewing is nothing new to other browsers.
On top of that Microsoft more then has enough resources to implement all the missing standards and not simply cherry-picking what they deem to be worth supporting.
That's the whole point of IE9; to get IE to where Firefox and Safari are.
Promises: I ain't buying it anymore. Deliver first on what was already promised, then I'll believe (maybe).
Microsoft knows SVG support is critical. They already have VML so it's not like they don't already have something they can rework. Also they've showed up last minute at a big SVG meeting a couple months ago. I doubt we'll see full support of any of the existing SVG standards; we're likely to see reasonable support for it.
Why XHTML? Is anyone here actually creating XHTML pages served up as application/xhtml (otherwise it's really just HTML with obligatory closing tags isn't it)? If not, is it because of inadequate browsers?
Honestly, I don't speak XML and I really don't keep up on this sort of thing anymore. I think of XHTML as pretty much a failed experiment and HTML5 as showing a lot more promise for a usable web in the long run.
So at the risk of exposing my ignorance, why should I care about XHTML? Or actually, wrong question - why should I prioritize XHTML 1.? support over HTML5?
In addition it means the content can be parsed as if it is xml: I can use tools to manipulate xml at will on my xhtml to e.g. make changes on a site wide scale that I failed to anticipate in my server side includes: I can still do them easily enough no matter how complex the get without having to rely on a html parser.
html5: there is still xhtml5 as well. so you do not have to choose between xhtml and html5: you can have both.