Happy New Year!
Cheers!
The IE Team
Comments
Anonymous
December 31, 2008
Happy new Year (still 5,5h for me) :-)Anonymous
December 31, 2008
Happy new year! I'll hope you do a great IE8 release in the following year ;)! Still, ~5:19 h for me :PAnonymous
December 31, 2008
Happy New Year to all your guys. Looking forward to IE8 :-)Anonymous
December 31, 2008
Happy new year! I'll hope you do a great IE8 release in the following yearAnonymous
December 31, 2008
The comment has been removedAnonymous
December 31, 2008
Happy new year! And may it be the year web developers stopped hating IE :)Anonymous
December 31, 2008
Thanks, and to you guys too! IE8 is shaping up nicely, and i look forward to exciting things to come! Keep in there - loads of us still use IE!Anonymous
December 31, 2008
Keep up the good work! Hope you all have a happy new year and an enjoyable and productive 2009.Anonymous
December 31, 2008
http://www.microsoft.com/downloads/details.aspx?FamilyID=21eabb90-958f-4b64-b5f1-73d0a413c8ef&DisplayLang=en "This VPC image will expire in April, 2009." Looks like IE8 Final will be released in April, just in time for Windows 7 RC or Final.Anonymous
December 31, 2008
The comment has been removedAnonymous
December 31, 2008
post a decent IE you lazy peeps!Anonymous
December 31, 2008
Happy new year! Wish you all the best and joy and wonderful things to become true this year! It's 2009!Anonymous
January 01, 2009
Happy new year! What is the new years resolution for the IE team?Anonymous
January 01, 2009
A happy, healthy, and bug-free year to all.Anonymous
January 01, 2009
@Marty: Happy new years to you. @VPC: The vpc images have expired on a rolling basis since we started releasing them. It would be a mistake to try to infer anything about IE8's release date from them.Anonymous
January 01, 2009
marty: The correct way of publishing that kind of image is using a vectorial image format. That way it'd look perfect even when resized/zoomed or printed, it'd consume less bandwidth, and you could transform it and make it interactive. If only all major browsers supported some common vectorial image format...Anonymous
January 01, 2009
all browsers do support vectorial image format well cept for internet explorerAnonymous
January 01, 2009
@Someone/@gabe - Hmm, I wonder some sort of Scalable Vector Graphics format? or something that would open up a Canvas to draw on. I vote we call it SVG or Canvas. Woot! Everyone is on board! oh, wait, IE still doesn't play the standards game - I wonder if the new year of 2009 will produce a statement from Microsoft to the tune of: "Microsoft Internet Explorer will natively support SVG in release ____" Heck! I'd be happy to get that in my Christmas stocking next year.Anonymous
January 01, 2009
Happy New Year! "IE still doesn't play the standards game" They appear to have made steps in the right direction that say otherwise. Just because they didn't implement what you want doesn't mean they're not playing the standards game. It might be a happier 2009 if IE 8 were to ship with non-critical enhancements like Canvas, SVG, proper XHTML, full defineS|Getter/lookupS|Getter, and the W3 event model. That said, it still looks like a great upgrade for IE 7 users (see past blog entries).Anonymous
January 01, 2009
@gabe WPF and Silverlight supports vectorial imagesAnonymous
January 01, 2009
@gabe WPF and Silverlight for IE support vectorial imagesAnonymous
January 01, 2009
luc: yeah, because relying on a plugin just to display mere static images is the way to go...? Any Silverlight criticism aside, and from an objective point of view, that kind of plugin is clearly better suited for relatively complex stuff (at the very least an animated banner or a throbber, although an animated GIF is often more suitable for the latter).Anonymous
January 01, 2009
The comment has been removedAnonymous
January 02, 2009
welcome to http://cn.paiming.org/learn to learn ChineseAnonymous
January 02, 2009
The whining here would be much less annoying if you guys had any idea what you were talking about. The image above is obviously from a vector file; you can see it here: http://www.istockphoto.com/file_closeup.php?id=4876181 However, you neglect to mention that IE has supported vector images FOREVER. Windows WMF/EMF files are vector images and have rendered inside IE for over a decade.Anonymous
January 02, 2009
Ted: Well, IE is alone in that, as every other browser supports SVG instead. Hence, it's not very useful: the only "use" it ever got was a pretty big security vulnerability. Also, how good is the support? I haven't tested it, but are they treated as real vectorial things or just rasterized to a bitmap? Do they look good even when zooming? In any case, WMF/EMF is not the solution. As much as SVG might be suboptimal, at least you can govern it with JS to animate it and/or enable interactivity (or even create it from scratch). WMF/EMF is just a resizable static image, represented by a GDI command list (hardly a "neutral" thing, even if alternative implementations exist). This is just another version of EOT vs TTF. IE might have supported EOT since forever, but nobody ever used it.Anonymous
January 02, 2009
The comment has been removedAnonymous
January 02, 2009
The comment has been removedAnonymous
January 02, 2009
I am having trouble getting the internetAnonymous
January 02, 2009
yolandsa, you're on the internet now. good job!!! As for EMF/WMF not working on Mac or Linux, who cares? The vast vast majority of the world uses Windows. "are they treated as real vectorial things or just rasterized to a bitmap?" Unless you understand why that statement doesn't make any sense, you don't understand the basic principles of graphics. Vector graphics are always rasterized to bitmaps, because that's what graphics cards know how to render on your monitor.Anonymous
January 02, 2009
The comment has been removedAnonymous
January 02, 2009
I don't know why we all have to start arguing in a simple "Happy new year" post.. Beats me. And I even participate >.< Hey Ted, the vast vast majority of the world has good eyes, surely there's no need for glasses. The vast vast majority of the world also suffers from huger and thirst. Surely you don't eat and drink very much as well, do you?Anonymous
January 02, 2009
http://iedeathmarch.org/ http://icanhazrealbrowser.com/ Just say NO to Internet Exploder 6/7.Anonymous
January 02, 2009
Why does this blog load so slowly? is it because of the images the other commenters have mentioned? If so can you please fix it soon. As for the latest version of IE8 I don't find that it renders things like other browsers or even like IE7 did. (I'm aware of the whole standards changes but it still looks really un-finished) This isn't the version that will be released soon to the public is it?Anonymous
January 02, 2009
In IE8 I find that many of my hyperlinks with a CSS dotted border do not show the top portion of the border until I hover over them. They work fine in any other browser though. Is this a known bug?Anonymous
January 02, 2009
I have result tables with the CSS tr{ background-color:#fff; } tr:hover{ background-color:#ffeedd; } If my table is any more than 3-5 rows (normally it is 25-50), moving the mouse vertically up and down over the table should very quickly highlight each row moused over. In IE8 only the last row shows the highlight. it is as if IE8 is struggling to keep up with the mouse events. Does IE8 have a major bug where one CSS :hover event trumps a previous CSS :hover event? I don't want to resort to adding event handlers just to fix a simple table row highlight feature but this should be snappy. Thanks MiltonAnonymous
January 02, 2009
Can you remove the tooltip on the RSS/Feed/WebSlice button on the Command Bar? It always pops up under the list that drops down when you click the arrow to choose which RSS/Slice you want to track.Anonymous
January 02, 2009
The view source option on right-click of any page is much improved, but the cursor/caret thing is all messed up, in renders EXACTLY half way through each character, not before or after each character. Worse yet, when you click on the page, it actually picks a spot about 1" to the left of where you actually clicked.Anonymous
January 02, 2009
The comment has been removedAnonymous
January 02, 2009
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9123091Anonymous
January 02, 2009
http://www.computerworld.com/action/article.do?command=printArticleBasic&taxonomyName=Internet+Applications&articleId=9124562&taxonomyId=168Anonymous
January 03, 2009
yaşam deyerlidir aheng vericidir internet ortamıyla....Anonymous
January 03, 2009
Been away, Happy New Year to all. Even TedAnonymous
January 03, 2009
The comment has been removedAnonymous
January 03, 2009
The comment has been removedAnonymous
January 03, 2009
@ its official I'm not sticking up for IE8, but I'd like to see you define faster. Say a shop sell bread at £0.50 and sells a T.V at £400 Say another shop sells bread at £1.50 but sells the same T.V at £300 Is the second show £99 cheaper or does it depend how often you buy bread? Browsers are like that except you can't go to 1 browser to render one part of the page and the other browser to render another part. Saying IE8 is 10x slower is a very subjective statement.Anonymous
January 03, 2009
@its official Seeing as Google is trying to promote their own browser, it's not saying much for them at axe IE. Actually, I'd say it's a pretty sneaky move and possibly viable as an anti-trust suit, seeing as IE6 is still a very prevalent browser. @IE Team Keep up the good work! Someday I hope to be able to argue decisively against my friends who continually brag about FireFox.Anonymous
January 03, 2009
@milton Try this: tr td { background-color:#fff; } tr:hover td { background-color:#ffeedd; }Anonymous
January 03, 2009
@TR - No! that is NOT a good idea! If milton wants the WHOLE row to alternate color on hover, then changing the TD would be goofy. (e.g. changing 'n' elements background (the table cells) vs. changing '1' elements background (the table row)) I've actually tried this myself. If you think the rendering is slow for the row toggle, the td toggle across an entire row is even slower and actually gets worse because some of the cells get so delayed that you'll start highlighting row 7 before row 6 has finished resulting in a broken wave pattern. I suspect milton's guess at the bug is likely an accurate one. @Damian - I believe the stats are pretty clear. For pure JS processing speed, IE comes in last every time. With deep ties to the OS and several pre-loaded resources the IE browser loads fast and the rendering of pure HTML is pretty quick. If IE doesn't pick up the pace with JS processing and apps continue to maximize the use of JS IE will only fall further and further behind in the browser usage stats. (IE has already fallen below 69% and Firefox is up over 21%) http://www.tgdaily.com/html_tmp/content-view-40800-113.htmlAnonymous
January 03, 2009
The comment has been removedAnonymous
January 03, 2009
@Wraith Daquell "Seeing as Google is trying to promote their own browser, it's not saying much for them at axe IE." Except they're also promoting Firefox, so it's not just about killing competition, but about pushing the web forward. In case you didn't bother visiting the page, check it out: http://mail.google.com/support/bin/answer.py?&answer=107906&hl=enAnonymous
January 03, 2009
The alt text for the image in this post is not suitable. "Two champagne glasses toasting" sounds like a caption, and thus is suitable title text but not suitable alt text. Good alt text usually consists of a complete sentence or sentences chosen so that the no-images user wouldn't even be aware that they were "missing" anything -- which they shouldn't be anyway, as good alt text provides an equivalent (not necessarily identical) experience to the image as far as is practically reasonable. In this particular case, good alt text would be "Cheers from the IE Team".Anonymous
January 04, 2009
can someone fix the image already? its been wrong for over 4 days now! yeesh!Anonymous
January 04, 2009
¡Feliz Año Nuevo, IE Team! I'm really enjoying using IE8. Here's to a great 2009 and a great IE8 release.Anonymous
January 04, 2009
The comment has been removedAnonymous
January 04, 2009
The comment has been removedAnonymous
January 04, 2009
http://www.neowin.net/news/main/09/01/05/warning-windows-7-beta-could-corrupt-your-mp3s Code quality at MS sure is bad these days. Where's the QA/QC people and why are they missing all of these major bugs? Windows Mojave, I mean 7 is turning out to be another turd like Vista.Anonymous
January 04, 2009
@Windows 7 beta could corrupt your MP3s Omigods, bugz in beta, we'll all die. LOLz.Anonymous
January 05, 2009
** M I C R O S O F T C A L L T O A C T I O N **
Its now the first full working week of 2009 and IE8 is due to go RTM this quarter (e.g. within 90 days) IE8 PR1 is currently NOT anywhere ready for a production release and developers are starting to worry about how dedicated Microsoft is to fixing IE8 before it ships. IE8 is a monumental milestone in the move towards IE supporting standards and will have to be supported by developers for AT LEAST A DECADE after it is released (e.g. 2019!) Since this release is more significant than the IE7 release ever was it is utterly important that developers are kept in the loop as to WHAT will and WHAT won't be fixed in IE8 so that we aren't sideswiped with an RTM that needs weeks of testing before we can even determine what route to take with OUR production code. Therefore the following questions ABSOLUTELY REQUIRE an answer before IE8 RTM ships. 1.) Will IE8 Feedback on Connect be kept up to date with internal fixes WHEN they happen - and not be mass-updated (often incorrectly) when IE8 goes RTM. 2.) Will this blog identify beforehand with at least a few days notice of when IE8 RTM will ship so that we can prepare for it. 3.) Will Microsoft be shipping another RC (Release Candidate) release before the IE8 RTM is shipped (as noted, IE8 PR1 is currently NOT acceptable as a final version (read: FAILS the RC tests) Thank you very much, and best of luck and success in 2009. Signed: All Web Application/Site Developers & Designers
** M I C R O S O F T C A L L T O A C T I O N **
Anonymous
January 05, 2009
@Fredie M: The Partner Build available to beta testers is just a build that shows some improvements to Beta 2. But you can hardly say it's representative. The IE Team already announced that there'll be at least one Release Candidate public build before RTM. It't this RC build that is expected this quarter. It's not yet known when RTM will be released. If you find bugs, report them over at Connect. Anything else is simply annoying.Anonymous
January 05, 2009
your image url, http://ieblog.members.winisp.net/images/cheers.jpg , returns a "500 - Internal server error." :'-(Anonymous
January 05, 2009
@Daniel - Where did you hear OFFICIAL word from Microsoft that the Partner Build was NOT the Release Candidate build indicated due for Q1-2009? I agree with @Fredie M that the current Partner Build is hardly better than Beta 2 and that neither are ready for production but a wall of silence from the IE Team doesn't help ease our minds when we are waiting for the ball to drop. If anything 2009 should be the year that the IE Team focuses on transparency. We haven't even dealt with the old issues yet and new features are being pushed. My tests thus far with slices, accelerators and local storage all indicate bugs - but I don't even have time to report them as I'm too busy trying to determine if I can even support IE8 if it ships before fixing all the regression bugs.Anonymous
January 05, 2009
@Steve, I've stated it in the past, and I'm happy to restate it: The December partner build was NOT the release candidate build which will be released in the first quarter of this year. I don't know where you're getting this "wall of silence" idea from, as we've been discussing issues on the blog extensively over the last few months.Anonymous
January 05, 2009
@EricLaw [MSFT]: I agree that you personally have been quite active in responding to questions and comments on this blog (and it is much appreciated). The "wall of silence" comment is the one that stems from the time that Dave left onwards. Even when Dave was around, the "Public Relations" spin on much of the posts was so thick and ambiguous that not much info could be reliably extracted. Re: RC Date - Thanks, its good to hear that there will be an RC build in Q1, 2009 and that it is not the Partner Release that came out late last year (the build naming was mis-leading) As for questions that do not have transparent answers at the moment I'd like to repeat a few that have been asked several times before with no answer. 1.) Will there be any sort of changelog/fix list published (before or after) IE8 RTM is shipped such that developers that don't check this site daily can quickly get up to speed. 2.) Will a permanent public bug tracking site be setup for after the IE8 RTM release so that developers can contribute to it without fear of completely wasting their time by populating it. 3.) Will (above) and the existing IE Feedback site get more regular status updates than the historic: "We've just released a new build - Mark all open bugs as fixed and let the developers re-test everything and re-open it" approach? 4.) Will there ever be a roadmap for IE development? Not having any clue what direction IE is going in is a very hard model to develop against. (as always - we aren't holding you to this - we just want to have an idea of what you are even considering) 5.) IE for mobile devices... is currently stuck promoting IE6 technology which the rest of the web is trying desperately to get rid of. Is there a roadmap for when Windows mobile devices will have an IE7 or IE8 based integrated browser? There's many other concerns but I suspect all would be met with "maybe in a future release". Thanks Oh, btw, when the Partner Release came out, it would have been much better if the release post indicated that it was not the anticipated RC that developers were expecting.Anonymous
January 05, 2009
@steve You listed some 27 problems starting here: blogs.msdn.com/ie/archive/2008/12/10/new-accessibility-features-in-ie8.aspx#9197210 You were asked about providing a testcase for each/all of these problems: { I'm not able to reproduce most of the "regressions" you've reported. It would be very helpful if you linked to relevant test cases. } Without a testcase, there is very little to go on here. The only reasonable, constructive thing to do until RC1 is released is to test thoroughly IE8 pre-RC1 Partner build 18344 and to report bugs/problems at IE beta feedback with a [preferably] reduced testcase. Regards, GérardAnonymous
January 05, 2009
The comment has been removedAnonymous
January 05, 2009
@steve: I don't fanc that solution, but if you're under serious time constraints, please use <meta http-equiv="x-ua-compatible" content="IE=7"> or the EmulateIE7 flag. This will buy you as much time as you need. Please consider this: If you write a testcase now, it may give the dev the ability to fix the bug. in this case you won't have to deal with it for the next decae (as you'd like to put it). Making websites compatible to a "inofficial" partner build is wasted time. Don't test before RC. Please wirte tests, as many as possible. And report them over Connect, that's simply the best thing we can do now. We all want IE 8 to become a best as possible release, but that requires testing now, and not after the release, when it's too late.Anonymous
January 05, 2009
The comment has been removedAnonymous
January 05, 2009
Can you people come up with a user friendly simple browser in 2009. Ease of use is important for accessibility.Anonymous
January 06, 2009
The comment has been removedAnonymous
January 06, 2009
It certainly would be a happy new year if you end of lined IE6.Anonymous
January 06, 2009
The comment has been removedAnonymous
January 06, 2009
@EricLaw [MSFT] Initial condition
Make sure you have Tools/Internet Options/Advanced tab/Browsing category/Recover automatically from page layout errors with Compatibility View checkbox checked when using IE 8 pre-RC1 Partner Build 6001.18344. This setting is activated by default; the checkbox is checked by default. Steps to reproduce
1- Load www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/background-color-change-hover-ie8b2.html in pre-RC1 PB 18344 under XP Pro SP3 2- Hover the mouse cursor over the link "connect's IE beta feedback as bug 365927" Actual result
A balloon will pop up saying " Compatibility View A problem displaying gtalbot.org caused Internet Explorer to refresh the webpage using Compatibility View " and the webpage automatically switches into non-standards rendering mode. This behavior is also reproducible 100% with some other links in the page and at brunildo.org/test/IE8b1_clickablearea.html Important note
The user then may not be aware that rendering mode (documentMode) will remain in Compatibility view as long as the user remains (browses, surfs to new webpages) in the same domain. This may not be easily noticeable. Regards, Gérard
Anonymous
January 06, 2009
@Steve >Indeed I was asked to provide test cases for the 27 bugs I listed. 6 people overall have invited you, have suggested to you or have formally asked you to provide testcase(s) and/or report these problems/regressions/bugs to Connect's IE beta feedback. Most of them some 25 days ago. 3 of them (EricLaw, Dan, SylvainG) being [MSFT] people. > I also responded after that indicating that I don't have time to build one for each and every bug I listed, EricLaw indicated that they couldn't repro most of them, thus please indicate which ones they could - so that I wouldn't waste time creating test cases for those ones. Maybe you misunderstood him. EricLaw said "I'm not able to reproduce most of the 'regressions' you've reported. It would be very helpful if you linked to relevant test cases. Thanks!" as he most likely meant all of the 27 mentioned problems/bugs/regressions. This is how I understood his "'regressions' you've reported" figure of speech-reply. There is no way one would know for sure what could be the precise markup code and CSS code causing/triggering most of those 27 mentioned problems/bugs/regressions just by reading your 27 short, limited descriptions. > But that clarification never came. > I have a day job too. I have contributed and filed almost 200 bug reports and test cases in IE Feedback (between IE7 and IE8) and only a handful were ever acknowledged, and even fewer were fixed. > I am a team player (don't get me wrong) but without 2-way communication on the bug front it all falls apart. This is an exchange you had with Dan: December 11, 2008 @Steve: I trust you filed all the bugs in the bug database you have access to? http://blogs.msdn.com/ie/archive/2008/12/10/new-accessibility-features-in-ie8.aspx#9197595 December 11, 2008 @Dan - No I haven't filed any of these bugs in Connect yet. I want confirmation of where this build sits in the roadmap first. (...) If any filed bugs in connect are going to get shut down again by an RC release in 30 days or so then I won't waste any of my time filing them (beyond the public "filing" above). http://blogs.msdn.com/ie/archive/2008/12/10/new-accessibility-features-in-ie8.aspx#9197778 You and I don't control the IE team agenda, policies, roadmap, to-do list, bugs-to-fix list, postpond-bugs list, hierarchies, requirements, etc. Microsoft is a private business, driven by profits, aimed at keeping share holders happy, etc. It's not a free-drinks-in-open-bar where democracy rules, where your demands/wishes are their orders, etc. Even in open-source projects, not everyone is consulted, not every meeting is accessible, not everything is consultable, documented or transparent or logical/coherent/consequent or resolved/managed as fast as a snap of fingers. I'm not going to deny that they have done a few fumbles here, turnovers there, bad calls, counter-productive planning, incoherent decisions, etc... regarding IE beta feedback bug database management/design/configurability, some bug reports, etc... Regarding IE beta feedback bug database, I have suggested several improvements which have been supported also by others in IE Blog and so far they declined or ignored them. Ultimately, it's their decision, not mine, not yours. A very wide majority of web developers would want IE 8 to be as best and W3C-web-standards-compliant (in particular HTML 4 and CSS 2.1) as possible release, but that requires testing now and proper bug reporting when needed/justified, and not testing+reporting after the release, when it's way too late for IE8 and way too early for IE9 (... in 2010?). Regards, GérardAnonymous
January 06, 2009
IE 8 is a poor product. I dumped it and installed Mozilla. I was sick of correcting the 125 percent zoom. Almost every web page visited had to be manually corrected. This takes my staff far too long. We Goggled the heck out of this and could not find a solution, so, Good Bye!Anonymous
January 07, 2009
The comment has been removedAnonymous
January 07, 2009
The comment has been removedAnonymous
January 07, 2009
The comment has been removedAnonymous
January 07, 2009
PLEASE PLEASE PLEASE, for those of us who use WSUS release a version of IE8 that will deploy silently!! PLEASE!!Anonymous
January 07, 2009
whats with the image on this post? why does it take almost a full minute to load? did someone mess up the dimensions or something and if so why has it not been fixed already?Anonymous
January 07, 2009
When will be the Browser compatibility issues will be resolved?. Do Microsoft has anything in their mind for IE future releases.? There should be a common standard followed by all the browsers so that, there shouldn't be any time consumed for fixing the browser compatibility issues. Microsoft please take initiative for this.Anonymous
January 09, 2009
your image url, http://ieblog.members.winisp.net/images/cheers.jpg , returns a "500 - Internal server error." Greets PensionAnonymous
January 10, 2009
Question: How many days does it take the IE Team to change an image hosted on the IE Blog? Answer: We don't know, we're still waiting. Maybe they think we like huge file downloads? Maybe they don't know about this new fangled PNG image format yet? Or maybe, just maybe, they have the Create permission, but not the Update permission on the Blog? Maybe one day they will figure out how to edit images - I hear you can do that, but maybe it is only on a Mac? ;-)Anonymous
January 11, 2009
Has anyone else noticed that this is the last post that shows up in the Windows Vista sidebar headline gadget? There haven't been any new articles showing up from any of the Microsoft feeds since New Years.