navigator.securityPolicy not implemented.
Assignee: dougt → javi
Moving to M17; javi may want to update this with a revised estimate after he finishes pending DoD work.
Target Milestone: --- → M17
per phil --> nsbeta2
[nsbeta2+ until 5/16]
Whiteboard: [nsbeta2+ until 5/16]
*** This bug has been marked as a duplicate of 17684 ***
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Reopening to keep on radar.
Status: VERIFIED → REOPENED
OS: Windows NT → All
Hardware: PC → All
Resolution: DUPLICATE → ---
Cleaning up status whiteboard on this "reopen" marking beta2 minus (5/16 is long gone).
Whiteboard: [nsbeta2+ until 5/16] → [nsbeta2-]
Adding nsbeta2 keyword to bugs with nsbeta2 triage value in status field so the queries don't get screwed up
*** Bug 17684 has been marked as a duplicate of this bug. ***
marking nsbeta3-. This is a feature.
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
new target milestone
Target Milestone: M18 → mozilla0.9.1
Mass changing of product. Browser:Security:Crypto --> PSM 2.0
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: mozilla0.9.1 → ---
Version: other → 2.0
Keywords: nsbeta2, nsbeta3 → arch, helpwanted, mozilla1.0
Mass reassigning target to 2.1
Target Milestone: 2.0 → 2.1
Priority: P3 → P4
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
what is needed here? to update some stuff from DOM or in PSM?
Mass reassign Javi's old PSM bugs to nobody
Assignee: javi → nobody
Status: REOPENED → NEW
QA Contact: bmartin → nobody
Target Milestone: Future → ---
I think this bug should now be wontfix? We no longer ship different versions of the product, with different crypto strength for different regions, so having this information seems to be useless? Please reopen if I'm wrong.
Status: NEW → RESOLVED
Last Resolved: 19 years ago → 13 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.