Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking at IE's privacy options screen and am trying to figure out how it breaks javascript, workarounds to that, and how I can gracefully degrade my user experience.

Is there a guide that directly describes the IE reaction to the P3P header?

How about corresponding Javascript samples for each known good/known bad example?

share|improve this question
up vote 1 down vote accepted

I would say that, to the client-side programmer, it doesn't matter how IE privacy settings break javascript -- If you're going to support graceful degradation, then the cause of the javascript failure doesn't matter to the programmer. All that matters is that whatever caused the javascript to "break" the code can handle it.

In that regard, it sounds to me like you are wanting a list of things to do when programming javascript graceful degradation. This kind of question would belong in, but has good information (including a "best practices" section at bottom).

If you specifically want to know how to do unobtrusive JS in regards to making sure your site is not dependent on cookies, then SO is still the place to ask that.

Also, P3P information does not affect the javascript (except for a few edge cases in MSIE (

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.