MIX Session Videos Now Available


We had a great time last week at MIX talking to many of you about IE9.  For everyone who wasn’t able to be at the conference, we wanted to let you know that all the sessions are now available on-demand. 

Enjoy!
Rob Mauceri
Group Program Manager

Comments (20)

  1. DanielHendrycks says:

    Thanks :)

    Could you write that post about requests/questions.

  2. Gaurav says:

    I was very impressed with the IE9 presentations last week and I’m glad you put these up. But I’m very disappointed about the XHTML parsing and error handling. This blog post explains the issue: http://bit.ly/b8kITm

  3. Tony Ross [MSFT] says:

    @Gaurav

    I commented on the linked blog post, but I’ll reply here as well for completeness.

    An HTML parser is not being used for XHTML and SVG, nor is any attempt at fixing up the content being performed. The work to display XML parsing errors in IE9 simply hasn’t been completed yet.

    From the IE9 Platform Preview Release Notes(http://ie.microsoft.com/testdrive/info/ReleaseNotes/Default.html):

    > XML Parsing Errors (affects XHTML and SVG)

    > No notifications are currently displayed for XML parsing errors encountered

    > while parsing XHTML or SVG. Note that even without notifications, parsing

    > correctly stops and only content occurring before the error is rendered on

    > the page.

    FWIW, Chrome and Safari also display content occurring before the first parse error. They render the error message just above the page content.

    Hope that helps clear things up!

  4. carlos says:

    i note that in order to see the videos you ask to install a  "plugin" ( in 2010 ! a plugin! my god 😉

    Please could you provide the same videos using the new video element in HTML5?

    Thanks in advance

         carlos

  5. Yes, but... says:

    …which codec would you expect them to use to post the videos? If they post in h264, the Firefox kids complain. They don’t seem likely to post in Theora format, given the IP fear.

  6. Andrew says:

    @carlos you can download them in a variety of formats here: http://live.visitmix.com/videos/

    wmv, high-bitrate wmv, and mp4. The plugin it wants you to install is silverlight for viewing inside the browser (which works a good deal better than flash does at the same job for me)

  7. Ted says:

    Interesting presentations.

    I was surprised that Microsoft is adding image support for JPEG XR in IE9, yet there is no word on support for Animated PNGs (APNG) or MNG formats. Both of these formats are supported by other major browsers like Firefox. It would be nice if IE9 at least supported one of them…

    http://en.wikipedia.org/wiki/Animated_Portable_Network_Graphics

  8. TheCycoONE says:

    @ted: I’d categorize apng along with blink and animated gifs as another piece of technology the web doesn’t need.

  9. JM says:

    Is IE9 going to support CSS3 calc()?

  10. Tony, thank you for clarification regarding display of XML parsing error messages in IE 9. I posed a couple of follow-up questions on the blog (one of them is difficult to reproduce here because it has a code example):

    http://bit.ly/b8kITm

  11. carlos says:

    @andrew, thank you for the links!

  12. George Wurst says:

    @Ted: You are wrong, there is no more MNG support in Firefox… Neither do Opera or Webkit based browsers support this format. However APNG is supported by current Firefox and Opera versions.

  13. Matthew Raymond says:

    @JM:

    Currently, IE supports what are called "Dynamic Properties", which use Javascript to perform actions similar to calc(), but that’s been deprecated and only works in compatibility mode. The calc() function is far simpler and doesn’t use Javascript at all, making it easier to implement and less disruptive to a browser’s security model.

    Currently, no browser supports calc(), although both Gecko and Webkit have tracking bugs with patches.

  14. hAl says:

    It would be nice if the JPEG XR code was backported to IE8 as well.

  15. Many says:

    Please tell every presenter to TURN OFF their mobile devices before going on stage.. the static feedback is very annoying!

    This should be a known for any professional presenter.

  16. Taylor says:

    Checked out the dev tools in IE9!

    1.) HTML source is shown with the correct tag case (lower)! Great! Any chance this will be backported to the IE7/IE8 dev tools?

    2.) Text nodes in the source still have a useless prefix – please remove it!

    3.) element names in the style tab (inherited) are NOT lowercase – this still needs to be fixed.

    4.) There is too much whitespace around the colon on CSS properties and HTML attributes.

    5.) Pressing Enter is still required on all attribute/property changes/additions to have changes take effect. This is highly anoying when you have just typed a large style string and then mouse click outside of the edit box to see the changes or grab additional text content – it should save all changes on Blur (by Enter, Tab, or de-focus)

    6.) attributes in the HTML source tree are still appearing in 1990camelCase vs. lowercase/true source case.  Please fix that! It makes it look like our code is buggy!

    7.) The "edit" HTML source is all IE6 TagSoup case.  It should be 100% pure source, not IE’s legacy qUiRkShTmLmOdE.

    8.) The "edit" HTML source does not include the body tag, the head tag (and any of its content) or the html tag / doctype.  This tool is therefore just shy of absolutely useless.

    9.) Networking tab is an "about time!" item, so glad it was finally added.

    10.) Select by click doesn’t highlight the elements as you mouse over them allowing you to easily identify which element you are getting (e.g. a div wrapping a span) (this is a bug since IE8 supported it)

    11.) Color picker picks up anti-aliasing on text if you have Clear-type turned on.  On one hand this makes sense but it is a bit confusing if you aren’t expecting it e.g. if the font color is #0000ff, then it is odd to get a cyan or purple color back.

    12.) I count about 9 different modes that IE9 can be rendering/parsing JavaScript in.  I see this as a massive nightmare to maintain.  I’m not sure how to make it better, but expect developers to get more and more frustrated with IE with every version released.

  17. stevewebdev says:

    I watched the various presentations but have a few comments about the High Performance one by Jason Weber.

    Most of the content was good (and likely known by pro developers) but there were a few new items I hadn’t seen.

    Slide deck is on the video page.

    #12.) Cache function pointers (slide 75) which refers to examples on slides (55 and 56)

    I watched this and groaned that it looked like micro-optimization but conceded that I didn’t have test data to base that decision on.

    I just ran several benchmark tests in Firefox, Chrome & IE8 (50,000 calls – dozens of times) and discovered no determinable difference in speed using a local pointer vs. a global one.

    I’m wondering if there is more to this picture? Does it become an issue on large sites because IE pollutes the global namespace with every DOM element that has an ID or a NAME attribute? Or is this something that gets worse in IE9 that we should be aware of?

    I would presume that modern JIT compilers would optimize for this kind of stuff anyways.

    The second thing I noticed was:

    #15 Minimize DOM Interations (slide 75)

    refers to slide (62 and 63)

    The example shows how to reduce lookups (greatly desired) but fails (as did the talk) to indicate that looking up:

    document.body.all.lside

    document.body.all.rside

    document.body.all.result

    is bad with bad written all over it.

    Since "lside", "rside" & "result" are all unique items, they should have an id attribute set, thus:

    document.getElementById(id);

    would be the preferred lookup method, or even more simple (using jQuery)

    $(‘#lside’)

    $(‘#rside’)

    $(‘#result’)

    The **only** time developers would be advised to use the ".all" collection is when they are writing a function that is specifically designed to provide a workaround for a broken DOM method implementation in legacy versions of IE (e.g. IE6 & IE7)

    Other than those 2 items, the presentation was great.  I’m surprised that so many of the items were "news" to many, but glad the information is getting spread.

  18. EricLaw [MSFT] says:

    @stevewebdev: The book “Even Faster Websites” has a section on the cost of scope resolution, with performance charts: http://oreilly.com/server-administration/excerpts/even-faster-websites/writing-efficient-javascript.html

  19. stevewebdev says:

    Hmm,  yeah, the charts do indicate a perf gain (esp. in IE browsers)

    Doing some quick math…

    If I reference a global, from 4 levels deep in scope 200,000 times I can save ~100ms if I have a local pointer.

    100ms/200,000iterations = 0.0005ms saved for each iteration.

    Since most stuff I do would likely not iterate over more than 250 items… I could save 0.125ms!

    I’ll certainly keep it in mind, but yeah definitely micro-optimization… and the impact is really only geared to IE browsers.

  20. learned something says:

    The performance video was the most interesting. I’m making a lot of these mistakes today without knowing. You should publish a reference guide on performance like the orielly code samples series which shows developers exactly what we need to change with checklists and how. It’s easier to reference a book and checklists than trying to find the right section in a video. I would like to request an official reference guide. Thanks for making these videos.