nsIWebProgressListener needs a security state change method.

VERIFIED FIXED in M18

Status

()

Core
Embedding: APIs
P1
normal
VERIFIED FIXED
18 years ago
16 years ago

People

(Reporter: Judson Valeski, Assigned: dougt)

Tracking

({embed})

Trunk
x86
Windows 98
embed
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3+])

(Reporter)

Description

18 years ago
sIWebProgressListener::OnSecurityStateChange

We'll have a enum for the different security states: 
          secure 
          not secure 
          broken 
One notification happens at transition time. This one is cancellable - 
the notification method returns a PRBool. 
Another happens when we're done loading (this is really for the broken case).
This is not cancellable.
(Reporter)

Updated

18 years ago
Keywords: embed

Updated

18 years ago
Keywords: nsbeta3
(Reporter)

Updated

18 years ago
Whiteboard: [nsbeta3+]
(Reporter)

Updated

18 years ago
Target Milestone: --- → M18

Updated

18 years ago
Blocks: 48444
(Reporter)

Updated

18 years ago
Priority: P3 → P1
(Assignee)

Comment 1

17 years ago
checked in.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

17 years ago
checked in.  


Notes:
+ New interface is checked into
netwerk/base/public/nsISecurityEventSink.idl

+ security level flags add to the nsIWebProgressListener are not honor
yet.  RFE.

+ Deverged from inital conversation about this interface.  There will
not be any way to prevent a page transition via this interface.  I
deverged for a few reasons.  1. Current implementation does not allow
users to stop a page transition. (bad to warp an interface to fit
design... i know)  2. we post events into an event sink.  I did not want
to enforce a sync call into that event sink.  3.  Makes the interface
more complex.  This only effects page transitions (eg https -> http). 
You still will get notified, but unable to stop the progress. 
Cancelation can still be caused in the onStatusChange method.

Resolution: FIXED → ---

Comment 3

17 years ago
verified fixed.
Status: RESOLVED → VERIFIED

Comment 4

17 years ago
grumble.
Status: VERIFIED → REOPENED

Comment 5

17 years ago
fixed.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → FIXED

Comment 6

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