Privacy Levels/P3P Help appears without p3p extension compiled in

VERIFIED INVALID

Status

Documentation
Help Viewer
--
minor
VERIFIED INVALID
16 years ago
15 years ago

People

(Reporter: Tim, Assigned: R.J. Keller)

Tracking

Details

(Reporter)

Description

16 years ago
Observed in Linux 20020601 Linux installer trunk nightly build (I hadn't thought
to look until now).

I should note that it's not clear to me if any (even minimal) P3P support will
exist in 1.0.  If it will, this bug is probably invalid.

Steps:
1. Visit Help->Help Contents (in the menu bar)
2. Choose Using Privacy Features->Using the Cookie Manager
3. See the link entitled "Setting Privacy Levels" (among others). Visit it.
shortcut: chrome://help/locale/using_priv_help.html#privacy_levels

Privacy levels shouldn't be mentioned in the help if it's not going to get built in.

Related bugs:
bug 126360 (P3P pref showing up without the back-end)
bug 128639 (RFE to enable P3P by default--for vote accumulation purposes :)
bug 62399 (deals with the actual process of implementing P3P)

bug 62399 comment 61 is unclear as to whether any P3P support will go into 1.0

harishd@netscape may want to know about this (based on bug 63096 comment 18)

Comment 1

16 years ago
-->cotter.
Assignee: rudman → cotter

Updated

16 years ago
Blocks: 92997

Updated

15 years ago
OS: Linux → All
Hardware: PC → All

Comment 2

15 years ago
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030202

Still wrong text in it, Netscape is mentioned often,
the process of setting Privacy levels is described,
but can´t be seen in Mozilla preferences as described,
must be from Netscape.

Comment 3

15 years ago
Reporter (Tim), is this bug still valid? I think p3p is now a standard extension
Assignee: cotter → rlk
QA Contact: rudman → stolenclover
(Assignee)

Comment 4

15 years ago
-->INVALID

This bug was once valid, but now that P3P is in by default, it is INVALID.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID

Updated

15 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.