IEBlog 2010: Connecting With You
Same Markup and Hardware Accelerated
Two IE9 themes we emphasized repeatedly during 2010 were same markup and hardware-accelerated rendering (42 of 137 posts used the phrase “same markup” while 26 mentioned “hardware accelerated”). We underscore these because we believe it is these two attributes, along with overall DOM and JavaScript performance, that will most distinguish the HTML5 Web sites and applications of the future. By being able to use the same HTML, CSS, SVG, and JavaScript markup and code across browsers, more Web developer time can be spent delivering new end-user value while less is spent dealing with annoying differences between browsers. By building on a hardware-accelerated graphics platform using new features such as SVG, <canvas>, and CSS3, developers will be able to deliver the kinds of experiences designers dream of—experiences such as those showcased at our Beauty of the Web site.
Where Next?
For sure, we’ll be writing a lot more about IE9 in the weeks and months to come. We hope the information presented in IEBlog is useful and actionable. What information on this blog do you find most valuable? We want your feedback on the IEBlog itself. How can we make this a better resource for you?
The feedback you provide us through your comments is valuable as we assess where to go next with Internet Explorer as well as the IEBlog itself. Thank you for your support during 2010 and here’s looking forward to a great 2011!
—Ted Johnson for the Windows Internet Explorer Engineering Team
Comments
Anonymous
January 05, 2011
I’m looking forward to the Release Candidate version of Internet Explorer 9. I hope that IE Team can get it done as soon as possible.Anonymous
January 05, 2011
I’m looking forward to the Release Candidate version of Internet Explorer 9. I hope that IE Team can get it done as soon as possible.Anonymous
January 05, 2011
> How can we make this a better resource for you? Sometimes, information that are related to IE are published on other MSDN blogs or the blo9gs of some of your developers. It would be very useful if you had a section like "Elsewhere" that lists such articels. Or maybe something like the planet.mozilla.org or planet.webkit.org summarization.Anonymous
January 05, 2011
I'd like to know more about the research you're doing -- user studies, automated reporting and so on. I'd also like to know what are your ideas for the future of browsers and the web. Are you going to move your platforms (esp. Silverlight) towards HTML5-based apps? How will you make browsing smarter?Anonymous
January 05, 2011
How about a build with the HTML5 File API? Or perhaps just acknowledging that this is a huge part of the HTML5 browser experience, instead of constantly and consistently ignoring it?Anonymous
January 05, 2011
The comment has been removedAnonymous
January 05, 2011
@Chris Hynes: I filed a ticket at the IE comments site and they closed it stating that it won't be available in IE9. It's a big miss, but certainly I rather see a working browser with no new bugs instead of trying to push too many features and then break things that used to work.Anonymous
January 05, 2011
@AlfonsoML: IE6 and even 5.5 on some platforms are still supported for critical security fixes. I didn't call out IE6 in this post simply because we didn't talk about IE6 enough for it to make the word cloud of the top 150 terms. FYI: "IE6" occurred just 18 times in all the posts of 2010.Anonymous
January 05, 2011
The comment has been removedAnonymous
January 05, 2011
The comment has been removedAnonymous
January 05, 2011
I hate to repeat this here but once a post on the IE blog is not the latest post it gets ignored. Can someone from Microsoft please make a statement about shutting down the IE6/IE7/IE8/IE9 images at http://www.spoon.net/ ====================================================================================================== This was THE most useful resource for testing multiple versions of IE and the shutdown really ticked developers off! As a long time web developer of Enterprise Web Applications I've tried all the options out there to try and simplify testing IE and the lack of realistic options is a royal PITA. 1.) Multiple IEs - IE8 breaks the functionality of IE6's textboxes - thus its a NO-GO 2.) IETester - works great until you need to test popup interaction and then it fails - thus a NO-GO 3.) Virtual PC with timebombed images of IE6, IE7, IE8 - works ok, but the 12Gigs of HD space needed is frustrating when each full image of Windows dies 4 times a year, running a full Windows image is slow and you have to beg for updates because the releases are not co-ordinated and announced well at all - thus its a NO-GO 4.) IE Super Preview - Last I checked this did not allow full testing of IE user interaction, JavaScript DOM changes, popups etc. - thus its a NO-GO 5.) Multiple PC's to run multiple versions of windows and IE. With all the hardware, software, and physical space needed - its a NO-GO 6.) Spoon.net IEs - They work, they work just like local native apps once running, and there's no hacking of my real local IE install. - the ONLY problem with these IE's is that Microsoft shut them down Please understand that we (developers) just want something that works. Testing in multiple versions of IE is a pain to begin with and with IE9 on the horizon it is only getting worse. I'm not sure where the issue stands with Spoon, but I would really like a solution worked out fast. SteveAnonymous
January 05, 2011
First of all, I'm loving the regular blog updates. IE has come a long way. Secondly, every day I wish someone would reply to my feedback on Microsoft Connect: connect.microsoft.com/.../622551Anonymous
January 05, 2011
I would rather you actually work on improving your horrible browser than blog about improving your browser. Who knows, maybe your blog would render better in IE then.Anonymous
January 05, 2011
The comment has been removedAnonymous
January 05, 2011
@Steve - hopefully the days of IE6, IE7 and IE8 are soon behind all web developers, I certainly was glad when my company dropped support for 6. But at some point you are going to have to decide when to stop supporting them, though few and far between I still found some IE4 and IE5 requests in our 2010 logs. You don't have to block them but by this point they probably know that they are running an old browser.Anonymous
January 05, 2011
@Alison: Thank you for your thoughtful and actionable feedback. I agree with nearly everything you suggest and will see what aspects we can address in 2011. With regard to (j), it is simply not our policy to comment on anything beyond what we're currently shipping or demo'ing publicly. The frequent IE9 Platform Previews allowed us to demo and talk about IE9 features pre-beta, yet we still didn't talk about things until they were available.Anonymous
January 05, 2011
HTML5 Forms CSS3 Text-Shadow, Transitions, Multi-Column,Grid-Layout NOTE: I have problems on IE9 running sites like this blog and apple site (crash or break)... all my 3 Win7 PCs.Anonymous
January 05, 2011
I call Chris Hynes File API support and raise with History API support. If not in IE9, release the features in point updates ASAP (and push the updates to the users like Google does with Chrome).Anonymous
January 05, 2011
Having opened tool "cross_fuzz" that searches out the vulnerability that the security researcher of Google searches out the vulnerability of Web a browser to the public gets into the news. How does Microsoft think about the vulnerability pointed out with cross_fuzz?Anonymous
January 05, 2011
The IE blog is an interesting resource that I look at from time to time. I am glad it exists, and sometimes there is useful information for me. The home page does take a very long time to load, though, due to the amount of content it contains. Also, I know it is not strictly to do with the IE blog, but I second Alison's comment about MSDN documentation. It is really not that great. I mostly use Mozilla's documentation (developer.mozilla.org) for CSS and DOM documentation - they do a better job of documenting Internet Explorer's capabilities than Microsoft itself does! A lot of documentation on MSDN has not been updated for a very long time: stuff like "The default unit of measure for dialogLeft in Microsoft Internet Explorer 4.0 is the em; in Internet Explorer 5 it is the pixel" (and the continuous references to "DHTML") proves this point. Developers cannot have confidence in such stale documentation. Instead of such out-of-date stuff, a summary of cross-browser and IE version compatibility information should be written.Anonymous
January 05, 2011
> How can we make this a better resource for you?
- Respond to requests posted on this blog for fixes to blog pages or demos.
- Get serious about cross browser support on this blog and in the demos. i.e. include audio and video that Opera and Firefox 4 can play natively The "Happy Hardware Accelerated Holidays" (blogs.msdn.com/.../happy-hardware-accelerated-holidays.aspx) exemplifies what's wrong this this blog. There's lots of talk about being "all in" on HTML5 but there's no page support for Ogg Vorbis audio or WebM video. When these are requested those requests are flatly ignored and, to add insult to injury, pages which apparently at some point in their life used Ogg Vorbis audio are quietly modified to remove all references to it. Note that I'm not asking you to build Ogg Vorbis or WebM support into IE9 (although that would be nice and would demonstrate that Microsoft really is committed to building a better web). All I'm asking you to do is build web pages with media that works natively in Firefox 4 and Opera and any other browser with open media support. It's wonderfully easy to do and there's no compelling reason not to do it.
Anonymous
January 05, 2011
I was going to post this on the last article thread to finally put the issue to bed but that article is now locked. For any of the readers that claim that Microsoft's bug with IE's innerHTML is not a bug please visit this URL. support.microsoft.com/.../276228 Here is the quote from the Microsoft Knowledge Base in the Status section: "Microsoft has confirmed that this is a bug" - May 12, 2003 So for all the trolls that keep claiming that this bug is not one - give it up. Now Microsoft its your turn. The bug has existed for over a decade in multiple releases of Internet Explorer. Please make HTML5 in IE9 a possibility by properly, fully supporting innerHTML. Please don't be the only browser on the planet that can't do innerHTML properly. IE6, IE7 and IE8 already have that claim.Anonymous
January 05, 2011
I'm still hoping for HTML 5 forms (or at least placeholder text) in IE9. As for the blog, I think it would be nice if there could be some sort of checkbox next to a post to say whether or not it has been read by a microsoft employee. Just knowing that something has been read might help keep people from repeating the same stuff over and over in the hopes of getting seen.Anonymous
January 05, 2011
I'm a MSP. I use this blog (together with Channel 9) as my primary information source for my technical articles about IE. My articles are focused on web developers.Anonymous
January 05, 2011
The comment has been removedAnonymous
January 05, 2011
PLEASE IE TEAM IE9 MUST HAVE STANDALONE DOWNLOAD MANAGER ICON ON WINDOWS 7 TASKBAR. PLEASE DO NOT COMBINE DOWNLOADS WITH MAIN IE9 ICON. EVERY TIME WHEN I DOWNLOAD SOMETHING IN IE8 AND MY MOM WANNA GO ON THE INTERNET, SHE CLICKS ON THE IE8 ICON, UNMINIMIZE ACTIVE DOWNLOAD, BUT SHE DOES NOT UNDERSTAND WHAT IS GOING ON AND THEN SHE CLOSES THE ACTIVE DOWNLOAD WINDOW :( AND RE-LAUNCH IE8 AGAIN TO BROWSE THE WEB... PLEASE IE9 MUST OPEN ON WINDOWS 7 TASKBAR STANDALONE ICON FOR TRIGGERED DOWNLOADS, THE SAME WAY LIKE CONTROL PANEL ICON IS STANDALONE, EVEN IF IT IS ONLY NEW EXPLORER WINDOW...Anonymous
January 05, 2011
To clear the air, you'll see that I've never claimed that there were no bugs in any innerHTML properties of any object type, obviously there are. I've even found one myself, but that's a topic for another discussion. Some people get uptight about Microsoft having readonly innerHTML properties on objects such as table, and limitations with other properties when trying to update table elements nested within other object types. These are well-known design limitations which clearly need to be removed through further development work. Re-read that last sentence, especially the last part. I work in this field so the nuances between 'bug/defect', 'design limitation', 'feature request' and 'technical debt' are clear to me, but perhaps they are lost on most in this forum. Fair enough, it's not that important. I mistakenly believed that taking a moment to clarify a fine point (again never a blanket statement regarding all innerHTML properties) would enlighten. Instead it seems to out those who would resort to name calling.Anonymous
January 05, 2011
"design limitation" is the cop-out way of saying I don't want to admit its a bug. Congrats! enjoy your imaginary gumdrop world! The rest of us know its a bug and await an ETA for the fix.Anonymous
January 05, 2011
The comment has been removedAnonymous
January 06, 2011
The performance of this blog site is still pathetic and the layout terrible. So to make this a better resource please kick those blog software developers. (kick connect site developers as well please). Please ask the Mobile team to do guest posts on their mobile IE versions. They just dump unknown IE versions upon us without providing any information to webdevelopers and siteowners.Anonymous
January 06, 2011
Don't know whether there is something on Connect , but some bug/performance might be posted as comments there -> blogs.msdn.com/.../seanjenkin Just try to not overflow it or it gets overlooked...Anonymous
January 06, 2011
1.) Add the ability in the Preview releases for Popups to ACTUALLY work! (right now they launch in your default IE install, not as an IE9 preview popup window thus testing any Enterprise apps that use popups or open portals of any kind is not possible without installing the beta - which of course we'd love to do - but can't because you can't install more than one version of IE. That's why the preview release was awesome. 2.) Is there a special blog for "Mobile IE"? If there is - please provide a link, if not, please post info about mobile IE here too (or make such a blog) as there are many, many Mobile IE questions too!Anonymous
January 06, 2011
The comment has been removedAnonymous
January 06, 2011
nice post!Anonymous
January 06, 2011
great post !!! www.nuvenuschovendusfacts.com.brAnonymous
January 06, 2011
The comment has been removedAnonymous
January 06, 2011
Whatever happened to the web chats you used to have?Anonymous
January 06, 2011
> How can we make this a better resource for you? Get rid of Trident and use a different rendering engin, or just accept that you lost the browser war.Anonymous
January 06, 2011
So I finally manage to download virtual PC, and a couple images.. load it up, create my virtual PCs... the IE6 image defaults to Japanese, and the Vista image won't install IE9 because it needs a service pack update but It can't use windows update to upgrade and get the new service pack because although it can surf the net, it can't properly check for updates. TOTAL UTTER FAILURE! - Please sort out your issues with Spoon.net and let the experts host sandboxed images that load in seconds not hours/days... if you are lucky. Wasted half a day on this garbage!Anonymous
January 06, 2011
What we want? Transparency. There can't be enough transparency.Anonymous
January 06, 2011
I once posted this request to the IE suggest area, but I haven't checked for a while on that, But Is IE9's home button going to be moved back to the left of the address bar? For the Site specific Browser, the homepage is the website you pinned, but that button is where the home button should be. yet in the main IE9, it's in a horrible place off to the right, which makes no sense considering there is a home button for say, the Facebook pin app, on the left. Stability is a huge problem in the beta, I know it's a beta, but ocassionally something will crash just for the sake of crashing, like google.com I understand it's still earlly. and the browser has not been released yet, but I hope the browser doesn't get released too soon, unless some of the beta issues have been changed for the better. The menu for IE9 seems counter intuitive, when you have an optional menu with home and everything else, but then have a home button on the UI itself. Last I checked, Favorites is moved off to the right as well, Perhaps that should be moved back at the left, or atleast make changing the icons around possible, because a new user won't have a clue what all those new icons are for, Some people need a menu, I don't but Microsoft office 2007 annoyed me and a few others because the windows button was not really obvious, office 2010 was much better with the file button, and the ribbon customzation options really improved it's useabillity. Consider borrowing some of the ideas from office 2010, like more customizations (like some minor theming) and some leeway in how the UI is managed.Anonymous
January 06, 2011
More Transparency and open dialog please. As soon as IE9 was announced the flood of questions started from developers and they are always the same: 1.) Are you finally going to fix X (where X is one of many well-known long standing bugs in IE) 2.) Are you finally going to add/implement Y (where Y is something that most/all other browsers already support) 3.) Are you going to open up real public bug tracking/provide more frequent builds so that we can determine (X/Y) for ourselves If Microsoft would tell us more about X and Y we would be much better informed and waste less time arguing. I understand that it is Microsoft's policy to not talk about features you are adding until you have done so - and we get that! you wouldn't want to say you're implementing WizzBang! then find out you can't get it in on time. However the opposite scenario is the one that inflicts the most pain on developers and causes the most ill words against Microsoft... NOT TELLING US WHICH BUG FIXES/NEW FEATURES you have NO INTENTION of adding! because we wait, and wait, and wait, and finally there is a release and we groan asking: "Where the !@#$ is fix/feature Z?" - is Microsoft deaf?! we've been asking about this for 6-9 months!!!! This last item is something that can be resolved quite easily. Internally Microsoft has a roadmap, they know that there are 4 categories of fixes/features for every release: a.) Plan to put in b.) Hope to put in (if time) c.) Might put in (sometimes a bonus that makes it in as a result of adding something else) d.) Not going in (Out of scope for this release) "D" is the key here. If you know that fix/feature X/Y is not going to be going into this next release, then save us the headaches and pains by indicating such. e.g. If Fixing IE's .innerHTML is out of scope for IE9 - Tell us! If Adding GeoLocation is out of scope for IE9 - Tell us! If Adding HTML5 forms is out of scope for IE9 - Tell us! If Fixing the IE internal dialog UI/usability is out of scope for IE9 - Tell us! Because when Dean does his keynote in April at Mix and is touting all the new things Microsoft did Fix/Implement there will be no mention of the things that didn't make it in and we will be very upset to have waited 9-12 months to find out that (in our opinion) Microsoft once again did not listen to us or be Transparent about what they did/didn't intend to do. mikeAnonymous
January 06, 2011
What I like on the IE Blog is that you speak about concrete samples of what we can do with the new feature you introduced AND about how it's implemented internally to make is smart enough. You talk about the future of the web in both technical and practical terms. It's really a good deal since it makes both the webdesigner and the curious webdeveloper happy! Sometimes, I would like to see more innovation coming from Microsoft (things like CSS Grid Align....), though. However, as many have said, the blog need to be optimized for faster loading and you should publish before each IE release a table of features/bugs you :
- have fixed since previous version
- have planned to fix for the RTM of the next version
- will maybe fix for the RTM of the next version
- will (probably) not fix or implement You don't need to update this every week, or every month, it makes no sense. It may not be 100% reliable, it's not a big deal. But it's a good indication to developers of what you're going to do, how many progress has been done since the previous release, and how you see the big picture. We sometimes have the impression UA's are talking about features, and not about the way we can combine them; why they choose to 'skip' some things while implementing some others is also a mistery. It's a mistake (and not only Microsoft does that mistake). BTW, if someone having a Tablet PC at Microsoft could check connect.microsoft.com/.../pen-flicks-does-not-works-to-scroll-a-page-when-position-relative-and-overflow-hidden-are-used-at-the-same-time, it would be great. Regards, François
Anonymous
January 07, 2011
Upon downloading the demo, I did notice that IE9 was having issues on major sites. This included sites such as Best Buy, Barnes & Noble, Amazon, Gmail… etc. etc. It is usually small things such as viewing reviews, seeing photos through lightbox, or any other script driven window. I hope the engineer team has really taken these problems into consideration before their launch because already I have started becoming a fan of Google Chrome because it works.Anonymous
January 07, 2011
Redirect to ChromeFrame.Anonymous
January 07, 2011
Is there something about the Vista Virtual PC image that makes it so you can't install IE9 Beta? - It won't let me because the Service Pack is at level 1, but it won't let me install Service Pack 2 or 3? - What Gives? Can you release a Windows Vista (or better yet a Windows 7) image with the latest IE9 Beta already installed? or even just the IE8 with a default link to install the beta? ThanksAnonymous
January 07, 2011
The comment has been removedAnonymous
January 07, 2011
Will IE9 support GeoLocation? Will IE9 support touch events? Win7 has great touch support, and Firefox 4 has a nice browser implementation, even though I really like the WebKit version of touch events better. Which model of touch events will IE9 support? Moz-style? WebKit-style? Some implementation of its own? Will IE9 support CSS transitions? Will IE9 support 3d transform? Will IE9 support text shadow? Will IE9 support border images?Anonymous
January 07, 2011
IE8 consumes more and more memory the longer you browse with 2 or 3 open tabs. This is making our 1gb ram office machines greatly slow down. Can the memory usage be trimmed down?Anonymous
January 07, 2011
I am currently running IE9 Beta. A feature I miss (more than I expected) is the "Paste & Go" command in the context menu (that appears when right-clicking on the address bar). It is something really simple, yet so useful. I realize IE has the Accelerators stuff, but on many occasions the "Paste & Go" command just feel more natural and handy. Could you please consider adding this feature before the IE9 Release Candidate comes out? Thank you.Anonymous
January 07, 2011
Its funny that you did this cloud because if I take the comments from just this post it paints a much different picture: Keywords that developers care about? (listed alphabetical) better browser bug developers fail features finally fix html5 innerhtml msdn please post release resource something updated virtual web work In short, IE has lots of bugs that need fixing, so does MSDN, fix them finally so that the web will just work. Congrats on making IE9 so much better than IE7 and IE8 - but you've got a heck of a long way to go still if you want to join the other modern browsers and play with the big kids.Anonymous
January 08, 2011
That wordle image says it all. Now, try to make these words bigger: better, markup, community, improve, common, focus, impact, compatibility, working, pattern, right - and you'll be off to a good start. The 10 largest words could just as easily be the most used words on sites detailing how damaging IE has been to the Internet and any business foolish enough to have embraced it. Might want to run that by Marketing!Anonymous
January 08, 2011
"...IE9 is all about putting Web sites at the center of the browsing experience." Uh. Isn't that what most people use any browser for? I mean, isn't that the point? Or is Microsoft just now figuring this out?Anonymous
January 08, 2011
Очень Вам благодарен за ПРЕКРАСНЕЙШИЙ БраизерAnonymous
January 08, 2011
Спасибо спасибоAnonymous
January 08, 2011
More on Transparency> "If Fixing IE's .innerHTML is out of scope for IE9 - Tell us!" Yes, it's out of scope as told in a comment to a Connect issue: connect.microsoft.com/.../571341 "While we don’t have enough time to implement an innerHTML context stack for IE 9, we realize this is an important issue to developers, so we’re going to investigate fixing it for a future release."Anonymous
January 08, 2011
@Wheret This is very unfortunate. Even if the report is just about the select element, I've filed many innerHTML issues myself, for example on the table or the html element - Which suffer from the exact same issues. Ever since Beta 1 there was visible work on innerHTML which now seems in vain for IE9. We can only hope that this work is either miraculously finished or reverted back to the previous status quo. Because if the current unfinished work is kept, the feature becomes unusable. It's very unfortunate that there will be so many old issues that won't be fixed in IE9... Well, let's hope for a better IE10 then.Anonymous
January 08, 2011
"...we realize this is an important issue to developers, so we’re going to investigate fixing it ..." And this investigation will determine whether to fix it or not? You people never cease to amaze me.Anonymous
January 09, 2011
@Wheret - thanks for the link. Well I guess that about sums up IE9's failed attempt at full HTML5 support - IE9 will definitely NOT be fully HTML5 compliant ( dev.w3.org/.../Overview.html ) Which is really sad. Surely there is a resource at Microsoft that could have figured out how to do contextual HTML fragments sometime in the last 15 years.! Oddly enough every other browser vendor has solved this. Will Microsoft at least commit to fixing this by IE10? - It would be nice to have an IE browser that is capable of performing basic DOM manipulation before 2014.Anonymous
January 10, 2011
The comment has been removedAnonymous
January 11, 2011
The best thing you can do with the IE blog to fix it is to reduce the main page articles to ABSOLUTELY NOT INCLUDE THE FULL ARTICLE FOR EACH POST - EVER!!!!! Running the DOM Monster tool on the index page returned these results: "whoa, potentially huge issues 4 warnings indicate app ill-health" 3458 elements 8242 nodes 4779 text nodes 16.6 average nesting depth 1285.4k serialized DOM size Wanna know what you can do to improve the IE blog? - Easy - Stop the ridiculous waste of bandwidth and time of loading FULL posts on the index page... that's what an Index is... a page that lists what is on the other pages. I'm not sure why MSFT felt it necessary to structure this blog this way in the first place - its not like we haven't complained about this since the IE Blog was created - but unfortunately just like the bugs we file in Connect for IE, comments on the Blog about fixing the Blog are also ignored. DaveAnonymous
January 11, 2011
and I'm going to vote against taking full posts off the index page; I like having the whole post right there to read, that's why I load the page. Also, this is the way the MSDN blog engine works (check any Microsoft blog) so it may not be worth expending a great deal of effort complaining about it vs reading in an RSS reader you configure to work the way you prefer.Anonymous
January 11, 2011
The comment has been removedAnonymous
January 11, 2011
The comment has been removedAnonymous
January 11, 2011
Internet Explorer is f*****ng my projects since I'm a web developer. Please, stop releasing more versions. I'm tired of translating standard code to IE code.Anonymous
January 11, 2011
@SnarkMaiden : The RSS is also buggy, returning the full posts, with images, videos and everything else.Anonymous
January 11, 2011
@SnarkMaiden - If you want to read any post you simply have to click on the link to that post. Otherwise the benifit is that you won't waste any time downloading content you have no interest in viewing. As for the blogging platform - just because all MSFT sites decided to make the same mistake - it doesn't make it right.Anonymous
January 12, 2011
We need better features: GeoLocation, CSS transitions, 3D transforms, text shadow, & border images. It doesn't help that microsoft had internet explorer removed from spoon.net/browsers either. Now I can't test at all!!!! Are you deliberately helping end the reign of Internet Explorer? I'm not paying £120 to upgrade win7 to pro just for XP mode. No chance!Anonymous
January 12, 2011
At Mix11 will MSFT be announcing that the IE images on Spoon.net are back online so that developers can properly test - or will there be disgruntled developers angry at MSFT for making their jobs harder than they should be?Anonymous
January 15, 2011
Actually I think that IE team is doing their thing no matter what users say!! Feedbacks are moving to recycle bin of their system!! I posted tons of reasons for them to move the tabs ABOVE the addressbar and use the space provided in the title bar. Instead in the new design they've introduced an option to move the tabs BELOW the addressbar and still there's a FULL EMPTY ROW SPACE just for NOTHING!!! So be it. Go your way. Do your thing and hope that everyone will use your browser :)) A browser should be well designed. Not just hardwer accelerated and fast! If the new RC or release is what I hear it is, I will go back to a browser that uses user's feedback not just throwing it away!Anonymous
January 16, 2011
Our IT is considering a switch to Firefox so that the rich features of E4X can be used, when will IE get E4X, is it planned for IE9?Anonymous
January 17, 2011
E4X is great, but it's higly non-standard, and involves many changes in the JavaScript parser. I don't think they planned it for IE9 nor IE10. I support the suggestion to make it a standard to have it as soon as possible in every browser. However, switching your IT to FireFox is risky. They may unsupport the feature in the future (in order to implement a standard based on the spec but different), they may change it dramatically, your code will be broken. Your code will also never works in any other browser anymore. Think about it. If you have users who can't install FireFox on their computer, they will not be able to use your intranet. It's not the way a responsible IT department should work.Anonymous
January 17, 2011
Well, I badly expressed myself. Swithching your IT to FireFox is not so risky. What's risky is to rely on a non-standard feature no one else uses ;-)Anonymous
January 18, 2011
@Colin Thank you for the positive sentiment - we appreciate the time you and others invest in reading our blogs and letting us know your thoughts on the direction of IE. This is an important vehicle for us to talk to and hear back from the community. With respect to your bug (connect.microsoft.com/.../622551), we have updated it on Connect to let you know we are able to reproduce the issue and are investigating. Thanks a ton for taking the time to log a bug there - that is by far the best way to help us improve the quality of IE and understand the needs of our users. we'll let you know once we've finished our investigation!Anonymous
January 18, 2011
The comment has been removed