MSDN Blog Postings as a superintend » Blog Archive as a superintend belittling » The Privacy Impact of Add-ons: New APIs repayment for IE8

By come to distress, when starting a fresh sitting using IE8’s InPrivate Browsing adduce, toolbars and Browser Helper Objects are harmed. This is done to succour drive comprised in one’s wing the user’s isolation: mixed toolbars and extensions stature their own navigation/search/etc adventures lists, and such lists could disobey the user’s belief of isolation while InPrivate Browsing is enabled. In imbalance, ActiveX controls persist enabled while browsing InPrivate because mixed sites rely on such controls, and they are to some less indubitably to follow users’ stature in a procedure that impacts isolation. The IEIsInPrivateBrowsing() solemnization returns a boolean value indicating whether the common browser event is contest InPrivate.
To allow all browser extensions (ActiveX, BHOs, and toolbars) to be more privacy-conscious, IE8 includes a fresh API to concession to add-ons to come on when they are contest advantageous a exclusive browsing sitting. Your spread remote needs to halting this API moment per sitting, because entering and exiting InPrivate Browsing results in the creation/teardown of the browser event (and consequently your add-on).

When IEIsInPrivateBrowsing() returns TRUE, your spread should do the following things:
Do not concession to script/network access to any unwavering stature poop generated from a late sitting (e.g. Stated another procedure, you distress not bite that the redress value of this API inclination interchange during the lifetime of the deal with. start with an cheap cookie receptacle, DOMStorage, etc). cookies, DOMStorage, or equivalents) to session-based stature that is cleared on door.

Downgrade any attempts to change unwavering stature (e.g.
Avoid making any changes to statistics stores (e.g.
By supporting the IEIsInPrivateBrowsing API, you can delegate persuaded that your add-on is brooding of the user’s isolation choices. disk caches, registry, etc) unless those changes are reverted on door. Even if you’re implementing a BHO or toolbar, you should payment supporting this API because end-users may handle the sceptre to allow toolbars and BHOs while InPrivate via unchecking the Disable toolbars and spread when InPrivate Browsing starts choice on the Privacy flap of the Internet Options dialog.
In spread to the IEIsInPrivateBrowsing API, we’ve added a fresh API that allows extensions to be notified when users eradicate their browsing adventures.

Comments are closed.