Developer Tools in Internet Explorer 8 Beta 2
In March I wrote about the Developer Tools in Internet Explorer 8 Beta 1 and outlined three key benefits:
- Integrated and simple-to-use
- Provide a visual interface to the platform
- Enable fast experimentation
Internet Explorer 8 Beta 2 brings the Developer Tools closer to realizing the full potential of these benefits with significant improvements to existing features and new functionality meant to make you more productive.
Profiling and Debugging JScript
Beta 1 introduced a JScript debugger that lets you easily debug Jscript within Internet Explorer. In Beta 2, we’ve made a few great improvements: it now supports console.log, just-in-time debugging, and has better usability through changes like an improved file chooser.
However, the debugger only helps get your site working properly and you need to make sure your site works optimally. That’s why Beta 2 includes a built-in JScript profiler. Use it to build high-performance web applications in Internet Explorer by finding hotspots and comparing different design patterns. Simply press ‘Start Profiling’, perform you scenario, and press ‘Stop Profiling’ to view profile data for all JScript, including built-in methods.
Keep following the IEBlog for more details about these great features. You can also read our online documentation on script debugging and script profiling.
Working with HTML and CSS
While Beta 1 supported live editing of only HTML attributes, Beta 2 brings this functionality to all of HTML and CSS. With live editing of CSS, just click a property name, value, or selector, type a new value, and press ENTER.
If you need to change HTML tag names, reorder, or add/remove elements, use full-text editing. Press ‘Edit’ in the toolbar of the HTML tab to make the full HTML editable. Press it again to commit your changes and return to tree view. This uses innerHTML so the same rules about running script apply as if you made the changes through JScript with innerHTML.
Changes made in the tools last only until the page refreshes or you navigate away. While this lightweight editing is helpful, it also makes it easy to lose changes. Beta 2 lets you save the current HTML and CSS to a text file so you have a reference when updating your source. The data in the tools comes from Internet Explorer rather than your source and thus might contain changes beyond edits you made with the tools so the default file format is txt to prevent accidental overwrites of the original source. A good way to identify just your changes is to save the HTML from the page before and after your changes and use a tool like windiff.
Testing Compatibility
The Developer Tools have two menus for compatibility: “Browser Mode” and “Document Mode”. “Browser Mode” lets you modify how IE behaves as well as how it reports its version to servers and web sites. This lets you use IE8 to test what your site looks like in IE7 and what your site looks like for users in IE8 who pressed “Compatibility View”. “Browser Mode” affects the user agent string, version vector used when evaluating conditional comments, and the rendering mode.
“Document Mode” lets you test what your site would look like if you changed its rendering mode by using a different doctype or the meta tag.
You’ll also notice that the menus always display the current mode so the information’s available with zero clicks.
Simple to Use
From the start, we’ve worked to make the tools user-friendly. We made them part of every IE8 installation so you didn’t have to install anything extra, built per-instance script debugging so you don’t constantly find yourself in the ‘Advanced’ tab of Internet Options, and worked to reduce the clicks needed for common tasks. In Beta 2, we’ve made a few important changes that should make the tools even better.
If you’re like me, you love using the keyboard. Beta 2 adds extensive keyboard shortcuts for frequently-used functionality and uses common keyboard conventions so you become comfortable with the tools quickly. For example, F12 opens the tools, CTRL+E puts focus in the search box, and F3 and SHIFT+F3 cycle through results. Check out the full keyboard reference to learn all the shortcuts.
Besides some polish to make the tools prettier (even devs appreciate a nice design touch here and there), toolbars within the tabs make access to common tasks fast, and syntax-highlighting throughout the tools makes everything easier to read.
You can pin the Developer Tools to the Internet Explorer window as you could with the Internet Explorer Developer Toolbar, but Beta 2 also lets you minimize in window. With the tools pinned, press the ‘Minimize’ button or CTRL+M to reduce the tools to only the menu bar to save screen space while retaining access to the menus and Browser and Document Modes.
Internet Explorer Developer Toolbar Features
As promised, we’ve included all the features you’re familiar with from the Internet Explorer Developer Toolbar, including the ‘Attributes’ list view and ‘Resize window’ functionality.
More Information
Keep watching this blog for more about the JScript tools and check out these articles for more information:
- Discovering the Internet Explorer 8 Developer Tools
- Developer Tools: Script Debugging Overview
- Internet Explorer 8 Developer Tools GUI Reference
- Developer Tools: Script Profiler Overview
- Developer Tools: Keyboard Shortcuts
John Hrvatin
Program Manager
edit: image resize; Console.log to console.log; search fox to search box
Comments
Anonymous
September 03, 2008
PingBack from http://www.easycoded.com/developer-tools-in-internet-explorer-8-beta-2/Anonymous
September 03, 2008
Great job John, just one question: how do I debug this: <div id="test"></div> ... t = document.getElementById("test"); while(true) { t.innerHTML += "a"; } It blocks the whole of IE, not just one tab. Everything becomes unresponsive. I thought IE8 was supposed to solve this problem? All tested browsers (Chrome, FF, Opera) deal with this better than IE8 beta 2. What am I missing?Anonymous
September 03, 2008
Great guys,but remember! Add Download Manager,spellchecker to internet Explorer 8 !Anonymous
September 03, 2008
When you inspect a HTML element, why does the CSS pane display every single property of the element's parents? For example, even if you have an innocent SPAN tag selected, the dev tools will show irrelevant properties from they BODY tag. It's also inconsistent when trying to disable certain CSS properties, it seems that some can be disabled (padding) while others can't (borders). And what about adding new properties like in the old dev toolbar? Thanks for posting this though.Anonymous
September 03, 2008
Off-Topic Just wanted t make an observation with IE8 and Google Chrome. The developers at Google chrome (3guys ?) has been successful in developing such an amazing browser in 2 years, that you guys have failed to achieve for so long. I think this is the beginning of the end for IE. I really wanted to help IE 8 team so I subscribed to this blog, downloaded both IE8 betas and tested them. The only reason I wanted to help IE team because previous versions have helped break the web for lack of Standard compliance; as a developer this is very important and frustrating for me. But after using IE8 beta 2 since it's release, all I can say is that I am hugely disappointing. Bloated, broken, crashes randomly, takes minutes to load... I understand it's a beta. But so is chrome, have you guys used it? Seriously, please take an hour of your preciously time, sit back and enjoy the browser, and compare it with IE8 beta2. I can't crash Chrome, even if I wanted to... I think the only way IE8 will survive, is if it becomes open-source. You guys have already failed, in a major way. This is sad because, I was very attached to IE for the longest time. Why is IE always playing catch-up and not leading the browser market with innovations? Sorry for the off-topic, but I really badly want to know what you guys think about Chrome. Please, some developer from the team share your opinion about chrome. Thanks.Anonymous
September 03, 2008
@Pavs: Of course we've taken time to look at Chrome as well as the other browsers. If you've been a regular reader of the IEBlog, you know we don't generally comment on the other browsers; most of our readers come here to learn about IE. I will say that we are happy to have more people who love browsing helping to bring good ideas to the table. Competition makes us all better and ultimately improves the internet for users.Anonymous
September 03, 2008
Tony - Thanks for commenting. I understand that it is not appropriate to talk about other browsers in a IE developers blog. But I needed to know this; as for the longest time I had this weird feeling that the IE developers don't use anything other than their own softwares, so they don't know how badly IE stands compare to others. So it's good to know that you use/compare IE to other browsers, even if it's done privately, among your peers. Hopefully chrome will push you guys harder to build a better browser. Good luck to you and your team!Anonymous
September 03, 2008
Generally the developer tools in IE8 is great. I have noticed one thing though. When using a javascript library (in this case prototype) the HTML view becomes useless because every attribute and function added by the library is being displayed. It would be great if there was an option to disable the display of non-HTML attributes on the elements. A bit of inspiration for this can be taken from Firebug. It keeps the html-view clean of non-HTML attributes.Anonymous
September 03, 2008
Notice a little quirk When compatibility mode is on, the user agent string sent is 'Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) But the user agent sent during an ajax is 'Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)' It's still sending as MSIE 8.0 Any way to override user agent strings sent by ajax?Anonymous
September 03, 2008
The comment has been removedAnonymous
September 03, 2008
@Pavs Only three guys worked on Chrome? That is truly impressive but it should be pointed out it based on webkit and so not quite three guys.Anonymous
September 03, 2008
chk this. Chrome Captures 1% Market Share In Just Nine Hours http://marketshare.hitslink.com/report.aspx?sample=21&qprid=43&qpcustom=Chrome+0.2Anonymous
September 03, 2008
@Mike I just double checked - My mistake. There were four developers. (http://www.wired.com/techbiz/it/magazine/16-10/mf_chrome) Project started around 2 years ago June 2006. Webkit is the only part of chrome browser that's not developed by the chrome team. Chrome is more than webkit. I am finding it really hard to go back to FF as my default browser.Anonymous
September 03, 2008
pavs, to crash chrome (not just the tab in question, making a mockery of the publicity materials), type about:crash% into the address barAnonymous
September 03, 2008
Chrome = refurbished Webkit. If it took them 2 years to do a skin and seperate the tabs to processes, then Chrome is pretty sad.Anonymous
September 03, 2008
Arieta: it really doesn't seem like you know what you're talking about... You're making it sound much more simple than it is. Are you a developer at all?Anonymous
September 03, 2008
Arieta - obviously you don't know what your are talking about. So no point arguing your claim. To go back on topic a little bit (sorry IE team); on it's first try chrome debugger (developer tools) "almost" puts firebug to shame. This, coming from a heavy firebug user: http://farm4.static.flickr.com/3089/2827758630_311c67c93c_o.pngAnonymous
September 03, 2008
I really appreciate all the improvements being made in IE8 though why is the JScript blog so quiet? Where can I read about DOM improvements in IE8 compared to IE7? I'm hardly a JavaScript guru though I've been getting much better over the past couple of years. Support for console.log is interesting. Also I wanted to thank you guys for adding border property support for checkboxes! I've been getting comfortable with MySQL the past couple of months and IE8B2 supporting :focus on a checkbox makes it so much easier to keep track of which element has focus! :-) Frankly I think Chrome severally failed on their release, I blogged about those important points on my site so if you disagree chat there instead please...still it's nice to have two versions of WebKit available for testing (and makes it easier to test two different versions) just as we can now almost instantly test IE7 and IE8 with a click of a button! Also will you guys be blogging about the GUI any time soon? It's still not customizable though I have noticed some slight improvements in the general direction. I was under the impression that the GUI was going to receive a lot of attention for Beta 2?Anonymous
September 03, 2008
In March I wrote about the Developer Tools in Internet Explorer 8 Beta 1 and outlined three key benefitsAnonymous
September 03, 2008
http://weblogs.asp.net/markwisecarver/archive/2008/09/04/developer-tools-in-internet-explorer-8-beta-2.aspxAnonymous
September 04, 2008
Adding the IE6 rending engine to a "developer" version of IE8 would be really amazing. I hope you guys consider doing this.Anonymous
September 04, 2008
Nice idea but it seems to be a copy of firebug, a webdeveloppement plugin for Firefox, no ? https://addons.mozilla.org/fr/firefox/addon/1843 I hope yours work very well like the open-source one.Anonymous
September 04, 2008
@JAB Creations: Thanks for your interest in JScript blog. Details of JScript features in IE8 will roll out shortly both on the IE blog as well as the JScript blog.Anonymous
September 04, 2008
Web developer Tools included on IE8 are GREAT! I cannot beat IE will conquer its past users levels but including InPrivate, Tab Process Independence and this new Developer Tools will set new standards on the Web Browser Development... and it seems Google Chrome has implemented this new standards !!! Good work, keep doing it so well.Anonymous
September 04, 2008
@KristoV: I'll cite a previous IEblog post comment from a MSFT member: "we've definitely seen Firebug!". I won't go as far as saying they started the photocopier on that one - if only because there aren't 20 radically different ways to make a web page debugger - but that was to be expected, considering how many times the IE Developer toolbar team was asked to implement a Firebug equivalent. On a side note: Firebug 1.2 is out. IE 8 is shaping up to be not as outdated as IE7 was upon release - and for the first time since 1999, will actually innovate - but, frankly, DOM2 events support is getting ever more important. A small question about IE8's development tools: will they be updated along with IE releases only, or can they be updated independently of the browser?Anonymous
September 04, 2008
Tim: I think it'd just add needless confusion and bloat to the program, not to mention IE6 needs to be completely wiped off the face of the web. If you are a web developer and want to check IE6 compatibility, just get IETester.Anonymous
September 04, 2008
As a developer I understand the feeling that one's ideas and code are better than everyone else's. Hubris is almost a job requirement. But there comes a point where you have to look at the bigger picture. Would the IE team ever consider the idea of joining forces with one of the open source browser engine teams, for example WebKit, to produce a version of IE that used a common code base for its core functionality? Instantly that would remove a whole set of cross-platform compatibility problems that web developers in the trenches have to deal with. And think of the benefit to ordinary consumers who just want to see their favorite sites and conduct their everyday business! Given that: a) IE has had some great innovations like XMLHttpRequest that changed the web for the better, b) Browsers should be interchangeable commodities, uniformly fast, stable, and consistent, and c) Differentiating value, if desired, can be added to browsers outside of the core functionality, why not hook up with one of these other teams to achieve these goals cooperatively?Anonymous
September 04, 2008
@Tim Hettler I think the IE 6 rendering engine is included. If you open the Developer Toolbar, and select "Document Mode", you should see "Quirks Mode", which is the IE 6 engine, is it not???Anonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
That is "console.log" (all lower case) to match with Firebug and similar. until I saw the screenshot, I thought for a second you guys tried to re-invent the wheel.Anonymous
September 04, 2008
Congrats You're getting closer to Firebug and the Webkit effort to clone Firebug. How about a console now? Please support the Firebug API like Webkit are doing: http://trac.webkit.org/changeset/35676 http://getfirebug.com/console.html http://getfirebug.com/commandline.html Having to convert console.log() statements to alert() calls is just giving me yet another reason to still hate IE. Please do everyone a favour and implement this before IE8 RTM.Anonymous
September 04, 2008
http://www.surveyware.com/report.aspx?qprid=1&qpcustom=595&qps=1&qpcustomb=&qpnoauth=1&qpcustomc=99 Firefox seems to be kicking IE (as does every other browser) in the "which browser is best" opinion poll. Glad to see the dev tools improving for IE. Its no Firebug/Chrome debugger thats for sure, but it is coming along. I love the "same rules as JScript" comment about editing the DOM in real-time. What a very nice way of saying... tons of stuff won't work! Don't bother trying to change the .innerHTML on TABLEs, THEADs, TFOOTs, TRs, SELECTs etc.Anonymous
September 04, 2008
To those praising chrome team for only two years of development completly forget that IE team had far more work then Chrome-team.Anonymous
September 04, 2008
Chris, Quirks mode is the bane of web development. Quirks mode isn't IE 6 rendering engine. Quirks mode is something that is activated when a web developer creates a web page and doesn't delcare which standard the browser should used (i.e. HTML4 XHTML1.1, etc.) so the browser tries to 'guess' how the page should be rendered. Each browser would guess differently since there was no baseline standard for 'guessing.' !Mucho Problemos!Anonymous
September 04, 2008
so is there another beta coming in november? or its time to RTM now?Anonymous
September 04, 2008
It expected that RTW for IE8 will b drop on 1 Nov..!!Anonymous
September 04, 2008
@Rowan There are definitely still bugs in the style tracing that we'll work out for RTW. If you find specific issues, please file a bug. Allison posted in July (http://blogs.msdn.com/ie/archive/2008/07/30/wanted-ie8-beta-testers.aspx) about how to join the beta. You can still add properties through the 'Attributes' pane. You can also add an attribute to the selected node by pressing '+' in the tree view. JohnAnonymous
September 04, 2008
@Chris: IE6 and IE7 both have the same quirks mode (= IE5.5 mode), but IE8 doesn't have the IE6 "strict" mode. In other words, IE8 can behave like IE5.5, IE7 and IE8, but not like IE6. @Klimax: so what? It's not the amount of time spent on the browser that matters, it's how good the browser is in the end. Ancient codebases are a pain rather than a blessing, and the fact IE is old isn't an advantage. Besides, "2 years" also happens to be the time spent on IE after the 5-year break taken, as IE6 was supposed to be the last IE version. So Google started working on Chrome around the time the IE team finally resumed work on IE...Anonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
@erlando Our priority has been to use the tools as a window into IE so we do little to nothing to clean up the tree view or any data we get back from IE as that might cause more confusion. Having options for hiding certain attributes or elements so devs can knowingly turn them off is a good suggestion though. thanks! JohnAnonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
@hks we did work to address this type of issue. do you have a repro site we can look at? thanks!Anonymous
September 04, 2008
JohnHrv [MSFT]!!! If this is so, why the heck wasn't this one of the first things posted on the Beta 2 release! We've been screaming about this loss of functionality since the first public beta of IE7!Anonymous
September 04, 2008
false hope. You can't put any toolbars in that HUUUUGE blank spot to the right of the Menu. Good news is now you can actually have a full set of tabs on the tab bar.Anonymous
September 04, 2008
you can move some stuff, but it is still broken! I moved the command bar to the far left... but the menus (safety, tools), still open to the left!!! With the command bar in this better spot, you can't drag any toolbars to be put AFTER this toolbar (e.g. on the right)Anonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
Zoom in any level on any page (e.g. about:tabs) Try to highlight/do anything. The page almost hangs trying to handle user-interaction... Zoom back to 100%, all is fine again. moral of the story? Zoom is still busted in IE8 (but worse than IE7)Anonymous
September 04, 2008
Woo Hoo! My RELOAD and STOP buttons are now in the CORRECT location!!! LEFT of the address bar!!! it only took 3+ years! Way to innovate! Any chance this can get back-ported to IE7 so I can fix it too?Anonymous
September 04, 2008
Rendering glitch below tab bar when restoring from a fullscreen view in XP.Anonymous
September 04, 2008
less memory usage for IE 8 i have Vista with 1.5gb memory.Anonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
Request for help: I downloaded IE8 Beta 2 and I have many problems. I would like to remove it and reinstall IE7. How can I do that? I am not an expert so please explain in detail. Thanks.Anonymous
September 04, 2008
This is a great improvement, but a thing I really don't like about the new developer tool is the treeview display of the DOM. It shows way too much information. All I really want to see is the tag type and the ID (it if exists). The rest is already available in the property grid. The problem is that the style property is shown first, so it's impossible to quickly identify a node by ID because you would have to scroll right to see it. I liked much better how this worked for the IE6+7 developer toolbar. Furthermore it's really sluggish for large DOMs and I suspect all that redundant information is causing it (again the old tool was much faster).Anonymous
September 04, 2008
@Morten I agree the ID could ideally come first, but I'd rather it reflect the TRUE DOM as it was served up. (e.g. If I set class first, that's what I want to see first. Putting everything else in the grid is a bad idea. It dis-associates the attributes from the nodes. Glad to see that the case is fixed though! that UPPER CASE garbage was very hard to read. nickAnonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
@JohnHrv [MSFT] This is what I mean by customizable GUI... http://img175.imageshack.us/img175/3019/ie8betterguier2.pngAnonymous
September 04, 2008
The comment has been removedAnonymous
September 04, 2008
"Wrong. The first thing to tackle to make a webpage work as efficient, as optimally, without a itch, without problems is to choose a doctype declaring a strict DTD, validate the markup code, separate the presentation from the structure, validate CSS code. It's widely know that it's useless to try to debug a webpage or to improve a webpage without first achieving those necessary steps. For hundreds of reasons. None of those tools help in such task." How does that contradict what he wrote at all? If it still isn't performant after that then the first thing you should do is profile the site to see where the problem is. Just like in native application programming where you make sure your code is well-structured, makes proper use of OO (or functional programming or what-have-you), is clear, etc., etc., and then when it's not performant you profile it and optimize the slow parts.Anonymous
September 04, 2008
With news like this, I'd actually start getting excited for this browser...if we'd get a fix/workaround for the lack of css opacity for standards mode...Anonymous
September 04, 2008
Well I like them a lot. Would like to be able to view response headers as well.Anonymous
September 05, 2008
The comment has been removedAnonymous
September 05, 2008
pavs: The debugger is exactly the one that comes in the WebKit package and so, probably not a Google-built thing. The point is that it was not easily available for Windows PCs and was very much restricted to MacOS users.Anonymous
September 05, 2008
Love the addition of Profiling in IE, my most wanted aspect from firefox for IE. I have noticed several requests for features so please forgive me adding on. Is their any chance of getting a way on the html tab to just open the entire tree structure? Selecting elements is good for looking a one item, but seeing the entire html structure takes a while to have to click on all the '+' buttons.Anonymous
September 05, 2008
Something has to be done with the suggestions in the address bar, it takes too long to show up in some cases.Anonymous
September 05, 2008
or the open the entire structure under a selected nodeAnonymous
September 05, 2008
@Lucas You can open the entire tree by pressing Shift + (Numpad *). Works in the HTML Tab as well as the Profiler Call Tree view.Anonymous
September 05, 2008
The comment has been removedAnonymous
September 05, 2008
Jana, I, personally, believe that all those with older computers should upgrade. It would solve a lot of problems.Anonymous
September 05, 2008
@Jana, Fact: Firefox 3 is not available to Windows 98 users. Fact: Safari 3.x for Windows is not available to Windows 98 and Windows 2000 users. Fact: Konqueror 4.1 for Windows is not available for Windows 98. Even if all those browser versions were available for Windows 98 users and Windows 2000 users, I would certainly invite my friends to upgrade their os or to switch to an os which is still maintained with service packs, security fixes, bug fixes, has regular security updates. Will the getElementById function get fixed in IE8? Just see for yourself: connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=333979 And such getElementById bug involves a precise code context where name and id attribute values are using, are sharing the same value. Besides such precise code context, I am not aware of any other particular bugs affecting the working order of getElementById in IE 6 or IE 7. Using the same value for id and name gets reported as a warning when using HTML Tidy. You don't like the UI in IE 7+? Deal with it otherwise proceed from it. It won't change in IE 7. And maybe it's too late for IE 8... really don't know. Anyone with a PC with modest system resources can switch to Linux Ubuntu, Kubuntu or Xubuntu for free. If the PC system resources were sufficient for Windows 98, then they will have the sufficient system resources for a |K|Xubuntu operating system: www.whylinuxisbetter.net/items/environment/index.php?lang= Fact: Windows 98 and Windows 2000 users represent less than 3% (and declining) of the market today: www.w3counter.com/globalstats.php marketshare.hitslink.com/report.aspx?qprid=10 "if everything goes extremely well, we migt be able to ditch the most horrible IE workarounds somewhere in 2020" Not if you make your webpage comply with basic WCAG guidelines, degrade gracefully, not if you avoid adopting pixel-perfect page layout goals and warn visitors that it is their responsibility to be using a W3C web-standards compliant browser. One last thing. This blog post from John Hrvatin was about the new developer tools. Regards, GérardAnonymous
September 05, 2008
The comment has been removedAnonymous
September 06, 2008
Well, i think this is great. I would see any functions like Total Commander. I can dream all night long of illusion functions possible on internet browsers.Anonymous
September 06, 2008
The comment has been removedAnonymous
September 06, 2008
[l] The second beta version of IE8 was released on August 27th. It is working well in testing so farAnonymous
September 06, 2008
I like to have the Web Developer Toolbar open and docked all the time. I would also like it to remember if I minimized or resized it when I create a new tab or open a new session. Currently it does not do that. I hope this feature will be implemented in the future.Anonymous
September 07, 2008
Parce qu'il n'est pas possible d'écrire sur tous les sujets et que d'autres le fontAnonymous
September 07, 2008
The comment has been removedAnonymous
September 07, 2008
Bugs discovered in IE8 beta 2 http://www.neowin.net/forum/index.php?showtopic=664024&st=0&#entry589754162Anonymous
September 08, 2008
General Top 10 Things That Annoy Programmers : Kevin Pang has an extremely accurate list of developers' top annoyances. Handling Passwords : A great article for both the beginner and expert about securing passwords. SQL Server 2008 - Introduction To TheAnonymous
September 08, 2008
recently jscript errors stated popping up on every site I visit already posted in feedback IE 8 b2 has flipped out on meAnonymous
September 08, 2008
We’ve been sharing plenty about the work we’ve done in Internet Explorer 8 Beta 2 for browser users;Anonymous
September 08, 2008
As others have pointed out, most of the ideas for the developers tools are obviously borrowed from Firebug, which is fine. But you don't even have the common courtesy to mention it in the blog post or link to it?Anonymous
September 09, 2008
I think that everyone already has chosen tools to develop Web pages. The proposal, which offers Microsoft is interesting. I think that should be tried.Anonymous
September 09, 2008
It appears that most of js errors on many sites I encountered are caused by IE8 blocking google analytics or similar cross site js. I dunno if it's a good or bad thing :PAnonymous
September 09, 2008
One of the key themes for IE8 is developer productivity. IE8 Beta 1 improved developer productivity throughAnonymous
September 10, 2008
I'm just curious as to why you didn't consider hosting the IE developer tools in the Visual Studio Shell. Granted that the shell would be a separate download about 10 times larger than IE itself but it would give developers a familiar IDE.Anonymous
September 11, 2008
Hello! I am Sameer Chabungbam, one of the Program Managers on the JScript Team. The recently releasedAnonymous
September 14, 2008
The recently released Beta 2 of Internet Explorer 8 contains a lot of improvements which are aimed atAnonymous
September 14, 2008
As you probably heard, IE8 introduces the Developer Tools. Lots of great features like live HTML andAnonymous
September 17, 2008
In Internet Explorer 8 Beta 2 JScript team has focused on improving developer productivity. You can readAnonymous
September 17, 2008
It has been a while since I blogged here (this is an understatement!). Internet Explorer 8 Beta 2 hasAnonymous
September 22, 2008
Hi, my name is Jatinder Mann and I work on the Internet Explorer Administration Kit (IEAK) and GroupAnonymous
October 19, 2008
Одним из ключевых направлений развития IE8 является увеличение производительности труда разработчиков.Anonymous
March 19, 2009
微软宣布InternetExplorer8释放中国-中文简体ForWindowsServer2003http://go.microsoft.com/fwlink/?Lin...Anonymous
March 24, 2009
Microsoft released the final version of IE8 last week (3.19.2009); your users will soon be automatically upgraded unless auto-updates have been explicitly blocked. Are you ready?...Anonymous
March 24, 2009
During Beta1 and Beta2 pre-releases of IE8, we’ve blogged about the performance optimizations done inAnonymous
March 25, 2009
During Beta1 and Beta2 pre-releases of IE8, we’ve blogged about the performance optimizations done inAnonymous
March 30, 2009
微软宣布InternetExplorer8.0释放中国-中文简体ForWindowsServer2003http://go.microsoft.com/fwlink/?Link...
