IE7 Details Emerge

Varg Vikernes writes "Microsoft Watch has a story about new features we can expect in IE7 (code named 'Rincon') which they gathered through Microsoft's key partners. Apparently we can expect 32 bit PNG support, native IDN support, new functionality that will simplify printing from inside IE and, of course, tabbed browsing. The new browser also will likely include a built-in news aggregator. Apparently an important factor is security."

Comments

Re:Interesting Codename...

[Rude Turnip]

Microsoft likes to use codenames based upon the names of mountains. XP was Whistler for instance. There is a "Rincon" mountain range in Arizona.

Innovate???

[Horrortaxi]

I'm not sure I'd go so far as to say they'll innovate. Innovate means they will break new ground and offer something you haven't seen before. They'll offer what all the other browsers have had for 2 years and that's it. No innovation, just keeping up with the Jonses. Now maybe they'll have some innovative marketing plan or some innovative predatory practices that will allow them to rincon the browser market again. That's where Microsoft really innovates.

Re:Microsoft has finally been forced to innovate

[RoadWarriorX]

It seems the threat from Firefox is forcing them to innovate and improve in a market they once took for granted.

Have you RTFA? Tabbed browsing, IDN support, RSS news aggregator all available in Firefox in some form. So, where exactly is the innovation? Possibly anti-spyware integration??? That's like a mouse setting a mouse trap for itself.

Additionally, Microsoft's "improvement" is really their way of saying that they are now in "catch up" mode.

I don't mean to flame you, but customers should not look forward to the next version of IE in six months or so, when they can get virtually the same features today with Firefox.

All I need to say is "Why Even Bother".

Re:security

[LiquidCoooled]

Actually, a fairly reasonable visual tradeoff could be to display all extended characters in a different color.

For instance, if the extended characters were displayed in purple, but the normal characters remained black, then you could continue using it, and KNOW that its a mixed domain.

Infact, just typing that gives another solution, have mixed domains (std and extended) come up in a totally different size/style.

That way, all normal domains look normal, and all extended domains also look normal, but those using a combination are glagged as such.

just a thought.

Re:Um...WTFN?

[AstroDrabb]

I would have expected a big push for compliance with the whole .NET campaign they are pushing, a lot of it revolves around web app creation

MS's .Net sends down different HTML depending on whether you are making the request with an IE browser or a non-IE browser. It is one of the things I really _hate_ about .Net. I actually like C# a lot and use it every day, I just can't stand how MS tries to lock out everyone.

For example, in a .Net web app, you can add validators. So if you have a text input, you can validate that it is not empty when a form is submitted. This is _very_ simple JavaScript. However, with .Net, if you are using an IE browser, you will get an error message without going to the server. If it is a non-IE browser, it requires a round-trip to the server. How crappy is that? Like the people at MS could not write some simple standards compliant JavaScript to check if a freaking field is empty or not before a form post.

That is just one example. There are tons of others with the "built-in" web controls with the .Net framework that have all been made to work well in IE and have limited functionality in non-IE browser.

Because of crap like MS does with .Net, it has made me use Java/JSP for web apps. At least then I can control how well my applications can work with different clients and not be subjected to MS trying to make the world MS-only.

I really don't know what is wrong with MS. I mean, not all of their products are bad, and I really like some of MS's products. If they would just _compete_ and stop listening to their marketing/business @ssholes MS probably would not be too bad. All MS needs to do is compete and allow others to try to compete. MS needs to stop _all_ of their lock-in crap.

Seriously, look at the amount of dedication that OSS programmers show. MS could have that same loyalty if they just gave a _little_ back to the community. I am not talking about their crap "shared" source license or the wimpy XML setup wizard they released. I am talking a few major contributions of their code that they let a _community_ improve could make a world of difference to MS and their reputation.