Closed Bug 81249 Opened 24 years ago Closed 9 years ago

DOM crypto object needs to be callable from JS and C++

Categories

(Core Graveyard :: Security: UI, defect, P4)

Product:
Core Graveyard
Component:
Security: UI
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: javi, Unassigned)

Details

(Whiteboard: [kerh-cuz])

All other implementations of DOM interfaces in the client are done in such a way that it allows the DOM interfaces to be called from C++ or JavaScript. This is not true for PSM2's implementation of the crypto object. PSM2 should follow the conventions used by the other DOM interface implementers.
-> 2.1
Priority: -- → P2
Target Milestone: --- → 2.1
Version: 2.1 → 2.0
Keywords: nsenterprise
Priority: P2 → P4
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
removing nsenterprise keyword from PSM bugs with target milestone of future.
Keywords: nsenterprise
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer
QA Contact: ckritzer → junruh
Mass reassign Javi's old PSM bugs to nobody
Assignee: javi → nobody
QA Contact: junruh → nobody
Target Milestone: Future → ---
Product: PSM → Core
Whiteboard: [kerh-cuz]
QA Contact: nobody → ui
Version: psm2.0 → 1.0 Branch
Summary: PSM2 crypto object needs to conform → DOM crypto object needs to be callable from JS and C++
Version: 1.0 Branch → Trunk
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.