Closed Bug 1359700 Opened 7 years ago Closed 2 years ago

Label nsIAsync(In|Out)putStream::AsyncWait() called from internal JS script

Categories

(Core :: DOM: Core & HTML, enhancement, P3)

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: bevis, Unassigned)

References

Details

nsIAsync(In|Out)putStream are xpcom components and can be invoked in JS with Services.tm.currentThread specified as the nsIEventTarget of the ns(In|Out)putStreamReadyEvent runnable in
http://searchfox.org/mozilla-central/search?q=asyncWait&case=true&regexp=false&path=

However, the EventTarget of DocGroup/TabGroup/SystemGroup are not available in JS level.
:billm, do we have any plan to have labeling API in JS level that will be used in comment 0?
Flags: needinfo?(wmccloskey)
No, we don't have anything like that. I think we could add a getter for the SystemGroup to the thread manager. If we need access to the DocGroup or TabGroup, we could maybe add a method to nsIDOMWindowUtils.
Flags: needinfo?(wmccloskey)
Priority: -- → P1
I'd like to lower the priority of this bug to P3 because the use of asyncWait are in dev/tool and the old add-on sdk and dom/presentation(which is only enabled in Android) according to search result in comment 0.
None of these will contribute the high frequency of nsInputStreamReadyEvent.
Priority: P1 → P3
Component: DOM → DOM: Core & HTML
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.