Closed
Bug 154308
Opened 23 years ago
Closed 9 years ago
webProg notification state flags don't filter out other STATE Start and Tfer callbacks
Categories
(Core Graveyard :: Embedding: APIs, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: depman1, Unassigned)
References
()
Details
Attachments
(1 file)
5.02 KB,
text/plain
|
Details |
Since some requests also set bits for other document types, i.e. REQUEST also
might activate DOCUMENT Start callback, at least some of these scenarios might
be OK. If they are, they should be documented, and this bug would then track the
doc changes. Otherwise, I'll check to see what bits are actually set for each
request type.
1. In your local source of the above url, set the notification flag to either
NOTIFY_STATE_REQUEST, NOTIFY_STATE_DOCUMENT, or NOTIFY_STATE_NETWORK.
2. Compile testEmbed from /mozilla/embedding/qa/testembed directory.
3. run testEmbed from /bin
4. From Interfaces menu, select nsIWebProgress > Add Progress Listener.
5. Enter a url.
6. Check TestOutput.txt logfile in C:/Temp
Result: STATE_START and STATE_TRANSFERRING notifications are appearing for other
flags. For example, if the flag = NOTIFY_STATE_DOCUMENT, notifications will
appear for STATE_START: REQUEST and NETWORK, and STATE_TRANSFERRING: REQUEST
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Comment 2•21 years ago
|
||
This bug needs to be reassigned.
Updated•15 years ago
|
Assignee: rpotts → nobody
QA Contact: dunn5557 → apis
Comment 3•9 years ago
|
||
Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•