IE9 and Privacy: Introducing Tracking Protection

아티클
12/07/2010

The feedback and conversation on IE9’s Platform Previews and Beta to date from many different communities has made the IE9 development process, and product, substantially better than previous releases. The discussions around hardware-accelerated HTML5 and same markup with the developer community, for example, have informed many changes to the product. Thank you for using it and providing feedback.

In general, we’ve focused this blog on engineering issues. In this post, still continuing our pattern of transparency, let’s look at the increasingly important topic of privacy online through the lens of a consumer concerned about being tracked on the web. Here is a brief summary (warning, what follows it is long) of what we intend to deliver in the release candidate of IE9.

Today, consumers have very little awareness or control over who can track their online activity. Much has been written about this topic. With the release candidate:

IE9 will offer consumers a new opt-in mechanism (“Tracking Protection”) to identify and block many forms of undesired tracking.
“Tracking Protection Lists” will enable consumers to control what third-party site content can track them when they’re online.

We believe that the combination of consumer opt-in, an open platform for publishing of Tracking Protection Lists (TPLs), and the underlying technology mechanism for Tracking Protection offer new options and a good balance between empowering consumers and online industry needs. They further empower consumers and complement many of the other ideas under discussion. You can see how it might work in this video:

Some Recent Context

On December 1, 2010, the Federal Trade Commission released a major report on consumer privacy online. You can read the report here. Microsoft has been engaged in dialogue with the FTC, the Article 29 Working Party in the EU, and others in the privacy arena for some time, and has long recognized the critical importance of privacy to our customers. Unlike other topics we’ve discussed on this blog, privacy involves additional complexities beyond technology and product engineering and interoperability. For privacy, many other aspects are at least as important for making progress: public policy, the law and its enforcement, and engagement across several other industries. This increased importance applies both in the recent US report as well as in similar efforts in places like the EU.

The FTC report looks at recommendations in areas like Do Not Track, and others in the industry have discussed potential Do Not Follow solutions. The report asked a series of questions, including:

How can such a mechanism be designed to be clear, easy-to-find, usable, and understandable to consumers?
How can such a mechanism be designed so that it is clear to consumers what they are choosing and what the limitations of the choice are?
What are the potential costs and benefits of offering a standardized uniform choice mechanism to control online behavioral advertising?
What is the likely impact if large numbers of consumers elect to opt out? How would it affect online publishers and advertisers, and how would it affect consumers?
In addition to providing the option to opt out of receiving ads completely, should a universal choice mechanism for online behavioral advertising include an option that allows consumers more granular control over the types of advertising they want to receive and the type of data they are willing to have collected about them?

Perhaps the briefest form of the question concerns consumers who want the option to say “no thank you” to being tracked… what happens to them?

Consensus and Innovation

On the IE team, we’ve asked similar questions and want to make progress operationally as well as in the public discussion. We want to develop (as the recent FTC report put it) “more effective technologies for consumer control” and make progress on the report’s recommendation of “a browser-based mechanism through which consumers could make persistent choices” regarding tracking.

Today, we’re offering an early look at a way to enable operational progress in the privacy discussion.

Let’s take a look at how this might work and then consider how it furthers the conversations we’ve been having with all interested private and public bodies. While the web browser is only one part of the online privacy experience, for many consumers, the browser is a key technology to manage their privacy choices.

By applying principles described in the FTC report like Transparency and Privacy by Design, we can make it easier for consumers to opt out of potential tracking experiences. There is no change to default behavior with respect to privacy and tracking, and consumers need to exercise choice for anything to change.

How (and Why) This Works

Today, consumers share information with more websites than the ones they see in the address bar in their browser. This is inherent in the design of the web and simply how the web works, and it has potentially unintended consequences. As consumers visit one site, many other sites receive information about their activities (you can read more details here). This situation results from how modern websites are built; typically a website today might bring together content from many other websites, leaving the impression that the website appears to be its own entity. When the browser calls any other website to request anything (an image, a cookie, HTML, a script that can execute), the browser explicitly provides information in order to get information. By limiting data requests to these sites, it is possible to limit the data available to these sites for collection and tracking.

A Tracking Protection List (TPL) contains web addresses (like msdn.com) that the browser will visit (or “call”) only if the consumer visits them directly by clicking on a link or typing their address. By limiting the calls to these websites and resources from other web pages, the TPL limits the information these other sites can collect.

You can look at this as a translation of the “Do Not Call” list from the telephone to the browser and web. It complements many of the other approaches being discussed for browser controls of Do Not Track.

What we describe here is providing a new browser mechanism for consumers to opt-in and exercise more control over their browsing information. By default the Tracking Protection List is empty, and the browser operates just as it does today. The list is empty by default for two reasons:

Controlling this aspect of the browser’s behavior is up to the consumer. The browser vendor provides the functionality and respects the consumer’s choices here.
Restricting content from external sites can make some functionality in sites stop working along with the other web mechanisms (cookies, web beacons, and the like) that might be essential to how the sites operate.

Anyone or any organization can create a TPL (it is just a file that can be placed on a website) and consumers can add and remove lists as they see fit, having more than one if they wish. To keep everyone’s experience up to date, the browser will automatically check for updates to lists on a regular basis. One change from similar features in IE8 is that once a consumer has added a list, Tracking Protection remains enabled across browsing sessions until the consumer turns it off.

In addition to “Do Not Call” entries that prevent information requests to some web addresses, lists can include “OK to Call” entries that permit calls to specific addresses. In this way, a consumer can make exceptions to restrictions on one list easily by adding another list that includes “OK to Call” overrides for particular addresses.

We designed this feature so that consumers have a clear, straight forward, opt-in mechanism to enable a higher degree of control over sharing their browsing information AND websites can provide easy to use lists to manage their privacy as well as experience full-featured sites.

There are many points of view to balance in the design of such a feature because the technologies involved create such a complex situation, going well beyond what typical consumers and even many web developers are fully aware of.

While “Do not track” is a meaningful consumer promise around data use, the web lacks a good precise definition of what tracking means. Until we get there, we can make progress by providing consumers with a way to limit or control the data collected about them on sites they don’t visit directly. That kind of control is already technically feasible today in a variety of ways. It is important to understand that the feature design makes no judgment about how information might be used. Rather, it provides the means for consumers to opt-out of the release of that information in the first place.

Tracking Protection lists are “curated” in that people (or organizations) make decisions about what sites are on the list. Internet Explorer 8’s InPrivate Filtering functionality relied on frequency heuristics to build a list as a consumer browses sites. By moving Tracking Protection to use curated lists, we improve the predictability of the consumer experience. Consumers are in position to choose whose lists (if any) they want and to exercise control over what information they share with which websites.

Looking Ahead

Tracking Protection and TPLs are a great way to start making progress as we work through the public discussion. They provide greater transparency about how the web operates and the opportunity to act on that information. Transparency and progress are important. This step forward may be too much for some even as it is not enough for others.

Today many view third-party cookies as the principal tracking mechanism. Consumers using IE today have tremendous control over cookies and can, if they choose to make a few clicks, “block all third party cookies,” “Block all cookies from example.com,” or with a little more work, “Discard all 3rd party cookies at the end of the browser session.” Of course, it is about more than cookies, and as an industry we will continue to have incomplete solutions until we agree on a clear definition of tracking, how it is and can be done, and what should be done in response. Do Not Track technologies, from cookie blockers to what’s described here, will continue to be incomplete until we have a clear definition of tracking. (At the same time they might overachieve at preventing non-tracking activities). "Do Not Track" itself is misnomer in that tracking is an inherent part of many experiences on the web (e.g. a shopping site showing me other items I’ve browsed to) and off (e.g. a credit card company calling you to confirm what it considers to be suspicious activity).

Also, many have recognized the progress being made in self-regulatory efforts and are hopeful to see more. For example, you can see this progress with sites like https://www.aboutads.info/ that involve giving “consumers a better understanding of and greater control over ads that are customized based on their online behavior.”

One potential downside is that some web site publishers and developers already have concerns with large numbers of visitors blocking some of the content today (usually ads). We understand this concern and have provided several ways to deal with this issue.

First, this functionality is opt-in, and by default consumers’ experience will remain the same as it is today, unless they make a decision to change it. Second, any site can make available a Tracking Protection List that creates exceptions (via “OK to Call” items) for external content that provides the full experience of the site. This TPL provides transparency to the consumer about the additional sites he will visit and share information with. Third, a site can pull external content into its own domain, so that a consumer has no need to call external sites. Lastly, networks of sites and associations can work together to create a TPL that they recommend broadly to consumers. We designed the feature so that there are ample opportunities for all the constituencies to engage in a manner consistent with their priorities and point of view.

We designed this functionality as a good start to enable consumer choice and protection from potential tracking. We provide a tool in the browser, and consumers choose how to use it. As with everything on the web, we expect it to evolve over time especially as the broader privacy dialog continues. We’re communicating about it now as part of our transparency in the software development process.

Thanks –
Dean Hachamovitch
Corporate Vice President, Internet Explorer

P.S. Here’s a preliminary file format for TPLs that shows both “Do Not Call” (block) and “OK to Call” (allow) items. We will make the format available under a Creative Commons Attribution license and the Microsoft Open Specification Promise.

 <?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:wf="https://www.microsoft.com/schemas/webfilter/2008">
<channel>
<title>Demo</title>
<description>Tracking Protection List from ietestdrive.com </description>
<item><wf:blockRegex><![CDATA[msdn\.com/.*\.js]]></wf:blockRegex></item>
<item><wf:allowRegex><![CDATA[strikestrike\.com/.*\.js]]></wf:allowRegex></item>
</channel>
</rss>

P.P.S. One aspect of the larger tracking discussion involves a change to “HTTP headers.” The key thing to note is that such a change is the start but only part of delivering tracking protection. It’s a signal to the web site of the consumer’s preferences. The rest of that solution (defining what that signal from the consumer means, what to do with it, verification, enforcement, etc.) is still under construction.

List of articles referenced
Creative Commons Licenses
Do Not Track - Universal Web Tracking Opt-Out
FTC Staff Issues Privacy Report Offers Framework for Consumers, Businesses, and Policymakers
Google Chrome Gets Better at Blocking Ads | Maximum PC
Internet Explorer 8: Features
Microsoft Open Specification Promise
100 Million Adblock Plus Downloads « Mozilla Add-ons Blog
Online privacy, Tracking, and IE8’s InPrivate Filtering - IEBlog - Site Home - MSDN Blogs
Privacy Beyond Blocking Cookies: Bringing Awareness to Third-Party Content - IEBlog - Site Home - MSDN Blogs
Privacy Principles | Microsoft Privacy
Protecting Consumer Privacy in an Era of Rapid Change: A Proposed Framework for Business and Policymakers (Preliminary FTC Staff Report)
Selectively Filtering Content in Web Browsers - IEBlog - Site Home - MSDN Blogs
The Self-Regulatory Program for Online Behavioral Advertising
Understanding Cookie Controls - EricLaw's IEInternals - Site Home - MSDN Blogs
Your Privacy Online - What They Know - WSJ.com

Comments

Anonymous
December 07, 2010
Sounds interesting so far. Question: why does this use RSS as format?
Anonymous
December 07, 2010
This is a terrific development for consumer choice. PrivacyChoice has already leveraged the functionality in IE8 to block cookies based on our Tracking Company Index. See it in action here: www.privacychoice.org/.../ie
Anonymous
December 07, 2010
This is a terrific development for consumer choice. PrivacyChoice has already leveraged the functionality in IE8 to block cookies based on our Tracking Company Index. See it in action here: www.privacychoice.org/.../ie
Anonymous
December 07, 2010
The problem with IE is IE itself, its simply not for the person looking for real privacy. www.privacy-resources.edu.tc
Anonymous
December 07, 2010
What is the "channel" tag for? and why is this an RSS document? e.g. why would this not be usable: http://pastebin.com/vRtyTZL6 And should the root tag really be rss?
Anonymous
December 07, 2010
Makes me think if it will effect largely used 3rd party analysis tools like Google Analytics...
Anonymous
December 07, 2010
Sounds like a good idea, keep em coming.
Anonymous
December 07, 2010
What's the difference between InPrivate Filtering and this?
Anonymous
December 07, 2010
Isn´t this the same as InPrivate Filtering on IE8? Regards, Paulo Oliveira.
Anonymous
December 07, 2010
IMO block should trump allow - it appears from the video that if you have conflicting settings on different lists, content that's allowed by any list will be allowed even if blocked by another list. But overall, this is a great idea and I'm glad it'll be implemented.
Anonymous
December 07, 2010
nice :) alonarad.blogia.co.il
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 07, 2010
If I understand things correctly, the scope of the article can be summarized in a sentence: to go beyond blocking just third-party cookies in the browser, you're providing a way for the browser to block third-party HTTP. As I was trying to understand this article, I mistakenly thought for a moment it was referring to real-time site scraping. There's technically nothing to prevent a website from taking first-party cookies and any other information it has available and performing third-party server-side HTTP requests with that information. HTTP proxying is another option: It's easy to imagine a backend framework that would allow ads to be served as first-party content and then allow the ads to proxy their HTTP communication through the first-party server to a third-party location. If you call it "partnering" rather than "spamming" or "advertising," then it flies under the radar. For example, isn't this how Facebook partners with other websites (i.e., through the backend)? Any time you browse to a website, you mustn't forget that you're ultimately putting your privacy in the hands of the backend code on the website.
Anonymous
December 07, 2010
here's a suggestion guys... get your ancient slob of a browser up to par with your peers before adding useless feature-list-check-mark nonsense like this
Anonymous
December 07, 2010
Amazing work guys. Only for this, I'm choosing IE platform. Keep more of this work coming !
Anonymous
December 07, 2010
@MVE/Paulo Oliveira: This feature is somewhat similar to InPrivate Filtering in IE8, with a number of differences. In particular, this feature allows you to subscribe to lists of sites to block, and doesn't disable itself every time you restart. @DaveN: "block" doesn't trump "allow" because it's unlikely that any list that ppl actually use will contain any "allow" rules. The "allow" rules will effectively just be exceptions saying: "hey, this one file on that domain is necessary (e.g. jquery.js) while the rest of the files (e.g. tracker.js, evil.js, malware.js, etc, etc) are all unwanted." It's basically a performance enhancement to enable writing broadly-scoped "block" rules.
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 07, 2010
Now you guys need to add a built in spell check and I won't need any other browser, ever.
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 07, 2010
@ Quincy Boolum Sites do not have to track other sites nor do you need to send them a full list of sites. Sites serve pages that have references to content in them from other domains which can include references that invoke tracking scripts. The browser normally follows those references to get the remaining content (including ad and tracking content). The browser can therefore decide based on a listto not get the tracking information from other domains.
Anonymous
December 07, 2010
In actual fact this feature is a built in IE9 adblocker? I agree with Quincy Boolum - you should only block the cookies NOT the actual requests. For a company that owns Atlas (huge adserving company) and MSN (huge ad portal) this seems like an insane move??
Anonymous
December 07, 2010
Guys, this is the copy of AdBlock add-in for Firefox. Thanks for bringing it to IE! But Adblock works even better because when an ad is removed, the blank space will be removed too, and text will nicely reflow. Please add this capability also to the "Tracking Protection" feature.
Anonymous
December 07, 2010
Here is the privacy bug with IE9 beta, related to facebook. Primary sites shows comments in iframe from facebook. I add primary site to block cookies, do not allow 3rd party cookies. And yet my name from facebook is still visible in that iframe. How and why is this possible?
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 07, 2010
On a slightly different note regarding adverts, will some of the new forms of pop-ups be blocked in IE9? Take for example the TV-listings website www.onthebox.com. Go onto it, then click any of the four dropdowns that filter the table and a pop-up window launches -- and I've had this happen in Firefox, Chrome, Safari and Opera (all on default pop-up settings and with no add-ons like AdBlock). Blocking certain sites in the IE Restricted Sites stops it working -- but I've seen numerous sites use this style nowadays and it's rather annoying. Can't it be blocked by updating the pop-up blocker to realise some of the newer coding methods used to launch pop-ups?
Anonymous
December 07, 2010
@RBJ It does seem odd that over the years versions of Office would add certain things to the browser (like the "Send to OneNote" icon, the "Research" pane or the "Edit in Microsoft Word" icon) but yet not the Spell Check feature. There are add-ons (like IeSpell) but, come on guys, why not allow Office to integrate it's Spell Checker into WIE? (Yes, a native IE one -- or even a Windows one for use in WIE, Notepad, WordPad, and any other app, would be better, but hey, I'd settle for if-you-install-Office-you-get-a-systemwide-spell-checker as a compromise).
Anonymous
December 07, 2010
Pffft. Late to the party as usual, guys, but acting like it's another "innovation" all the same. Firefox+AdBlock already does this (and more) but without the usual MS bloat and spin.
Anonymous
December 07, 2010
@Brian Adblockers already exist for IE as well. For instance IE+ Simple-Adblock does something like as well. The new thing about this feature is that it will be a native feature to the browser and not trough plugin use only. So no thrid party executable software required. You only have to get hold of a good TPL list or possibly subscribe to one. That will make this feature also usefull for enterprise adoption where you do not want a lot of browser plugin software to manage.
Anonymous
December 07, 2010
@RBJ & @Drake - I couldn't agree more! IE not having a spellchecker feature built it is one of the key things keeping this browser in the dark ages. It's not rocket science... just add it! It's embarrassing that IE doesn't include it by default - in fact it is the ONLY browser that doesn't have it... once again ranking IE at the bottom of all available browsers... even IE9.
Anonymous
December 07, 2010
The comment has been removed
Anonymous
December 08, 2010
Nice feature, although it seems it can't really be used for ad blocking if it doesn't remove the blank space. On a completely unrelated note, you should really put Word's spell checker in IE9. It is way more powerful than all other spell checkers.
Anonymous
December 08, 2010
Add Sandboxie to isolate web browser from my real the hard drive!!! Add Deep freeze like features to keep the pc's performance steady sate!!!!!! you can make your computer uncrushable!!! "unless one you hard drive fails!!" prove me wrong Microsoft!!!!!
Anonymous
December 08, 2010
you can put Raid1 !!!
Anonymous
December 08, 2010
The comment has been removed
Anonymous
December 08, 2010
The comment has been removed
Anonymous
December 08, 2010
Looks promising but does it block fly-in/overlay ads to? I mean these are the really annoying ads and they aren't really blocked by just blocking the HTTP traffic. The markup/css has to be changed too (otherwise you have an empty div flying in). And as some others already mentioned, it would be cool if removed ads would not leave empty space on the page. BTW: Will the IE pop up blocker use the TPL lists too? This would be great because having a TPL list and a seperate (manually maintaned) list for the popup blocker would be semi perfect.
Anonymous
December 08, 2010
The comment has been removed
Anonymous
December 08, 2010
Deep Freeze will not give you a message saying you can not do this or that!! it will let you download and install what ever you want!!! As soon as you restart it will go a way!!! Full access to 3d video card unlike virtual machine!! "it is a real PC deep freeze make it locked that is all!!" Get all file you want on PC before freezing it!! virtual machines are useless!!
Anonymous
December 08, 2010
Who know Microsoft software can be this solid in some peoples hand!!
Anonymous
December 08, 2010
@Drake @Norm Maybe they can hear us, HEY GUYS WE NEED A BUILT IN SPELL CHECKER IN HERE HELLO IE9 TEAM, WE NEED SPELL CHECKER SPELL CHECKER SPELL CHECKER SPELL CHECKER That should do it, yup.
Anonymous
December 08, 2010
I hate to repeat this here but once a post on the IE blog is not the latest post it gets ignored. Can someone from Microsoft please make a statement about shutting down the IE6/IE7/IE8/IE9 images at http://www.spoon.net/ ====================================================================================================== This was THE most useful resource for testing multiple versions of IE and the shutdown really ticked developers off! As a long time web developer of Enterprise Web Applications I've tried all the options out there to try and simplify testing IE and the lack of realistic options is a royal PITA. 1.) Multiple IEs - IE8 breaks the functionality of IE6's textboxes - thus its a NO-GO 2.) IETester - works great until you need to test popup interaction and then it fails - thus a NO-GO 3.) Virtual PC with timebombed images of IE6, IE7, IE8 - works ok, but the 12Gigs of HD space needed is frustrating when each full image of Windows dies 4 times a year, running a full Windows image is slow and you have to beg for updates because the releases are not co-ordinated and announced well at all - thus its a NO-GO 4.) IE Super Preview - Last I checked this did not allow full testing of IE user interaction, JavaScript DOM changes, popups etc. - thus its a NO-GO 5.) Multiple PC's to run multiple versions of windows and IE. With all the hardware, software, and physical space needed - its a NO-GO 6.) Spoon.net IEs - They work, they work just like local native apps once running, and there's no hacking of my real local IE install. - the ONLY problem with these IE's is that Microsoft shut them down Please understand that we (developers) just want something that works. Testing in multiple versions of IE is a pain to begin with and with IE9 on the horizon it is only getting worse. I'm not sure where the issue stands with Spoon, but I would really like a solution worked out fast. Steve
Anonymous
December 08, 2010
As long as the GUI isn't restoring the full customizability of IE8, nothing matters as I won't be installing IE9. IE9 is an unproductive UI with constant action required from the user for the notification bar. Things like clearing your history and cache show a notification which requires user action to go away. Microsoft needs to be taught the very fundamentals of GUI design which they used to get without any problem in the 90s.
Anonymous
December 08, 2010
Get Deep freeze!!! Lock the PC down!!! "try it out!!" it will never loose performance or crash it!!! have two windows!! one with it and one with out!!!
Anonymous
December 08, 2010
you must have two windows!! one on each hard drive split!!
Anonymous
December 08, 2010
I think that IE9 should have an upload progress bar (or sth like that). In Chrome, it's very convenient to see the progress. But in IE9 beta, I can only sit there and wait, wondering if the window does not respond or the upload is in progress.
Anonymous
December 08, 2010
The TPL lists sound nice, but what about sites that don't have them but you still want to view external content on? You should have a button that says "trust all scripts/plug-ins on this site" regardless of source URL, or maybe a pop-up that allows to checkmark URLs you trust. If I trust a site, I usually trust all content it uses. However, without this ability it is impossible to run with scripting disabled. I understand there is a security issue, but it's better than everyone never disabling scripting because it's utterly impossible to surf with.
Anonymous
December 08, 2010
The tracking protection indication is that per domain or a static indication which is the same for all websites the user visits? If the latter case that would probably we have to block IE9+ users. Did Microsoft FORGET that HTTP is STATELESS? Where the web is moving forward, Microsoft goes back in time where sessionids are part of the url which make them vulnerable for tempering. Maybe I missed something, but why does IE9 not follow the same-origin concept? Cookies from the website you visit are allowed, while external requests (not same-origin) are blocked unless permitted by the user. That would leave shoppings carts and many other web applications intact while still protecting the privacy of the user.
Anonymous
December 08, 2010
@Soon to be Google Having read what the Deep Freeze does on Wikipedia it basically images your OS so that any changes done past a committal point are reversed. This is basically the same as the now discontinued Windows SteadyState (formerly the Shared Computer Toolkit). While tools like this can be useful, I fail to see why we need one specifically for WIE. Personally, I prefer using Virtual Machines -- slower, yes, but making no changes at-all on the host file-system other than creating a single file to hold the guest file-system. That said, with the image-based backup in Windows 7 (and pro/ultimate editions of Vista) it's easy to create a whole snapshot of your system you can use to roll-back: not as quickly, granted, but it's simple and works well. System Restore also works using image-based snapshots in Vista and 7 though and really does reverse changes (even re-install removed software) reliably, compared to Me or XP's single-file backup approach. @DumbDown Hate to agree but on low-res screens having the tabs and address bar on one row really is a show-stopper for WIE9. Microsoft should remember that casual, less knowledgeable users are more likely to just click agree on an "allow us to collect sample data" dialogue than IT pros who actually read dialogues. And of course those users probably don't use many tabs. Of course there is a work-around: open multiple windows and have tabs in each -- which kinda defeats why tabs were originally introduced, no?
Anonymous
December 09, 2010
The comment has been removed
Anonymous
December 09, 2010
So this is like the RequestPolicy addon for Mozilla Firefox?
Anonymous
December 09, 2010
…or rather like NoScript's ABE?
Anonymous
December 09, 2010
The comment has been removed
Anonymous
December 09, 2010
@Soon to be Google We do get your points but please stop trolling on behalf of your company. We can appreciate what Deep Freeze does, it's far from the only software that does such a feature (excluding Microsoft's own and Windows OS features Wikipedia gives six, alone). Also, what's with your posting name, "Soon to be Google" -- are you suggesting your company Faronics is about to be bought-out by Google Inc.?
Anonymous
December 09, 2010
The comment has been removed
Anonymous
December 09, 2010
Continuing on the pattern of transparency, could you next look at the estimated delivery of full size smart address bar and more room to hold tabs directly visible/accessible.
Anonymous
December 09, 2010
I know this is off the topic but: lifehacker.com/.../browser-speed-tests-ie-9-firefox-4-beta-chromes-crankshaft-and-opera-11-beta What happened? IE9 did very badly...
Anonymous
December 09, 2010
How is this different for the average consumer at home to the "per site privacy" thats been available since ie6?
Anonymous
December 10, 2010
@SomethingDifferent If Lifehacker wants to be credible, they have to say how they tested browsers. They don't give the JS benchmark name (I have a feeling it's Dromaeo, Kraken or the V8 Benchmark Suite)...how can MS improve if they don't know where IE crashed? Besides, Chrome's memory use might be big, but it has a reason...you can't simply run tests, do a nice Excel graph, give results and say "the best browser is...". That's called trolling for comments.
Anonymous
December 10, 2010
What version of IE9 is in video this article. It seem little different that released Beta. Tabs looking somehow better or i am seeing things?
Anonymous
December 10, 2010
Please, please add spell check to IE9. With the number of enhancements that have been made to IE9, I just can't believe that MS still hasn't included this feature.
Anonymous
December 10, 2010
The comment has been removed
Anonymous
December 10, 2010
@IE8lover_IE9hater I too can't understand the massive lack of UI customisation. Even the simple "large icons" choice has been removed. The cleaner Status Bar is also less useful: it no-longer shows an icon if a pop-up has been blocked, nor InPrivate Filtering status, nor if cookies have been blocked nor what zone a website is in. They should look at how the Office team did the Status Bar in Office 2007 and 2010: right-click and you can select what you want to be displayed here and what not. So much better. Maybe after a final-version upgrade Microsoft will keep the WIE8 iexplore.exe executable so you can use that interface but the WIE9 rendering engine, like it did with WIE7, where the upgrade kept a copy of the MIE6 iexplore.exe in an update folder in the Windows directory.
Anonymous
December 11, 2010
No spell checker, no support from me.
Anonymous
December 11, 2010
The comment has been removed
Anonymous
December 12, 2010
It won't be a big disappointment if they can at least read our posts.
Anonymous
December 13, 2010
cd
Anonymous
December 13, 2010
@Laco There is an icon on favorites to stick it to the left and inbrowser, would not hurt to try...
Anonymous
December 14, 2010
Google fixes security risks in urchin tracker/google analytics. <q class="google"> While the immediate probability of this attack is low, we urge you to take action to protect your site. We have fixed the bug, and all new experiments are not susceptible. However, any experiments you are currently running need to be updated to fix the bug on your site. Additionally, if you have any Website Optimizer scripts from paused or stopped experiments created before December 3, 2010, you will need to remove or update that code as well. </q> My comment: more work has to be done, Google Web Apps next please. One needs to ask... why doesn't my Google Toolbar SideWiki or Side Talk bar not work in IE9 Beta... Press F12 to display the developer tool, then select the Script tab, press "Start Debugging".... mmm permission denied errors. Come on Mr Google, you have Chrome, don't make the mistake of only targeting its security model. Glad to hear back from Connect that you are considering my issue ticket about missing notifications on the Status bar. I see a related comment has already been posted here. connect.microsoft.com/.../ViewFeedback.aspx
Anonymous
December 14, 2010
The comment has been removed
Anonymous
December 14, 2010
The comment has been removed
Anonymous
December 14, 2010
The comment has been removed
Anonymous
April 29, 2015
Lpveyo. Bu

다음을 통해 공유