Skip to main content

7 errant UI features in IE9

IE9 has some really cool tech upgrades.Here are a few errant UI features that makes IE9 less than perfect. It almost gives the impression that the UI engineers did not do a stellar job. or IE9 UI is a half baked cake.

1. Address bar, and the Tab bar.

The browser defaults with tabs shown alongside a compact address bar.
image

For what it is worth, the tab bar can be configured to show in a separate row. but it cannot be configured to be shown above the address bar. All tab enabled browsers (Firefox, chrome, safari does it little differently) relate to the notion that address bar belongs to the tab instead of the browser itself. So they show tab bar "containing" the address bar. But IE seems to have ignored this.

2. Back button

There is useless screen area that is taken up by the weirdly large back button. and there seems to be no way to configure it to become smaller.

image

Firefox 4, on the other hand, makes a strong point to allow users to "use smaller icons" – to reduce screen space.

image

3. Notifications

Where safari and Firefox have notification bars on the top, IE9, weirdly, positions them at the bottom with a unique coloring scheme that does not blend with windows scheme like traditional windows applications. Believe yellow is threat level?

image

4. Refresh and Stop button

These are mutually exclusive. In that, the status of the page can dictate only one be shown, while the other could be hidden. This could have saved screen space, may be not too much, but why have two ambiguous action buttons shown at the same time? FF – finally – merged the stop and refresh button to save screen real estate. IE9 still shows both.

image


5. The Star.

Stars recently have made an unofficial standard to one click bookmark/favorite (thanks to Google). IE9 seems to be defiant of the fact and instead shows a floating favorites bar on the left when you click on it. and then you could add to favorites. So to favorite a site, you need two precious clicks.

image

6. Favorites floats on left, docks on right

The afore mentioned aberration, gets even weird, the left-floating favorite bar flies to the right when you "dock it"

image

7. The title bar is useless!

IE9 made the title bar completely useless. A empty strip of transparent background with NOTHING in it but the 3 window control buttons on the right end, is a stunning difference from other 2011 products from Microsoft. For example office 2011 apps have a save, back and forward, an formatting menu's right on the title bar. and if FF4 can manage to get tabs on the title bar (image above), why can't IE9?

image

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...