1335601 - (nsInputStreamReady) [meta] Label nsInputStreamReady event

Status: RESOLVED WONTFIX

(Core :: XPCOM, defect, P3)

Description

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

We'll have to figure out what is triggering the event and how to get to a document from there.
http://searchfox.org/mozilla-central/rev/4e0c5c460318fb9ef7d92b129ac095ce04bc4795/xpcom/io/nsStreamUtils.cpp#32

The event includes a target, so we can just construct it with EventTargetFor to handle the dispatching.

I'm not sure what sort of work actually happens when this triggers. We can call into chrome JS via XPCOM.

Comment 1

[Bevis Tseng[:bevis][:btseng](Exited)]

The frequency of this event looks pretty high according to bug 1333984 comment 10.
I'd like to take this bug to follow up.

Comment 2

[Bevis Tseng[:bevis][:btseng](Exited)]

Sorry, no bandwidth for this until bug 1350177 and bug 1345464 are clear. :|

Comment 3

[Bevis Tseng[:bevis][:btseng](Exited)]

(In reply to Bill McCloskey (:billm) from comment #0)
> We'll have to figure out what is triggering the event and how to get to a
> document from there.
> http://searchfox.org/mozilla-central/rev/
> 4e0c5c460318fb9ef7d92b129ac095ce04bc4795/xpcom/io/nsStreamUtils.cpp#32
> 
> The event includes a target, so we can just construct it with EventTargetFor
> to handle the dispatching.
> 
> I'm not sure what sort of work actually happens when this triggers. We can
> call into chrome JS via XPCOM.

ns(In|Out)putStreamReadyEvent are expected by the call sites(imageLib, netwerk, call sites of nsPipe) of 
NS_New(In|Out)putStreamReadyEvent:
http://searchfox.org/mozilla-central/search?q=NS_New(In%7COut)putStreamReadyEvent&case=false&regexp=true&path=

We should file follow-up bugs in these sub-modules for tracking.