Today Rc in Download !!

“IE in San Francisco (2/10) – http://www.winrumors.com/internet-explorer-9-release-candidate-rc-now-available-to-download/

• Tabs should be above the address bar.  Most the major browsers are starting to adopt this approach.  It makes no logical sense for the address bar to be above the tabs as the address bar is related to the tab you are viewing and not the entire window.  Therefore it should be contained within the tab.
• There's too much waisted space above the address bar.  Previously the title would sit here.  If they're going to only leave the title in the tab then surely going for the chrome approach of placing the tabs right at the top would fit better.
• There's an over use of gradients.  Stronger colours with more subtle gradients look far more appealing, such as chrome and visual studio 2010.
• The back and forward buttons look terrible.  They're fair too grainy.

That's all i can think of for now.

1 hour ago, jgd12345 wrote

• Tabs should be above the address bar.  Most the major browsers are starting to adopt this approach.  It makes no logical sense for the address bar to be above the tabs as the address bar is related to the tab you are viewing and not the entire window.  Therefore it should be contained within the tab.

Except you don't view two tabs at once, only a single tab is active. I like the positioning of the address bar in FF3. It shrank way too much in IE9. And darnit, I want search in a separate box

4 minutes ago, CKurt wrote

@blowdart: They did improve searching, if you search for "everthing about .net" is will no longer try and access a .net address.

And you can make the address bar and tab bar separate. Hurrah. Now if only I could put the menu bar up top too.

http://download.microsoft.com/download/1/0/A/10AD7DEC-7DAB-492B-AE28-237B56F0BFFF/InternetExplorer9RCNewFeaturesSummary.pdf

http://download.microsoft.com/download/F/8/B/F8BFDCA5-316E-4689-9399-896E04F8835E/InternetExplorer9RCProductGuide.pdf

there is the sunspider result inside the product guide

42 minutes ago, CKurt wrote

@blowdart: They did improve searching, if you search for "everthing about .net" is will no longer try and access a .net address.

More importantly, you can designate you're searching by prepending a '?'. Searching for ASP.NET is now possible by typing "? asp.net". As far as I'm concerned, this fixes the "onebox" (really?) and I'm content with losing the seperate search bar.

C

EDIT:  It crashes everytime I close a tab.

Unhandled exception at 0x68767939 in iexplore.exe: 0xC0000005: Access violation writing location 0x00000004.

EDIT2:  Hmm, restarted IE9 and now it's not crashing. 

EDIT3:  After logging into Channel9 and posting, then opening a new tab, and closing it, it crashes again.  Coffeehouse forum open in the first tab, and anything else in the second tab, it seems, but only when logged into Live.

EDIT4:  Nothing to do with signing in ... it's just not 100% consistently happening, but is happening most of the time (7/10 times, roughly).

EDIT5:  I think it's one of the addins from the beta.  Disabling them all.

EDIT6:  10/10 tries with add-ons disabled and no more crashes.  So that's good.

But on the other hand, sites like beautyoftheweb, suggest that not everybody at Microsoft understand the web yet. Slow, very slow. I'm greeted with a white page for a few seconds, whaaaat the!?!?! Then again this blog also attest to that. Slow, AND greeted with a warning every time i enter (about nonscure items in a secure page). Microsoft don't quite grok the web yet. Google does.

I am just getting the IE logo on a white background. I get the icons on the extra function in the jump list i.e. CoffeeHouse for CH9 and Inbox for Hotmail, just not the icon for the taskbar or the thrird item up in the jump list (the website title)

Any help on this would be much appreciated.

Duncan

Can anyone tell me if the Menu bar and Favorites bar can now sit between the Address bar and the Tabs bar, to emulate the toolbar locations in IE8 ??

I'd really like to know that I can deploy it, and not have to deal with the "it's all different, and now I can't do my job - fix my computer!!" complaints, that happen every time the UI is changed.

Will let you know how i go

For me the truth is you hardley ever need to use them, now that seaching is so easy, but this is just a matter of opinion

I agree that it's trivial stuff, and should be something easily adapted to, but anyone who has worked as an IT Manager or CIO can tell you... users don’t willingly adapt to changes in their work environment, and use anything new as an excuse for why they can’t achieve xxxxxx or why they failed to complete yyyyyy by the deadline, and the higher up the managerial ladder you go, the louder and more accusational those complaints/excuses become.

This already sounds like another “the IT dept is to blame” battle-zone.

Only thing is I hope my bank works with IE9 RC (Wells Fargo). In the past when I installed a beta or RC, the bank website says it doesn't support that version...

I was happy to see that the site where I do my taxes noticed I had the beta and notified me that they were confident enough that they were compatible that I could continue, but that there might be visual glitches. That made me happy because a lot of big sites tend to have their heads up their rears when it comes to stuff like that.

I often read that it is too costly to migrate?

So what is Microsoft offering in terms assistance?

I think where it gets expensive is making sure that the intranet applications still work. Many companies have spent a lot of resources on tweaking these applications to work in IE6, and bringing in a new browser that breaks all of their hacks, modifications, and workarounds is seen as too big of a project. Never mind that they could probably save a lot of money replacing their ancient web applications in the first place.

This is, of course, based on my own experience. YMMV

What are Microsoft doing the make the conversion automatic and less expensive,

Here's your IE6 app, let Microsoft apply some magic and now you have and IE9 application.

It the Magic part, Microsoft should be providing.

Automagic conversion.

And Due to areo transparency, my tabs are too dark. Black tab title is harder to read on top of dark tab color.

And I don't think I will get used to fav. The blue arrow of fav is point to right when it is outside of screen? That just doesn't make any sense. And then when you pin it, it is on the left, not one right? How am I suppose to get used to it when the behavior is so confusing.

And, I think I kept getting logged off from C9 when I close the browser.

- all the people who never print a webpage and don't care anyway

- all the people who know how to right-click

- all the people who just go Alt+F P out of muscle memory

- all the people who saw Eddie Izzard's "Glorious". (if you really must, you can skip the first 3 minutes)

Having spellcheck everywhere along with adblock kind of is addicting. No matter how good IE9 is, it is hard to go back to something without those features. Especially since Firefox has a nice clean look, as well as GPU Accleration and DirectWrite.

I wonder why they added the ability to bring all the bars from IE8 back... is anybody actually doing that?

10 minutes ago, littleguru wrote

I wonder why they added the ability to bring all the bars from IE8 back... is anybody actually doing that?

Considering my dad still has the menu bar visible by default in IE8, it's likely he'll do exactly the same thing in IE9 also.

I guess people take to using software, like riding a bike, or driving a car. You become used to where things are, and operate thoughtlessly when doing something. Software has the virtue of not always expelling users when new versions come out that are inured to the previous, though it costs more to develop and support and more importantly for business teach and pay people for little to no value in return. Hoe does IE 7, 8 or 9 make their employees more productive?

MS should start treating IE as a full standalone app. Then you can have your main IE (which also provides the required OS rendering support), and one or more additional versions of IE. Let's say you install IE9 which is now your main browser. In addition, you also install IE6 but it's zones are configured to only allow intranet connections. Then people can use IE9 to browse on the internet, and use IE6 to use all those old LOB applications.

Can someone explain to me why this won't work (other than removing the artificial restriction of preventing multiple versions of IE)?

I agree, I have been advocating that a lot and a lot of people kept saying it is bad. I don't care. Supposedly .Net already solved DLL hell, IE preview is fine, and I want to have multiple versions installed.

They always blah on applications using it and depends on it, but, honestly, I am sure the application can be locked to a specific version using few lines of code.

It is like those appLocale excuses. Most of time applications don't talk to each other. I just want to play Japanese game for God's sake, and most people do the same. But, we are forced to restart Win7 (XP is ok) to change language. And the app is just a stand alone game.

Excuses over excuses.

In this case, it works much faster in Chrome. Any one have any thoughts as to why?

* I compared the IE9 rendering to Opera and imagine my surprise when I saw that Opera also renders its text just as poorly. IE8 seems to be in a class of its own in rendering text on currently available displays. I'm really disappointed by this revelation since if the agenda is to "standardize" then that can only mean "lowest common denominator" ie. all browsers will render text unreadable to make web designers happy = have text layout perfect rather than have it readable.

I reported this to Connect as a bug against IE9 beta, and it was closed as a duplicate, but it's still not fixed. 

I got the problem all the time with IE9 beta (never with IE7 or IE8), then I installed IE9RC1 expecting it to be fixed, and I didn't run into the problem for the first two days, but then sure enough, the bug has started occurring again.  I stopped using IE9 beta because of this, and as good as IE9 RC1 is, I won't use it if this bug isn't killed; I don't have the patience to jump through hoops to use a browser.