All that being said, I would like to drop p3p from the list of default
extensions, and leave it intact as a compile-time option, and perhaps
later as an XPI drop-in. While embeddors may want to continue to
include it, as a default option it doesn't really seem to make sense
to continue maintaining it. There isn't any need to cvs remove it,
though. As a test, we could drop this for 1.8a to get a better
overall response to how many users really need/want this and would
actually notice if it was gone (and how many would really be affected
seriously by this is yet another debate).
In terms of how this would affect users, Firefox no longer builds it,
and hasn't exposed UI for it in well over a year, with barely a peep
from the userbase. Near as I can tell, Opera doesn't support P3P
The current list of p3p bugs that don't have any ownership:
Thoughts/discussion/angry flames welcome, come one, come all!
It doesn't seem to be a terrible buglist (about half aren't what I'd
even consider "bugs") but I'm generally in agreement that the
combination of the lack of ownership and the lack of community interest
(which determines if the component is getting tested, even on an ad-hoc
basis) make for a compelling case for disabling the feature.
I'd certainly support anything that moves us towards a simpler, more
intuitive cookie interface. I'm also supportive of moving un-owned and
under-tested features out of the default configuration where that's
easily done. With features that are already segregated by build-time
flags, it certainly makes it a lot easier :-)
> All that being said, I would like to drop p3p from the list of default
> extensions, and leave it intact as a compile-time option, and perhaps
> later as an XPI drop-in.
Yep. Makes total sense imho.
I think the question of privacy is very important
but it looks like p3p is a bust.
IMHO, either decide to drop it (and cvs remove it) or keep it visible.
Hiding it will just bitrot the code even more and is just asking for
more grief later.
there's no need to CVS remove this yet. If it does actually bitrot,
we'll deal with it at that time.
^^ me, oops
It may also be the case that others who are doing Mozilla-based products
or distributions are interested in building with this (if it hasn't
rotted completely) so I'd say let's not remove it unless/until it does