Framework Madness!

And other adventures C# and …

Posts Tagged ‘internet explorer

IE 9 Preview 4 – How much HTML 5 support? Should it?

with one comment

I’ve been wondering how to get thru the hype of Html 5 support in IE 9. That’s not to say that the improvements they have made aren’t welcome – they very much are. But Html 5 is larger spec than just audio, video and canvas – and I’ve been wondering how broad Html 5 support goes.

I found a site called that will test your browser for HTML 5 support. How does IE 9 preview 4 fare?


That’s right – 96  out of 300? You say you want details? Here you go:


Related specifications


Clearly, while the IE team has done great work in bring IE forward with the IE 9 previews, clearly there is a lot more HTML left unsupported then currently in the latest preview. But should IE 9 have full HTML 5 support? Good question. If you take a look at the HTML 5 document at the W3C you’ll notice it’s “working draft” – the proposal in still flux. I would guess that MS is just expanding “de facto” standards support and hitting the highlights, where other features such as IndexDB, Web Applications, Html 5 Forms and other elements will come – eventually. But will they come in IE 9? Only MS knows the answer to that one. Let’s just hope we don’t have to wait three years until IE 10 to find out.


Written by Lynn Eriksen

August 5, 2010 at 10:09 am

Posted in Uncategorized

Tagged with

Impressions – Office 2010 Beta and Thoughts on the Future of IE

leave a comment »

The other night I tried out the Office 2010 Beta by using Click-To-Run to install. Nice experience! Very nice! All I had to do was enter a key, let the installer whirl for a few short (very short) minutes and then I was presented with an open Power Point app that highlights new office features as well as showing off Power Point’s new GPU animations. Best of all I didn’t have to uninstall my current version of Office just to try the beta.

Now this all happens thru app-virtualization which downloads the apps incrementally, and allows the apps to be available when the majority of the components are installed. BEST OF ALL – the app will be updated AUTOMATICALLY as updates become available.

Now … you can more than likely see where my madman web-dev self is going. IE should be delivered via app-v and should be delivered once more and for always. Did I just say that? Yes. Let’s look at the Pros and Cons.


  • Security would always be up to date. 

    Considering the blow-back from IE 6 & 7 in regards to the recent Google hacking incident having worry free automatic updates would be a major plus.

  • Progressive deployment of web standards.

    IE could have ‘feature modules’ added along with other upgrades added to the mix as they become available. No more needing to get that next version of IE to get that next generation feature, and then wait for two years for everyone to catch up. 

    Want proof this would work? Check out these FireFox install-base stats. Notice the rapid transition to v 3.5 that is underway? Don’t you wish the IE transition was that fast?

    If this were done there could be a RAPID, BROAD AND CONTINUING roll out of sites embracing new web standards for a massive number of users one the browser uptake reached critical mass. 

    No more waiting 2 years for that next update. When it’s ready – it ships in a ‘No-brainer’ way to EVERYONE.

  • User Bliss!

    Imagine telling a user ‘Install this version of IE and it will be the LAST version of IE you’ll need to install for a LONG TIME. No – seriously. Updates will be automatic, that includes security and new features.’


  • Moving to a modular release pattern would be very difficult for the IE team.

    An app the size of IE may be very (extremely?) difficult to refactor in such away as to deliver progressive updates via app-v. As an example of modular design benefits the IIS team for version 7 did a MAJOR redesign and they have rolled out a LARGE number of out-of-band updates. They’re very competitive and timely.  

  • Installed IE components are often application dependencies for 3-rd party apps.

    Even though IE has been gradually pull back out of the OS, it still has a very COSY relationship with the OS and lost of programs deployed depend on IE components being installed. My guess is that app-v would make this difficult to manage.

    So putting IE in app-v would not be a singular issue unlike browsers on windows. 

  • Corporate roll-out would always be slower.

    Like it or not corporate IT for the most part always moves slower. They want to test the updates, they want to deploy on a schedule. Understood. There would need to be some way to allow corporate users to prevent feature/modular updates for a short period of time (3 months). Would this even work? How would you version for this x-ua-compatible?

  • UI interface changes would be jarring.

    This is probably the least amount of concern. As long as the UI undergoes a slow transition you could have a browser update/welcome page that shows the new features that have been automatically updated for them. New installs wouldn’t be a problem because the app-v installer would always download the freshest version of the app.

Written by Lynn Eriksen

January 27, 2010 at 7:08 pm

IE quirk with iFrame and position: relative

with one comment

I have a project I have been working on that involves promoting realtor properties to multiple listing sources such a google, trulia and others. On one site in particular my client had noticed that there was as an issue where the property page form his web site would not show inside an iframe on the the listing web site using IE. I managed to trace it down to a style sheet issue. For some reason, cannot remember, I had put the css attribute ‘position: relative’ on the body and html elements. This passed the WC3 validator, but IE didn’t like this so the page would not show at all inside the iframe. Removing the attribute solved the problem.

Note: this was not error with FireFox.

Written by Lynn Eriksen

April 3, 2009 at 12:28 pm

Posted in Uncategorized

Tagged with , ,

Stick that Footer – No, really IE, I mean it!

leave a comment »

I was doing layout for a revision of today and I was following a fairly well established pattern of using CSS to absolutely position a footer at the bottom of the page – always and regardless of page length. In the process of trying to get the CSS to work I stumbled on a great, concise tutorial on how to do this. Followed it all, again, and I got it working in Firefox and Safari but sure enough I had trouble with IE 7.

Well, I think I found a solution. The IE7.js script does a good job of fixing up IE 6 difficulties and making it work similar to IE 7. But one thing I also remembered is that there is an IE8.js script (here is the link to both on Google Code) that can fix up issues with IE 7. Sure enough, attaching the the IE8.js script fixed it up nicely. No complaints here.

Written by Lynn Eriksen

January 16, 2009 at 7:55 pm

Posted in Uncategorized

Tagged with ,