All posts tagged ‘IE’

File Under: Browsers, privacy

Google Tricks Internet Explorer into Accepting Tracking Cookies, Microsoft Claims

Google was caught last week bypassing default privacy settings in the Safari browser in order to serve up tracking cookies. The company claimed the situation was an accident and limited only to the Safari web browser, but today Microsoft claimed Google is doing much the same thing with Internet Explorer.

In a blog post titled “Google bypassing user privacy settings” Microsoft’s IE Corporate Vice President Dean Hachamovitch states that “When the IE team heard that Google had bypassed user privacy settings on Safari, we asked ourselves a simple question: is Google circumventing the privacy preferences of Internet Explorer users too? We’ve discovered the answer is yes: Google is employing similar methods to get around the default privacy protections in IE and track IE users with cookies.”

Hachamovitch explains that IE’s default configuration blocks third-party cookies unless presented with a “P3P (Platform for Privacy Preferences Project) Compact Policy Statement” indicating that the site will not use the cookie to track the user. Microsoft accuses Google of sending a string of text that tricks the browser into thinking the cookie won’t be used for tracking. “By sending this text, Google bypasses the cookie protection and enables its third-party cookies to be allowed rather than blocked,” Microsoft said.

The text allegedly sent by Google actually reads “This is not a P3P policy” and includes a link to a Google page which says cookies used to secure and authenticate Google users are needed to store user preferences, and that the P3P protocol “was not designed with situations like these in mind.”

Microsoft said it has contacted Google to ask the company to “commit to honoring P3P privacy settings for users of all browsers.” Microsoft also updated the Tracking Protection Lists in IE9 to prevent the tracking described by Hachamovitch in the blog post. Ars has contacted Google to see if the company has any response to the Microsoft allegations, and we’ll update this post if we hear back.

UPDATE: It turns out Facebook and many other sites are using an almost identical scheme to override Internet Explorer’s privacy setting, according to privacy researcher Lorrie Faith Cranor at Carnegie Mellon University. “Companies have discovered that they can lie in their [P3P policies] and nobody bothers to do anything about it,” Cranor wrote in a recent blog post.

UPDATE 2: Google has gotten back to us with a lengthy reply, arguing that Microsoft’s reliance on P3P forces outdated practices onto modern websites, and points to a study conducted in 2010 (the Carnegie Mellon research from Cranor and her colleagues) that studied 33,000 sites and found about a third of them were circumventing P3P in Internet Explorer.

“Microsoft uses a ‘self-declaration’ protocol (known as ‘P3P’) dating from 2002 under which Microsoft asks websites to represent their privacy practices in machine-readable form,” Google Senior VP of Communications and Policy Rachel Whetstone says in a statement e-mailed to Ars. “It is well known—including by Microsoft—that it is impractical to comply with Microsoft’s request while providing modern web functionality.”

Facebook’s “Like” button, the ability to sign into websites using your Google account “and hundreds more modern web services” would be broken by Microsoft’s P3P policy, Google says. “It is well known that it is impractical to comply with Microsoft’s request while providing this web functionality,” Whetstone said. “Today the Microsoft policy is widely non-operational.”

That 2010 research even calls out Microsoft’s own msn.com and live.com for providing invalid P3P policy statements. The research paper further states that “Microsoft’s support website recommends the use of invalid CPs as a work-around for a problem in IE.”

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

File Under: Browsers

Microsoft Touts Plugin-Free Web, Offers Desktop Fallback for Flash

Microsoft’s new version of Internet Explorer has barred browser plugins in the Metro environment. But Microsoft has revealed a method that plugin-dependent websites can use to leap over Metro’s walls and reach the green fields of the conventional Windows desktop, where Flash is still allowed to roam free.

The relevance of proprietary browser plugins is declining as standards-based web technologies mature. Native web technologies don’t yet supply complete functional equivalence with the capabilities of plugins, but the open web has the advantage of greater ubiquity.

The ubiquity of native web standards over proprietary plugins is set to get a major boost from Microsoft with the launch of Windows 8 and Internet Explorer 10. As we have previously reported, the next major version of Microsoft’s web browser will not display plugins in the Metro environment, which will be the default shell in Windows 8.

A plugin-dependent website prompting the user for permission to run on the desktop. Image courtesy of Microsoft

Microsoft has published a series of posts in its official IE development blog that discuss the implications of this change and what it means for users and web developers. In a new post published this week, IE program manager lead John Hrvatin highlighted the advantages of plugin-free browsing and emphasized the need for web developers to start supporting users who browse in environments that don’t have plugins enabled.

“The transition to a plug-in free web is happening today. Any site that uses plugins needs to understand what their customers experience when browsing plugin free. Lots of web browsing today happens on devices that simply don’t support plugins,” he wrote. “Metro style IE runs plug-in free to improve battery life as well as security, reliability, and privacy for consumers.”

A growing number of websites that rely on browser plugins already offer a standards-based fallback for users who are browsing on popular plugin-free devices such as as the iPhone or iPad. Microsoft has previously discussed some of the steps it is taking to ensure that those websites serve their plugin-free content to Metro users.

There will still likely be many Flash-heavy websites, however, that can’t accommodate users who are browsing without plugins. In the blog post, Hrvatin explained that such websites can ask the user for permission to jump to the conventional Windows desktop and launch the windowed version of Internet Explorer, which will have full support for plugins.

Web developers can get the browser to display the prompt by including the special requiresActiveX=true property in an X-UA-Compatible meta tag or HTTP header. Hrvatin cautions that this feature is included for transitional purposes and is intended to serve as a last resort. The preferred behavior is still for web developers to display a plugin-free version of their site to users who are browsing in the Metro environment.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

File Under: Browsers

The Curious Case of Web Browser Names

Chances are your web browser is open all day, every day. Whether it’s Internet Explorer, Firefox, Opera, Chrome or Safari, the browser is the single most important piece of software most of us use. Given its central place in our lives, some history seems in order. If you’ve ever stopped browsing long enough to wonder why Safari is named Safari or where in the world the word “Mozilla” comes from, we have some answers for you.

Martin Beeby, a developer evangelist at Microsoft, has put together a nice little history of web browser names. Some are obvious — Internet Explorer came about because it was “a name that gave people a clear idea of what the product did” — some are less so, like Opera, which was apparently chosen because, among other things, “the Opera is fun.”

With the exception of Opera and IE, none of Beeby’s name origin stories come directly from the companies behind the browsers, so take all of these with a grain of salt. For instance, no one seems to know the exact origins of “Safari”, though the Beach Boys’ album seems like a reasonable guess — surfing the web, Surfin’ Safari… get it? The WebKit blog is named Surfin’ Safari, which might lend some credence to that story, but the name also nicely ties in with the notion of exploring the wild and connotes some of the same images as “explorer” and “navigator”.

Perhaps the least obvious name in the bunch is Firefox’s parent company Mozilla. Beeby cites a well-known story that the name that was derived by combining the words that were its original goal — “Mosaic Killer.” Webmonkey has heard another version of that story that claims the word “Godzilla” was the inspiration for “Mozilla,” a Godzilla-like force that would destroy Mosaic.

Beeby doesn’t offer any stories for less well-known browsers, like Konqueror, which, as the story goes, was going to “conquer” what IE and Netscape had “explored” and “navigated” respectively. The allusion didn’t really pan out, but, when Apple came along and ported KHTML to form WebKit, the developers did name their early efforts after a famous conqueror — Alexander.

For more details, and to learn where the names Firefox and Chrome come from, be sure to read through Beeby’s post.

File Under: Browsers

Microsoft Bids Farewell to IE 6 as U.S. Use Drops Below 1 Percent

IE 6 falls below 1 percent in the U.S. Delicious.

Microsoft is throwing itself a little party to celebrate the demise of Internet Explorer 6. Based on the latest data from Net Applications, the much-maligned browser recently fell below 1 percent in the United States, which prompted the IE Team to celebrate with a cake on IE 6′s grave, as it were.

Roger Capriotti, director of Internet Explorer marketing, writes, “IE 6 has been the punch line of browser jokes for a while, and we’ve been as eager as anyone to see it go away.”

The U.S. joins Austria, Poland, Sweden, Denmark, Finland and Norway in the less-than-1-percent category and several more nations are not far behind. Microsoft also recently announced that it would begin forcing IE updates for those that have opted into automatic Windows Updates, which should help further reduce the number of both IE 6 and IE 7 users.

Unfortunately for web developers the worldwide browser market share picture is not quite as bright. Internet Explorer 6 still has a considerable user base in China, where it tops 25 percent, and much of the rest of Asia hovers in the 5 percent range.

The other bad news is that despite the demise of IE 6, compensating for the shortcomings in both IE 7 and IE 8 remain necessary parts of a web developer’s job. And, given that Windows XP users will never be able to upgrade beyond IE 8, IE 8 will likely take IE 6′s place as the official pain in the ass of web developers everywhere.

Photo from the Windows Team Blog

File Under: Browsers

Internet Explorer 10 Platform Preview 4: Windows 7 Users Need Not Apply

Microsoft has released the fourth preview of Internet Explorer 10. As is the case with previous Platform Previews, the release is aimed at developers: the new features are important to those creating rich, complex web applications, but will have less impact on web users.

However, even web developers might struggle to get too excited about the latest preview, because they probably won’t be able to run it: it only works on the Windows 8 preview release that Microsoft shipped at its BUILD conference in September.

Safely share data between domains with IE10's CORS

The new features include Cross-Origin Resource Sharing (CORS), JavaScript typed arrays and binary file manipulation, and HTML5 video subtitling. Typed arrays and support for binary files enable much better performance for JavaScript applications that handle binary data, such as images and audio.

CORS provides a safe way for JavaScript applications to use services offered by different providers. Traditionally, JavaScript has been restricted by the same-origin policy: a script can only have full access to content that is hosted at the same domain, port, and protocol. This provides security by preventing theft of, for example, cookies and page data by objects included from other sites.

CORS allows one application to expose its data to another application even when the same-origin policy would otherwise deny such access. This is useful for creating “mashup” applications that combine web services from multiple different providers.

Microsoft has positioned its Platform Previews as a way to let developers test and provide feedback on new features so that they can inform Microsoft of bugs, and guide the development of new specifications. The first two Platform Previews for Internet Explorer 10 were made available to users of Windows 7. This preview, however, is not. If you want to use it, you’ll have to use the Windows 8 Developer Preview.

The third preview was in the same position; Microsoft did not release a Windows 7 version of Platform Preview 3. Instead, the version of Internet Explorer that shipped with the Windows 8 Developer Preview was the third preview. Though Internet Explorer 10 will support Windows 7 when released, web developers wanting to test the software now will have to use an unsupported, not-even-beta operating system to do so. And while they can do so using a virtual machine, doing so will disable most or all of the hardware acceleration features found in the browser, making it a second-rate experience.

This is a decidedly odd move. Internet Explorer 10 is going to be fundamental to Windows 8 in a way that no past version of the browser has been. HTML and JavaScript are one way for developers to create new touch-friendly Metro-style applications, and this support will be built on Internet Explorer 10.

But as important as Metro-style applications are to Microsoft, the browser will still have a substantial user base on Windows 7, and the web developers of today are far more likely to be using Windows 7 than they are Windows 8. Regular non-Metro web applications still matter. Effectively excluding this group from the preview—the group most likely to have valuable feedback and insight—makes one wonder what the entire purpose of the scheme is.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.