Fired when an event occurs that impacts privacy, or when a user navigates away from a URL that has impacted privacy.
- bPrivacyImpacted [in]
A Boolean that indicates whether the current top-level URL has violated the browser's privacy settings.
This event does not return a value.
PrivacyImpactedStateChange was introduced in Microsoft Internet Explorer 6.
This event also fires when there is a user-initiated navigation away from a URL that has privacy violations. If the new URL has no record of privacy violations, the icon is no longer displayed, and the privacy state remains unimpacted. However, when navigating from a URL with privacy violations to revisit a URL that has a history of privacy violations (for example, the page is retrieved from the cache), this event fires two times: one time to signal that it is navigating away from the first violating URL, and a second time to signal that it is navigating to a URL which has impacted privacy.
User-initiated navigations include the following.
- Typing a URL in the address bar.
- Navigating using the Go To option from the View menu.
- Choosing a URL from the Favorites List.
- Clicking on a hyperlink that does not contain a script href.
- Peforming a manual top-level refresh.
- Performing a top-level navigating using the Back and Forward buttons.
Privacy is considered impacted when any of the following occur.
- A cookie is suppressed when sending an HTTP request.
- A cookie is blocked from being written.
- A cached file is retrieved that has a history of privacy violations.
Minimum supported client
Minimum supported server
|Windows 2000 Server|
|Internet Explorer 6|
Build date: 11/17/2013