Closed Bug 306217 Opened 14 years ago Closed 14 years ago
XBLService::On Stop Request() doesn't fire for custom protocol
I've constructed a new protocol handler and channel as JS-based components, and for the most part the pair seem to work fine. The protocol loads HTML pages, XUL documents, etc. But when it comes to loading a XBL binding onto a XUL element, things get dicey. For XBL bindings, my protocol receives calls to OnStartRequest() and OnDataAvailable(), but not for OnStopRequest(). Because of this, the bindings never apply, and the document essentially never finishes loading. I'm attaching a XULRunner testcase (.tar.gz) in a few moments.
Note this testcase will likely not work until bug 304048 is fixed.
14 years ago
your open() method returns a nonblocking input stream. don't do that. (but I don't know if that's the cause of your problem)
Attachment #194083 - Attachment mime type: application/octet-stream → application/x-gzip
What does this have to do with XBL? Is the channel's OnStopRequest being called? If not, it's a problem in the channel impl or necko, not in XBL...
I am dumb. Very dumb. Adding this line to my set originalURI call fixed the stoppage: bufOutStream.close(); Many thanks to biesi and bz for their patience in remote debugging.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.