4 ms·
Oh look, Google fails to fully support features only MSIE has P3P was standardized Then it's a little unfair to describe P3P as some IE-only standard then, no
by untog 15y ago
Oh look, Google fails to fully support features only MSIE has
P3P was standardized
Then it's a little unfair to describe P3P as some IE-only standard then, no? You make it sound like proprietary extension.
- eli 15y agoLets not get lost in semantics. True it's a documented standard, but only Microsoft supports it and given its many drawbacks no one else is likely to add support any time soon. It might as well be proprietary.
- untog 15y agoIt might as well be proprietary. Not even slightly. That does a huge disservice to any standardisation process. In fact, how "only Microsoft supports it" ends up being Microsoft's problem baffles me. It was created by a standards body. The other browser manufacturers did not implement it. Therefore, it's all Microsoft's fault?
- eli 15y agoIt is Microsoft's problem that they have IE default to rely on what nearly everyone agrees is a crap solution to protecting privacy on the Internet. To web developers and certainly to web users there is zero difference between a standard that only Microsoft supports and a documented, but non-standard extension that only Microsoft supports.
- untog 15y agoIt is Microsoft's problem that they have IE default to rely on what nearly everyone agrees is a crap solution Do they? Then what's the point in the standardisation process? The whole point is that everyone agreed on a solution in P3P. Maybe it wasn't ideal, but it was the standard. So, faithfully, MS implemented it. So, MS is to blame when they go alone and make their own standards, but they are now also to blame when they follow the standardisation process to the letter and other people don't?
- eli 15y agoYou don't get a free pass because you're following a W3C standard. The way P3P is implemented in IE made web developers lives harder in exchange for virtually no additional privacy protections to users. The point of the standards process is so that we don't have multiple competing/incompatible/ambiguous header-based privacy policies. But that's not the problem here. There aren't any notable competing privacy headers because the whole approach is flawed.
- yuliyp 15y agoThere was a standardization process, then the committee in charge of it gave up on it because it wasn't going anywhere except IE. See the home page of the working group (http://www.w3.org/P3P/ http://www.w3.org/P3P/). It's time IE woke up to that reality.
- freehunter 15y agoI made the point in another post that it was a "standard" and my post was immediately made invisible. Sometimes you can never win when people insist on ignoring the point for the strawmen.
- timothya 15y agoHe didn't say it's an "IE-only standard", he said it was an IE-only feature. It may be standardized, but that doesn't mean that it's implemented in other browsers.