Quantum/DOM: Difference between revisions

m
Line 278: Line 278:
* Handled the received messages in '''IPC actor childs'''. (A received message will be handled on main thread with a new runnable if its actor child is created on the main thread.)
* Handled the received messages in '''IPC actor childs'''. (A received message will be handled on main thread with a new runnable if its actor child is created on the main thread.)
* Subclass of '''nsExpirationTracker''' (The overriden method of NotifyExpired() will be triggered implicitly with a new runnable by the internal timer in nsExpirationTracker implementation. See the dependency tree of [https://bugzilla.mozilla.org/show_bug.cgi?id=1345464 bug 1345464] for the list of the sub-classes.)
* Subclass of '''nsExpirationTracker''' (The overriden method of NotifyExpired() will be triggered implicitly with a new runnable by the internal timer in nsExpirationTracker implementation. See the dependency tree of [https://bugzilla.mozilla.org/show_bug.cgi?id=1345464 bug 1345464] for the list of the sub-classes.)
* The use of '''NS_New(In|Out)putStreamReadyEvent''' or the use of '''AsyncWait()''' on the '''(In|Out)putStream''' acquired from '''new Pipe()''' in js or '''NS_NewPipe()''' in native implementaiton. (These 2 use cases trigger new runnables named '''(In|Out)putStreamReadyEvent''' to the specified nsIEventTarget which needs to be labeled if the nsIEventTarget points to the main thread.)
* The use of '''AsyncWait()''' on any '''nsIAsync(In|Out)putStream''' . (These use cases trigger new runnables named '''(In|Out)putStreamReadyEvent''' to the specified nsIEventTarget in the invocation of AsyncWait(). These runnables need to be labeled if the nsIEventTarget points to the main thread.)
* The use of '''NS_ProxyRelease''' on main thread or '''NS_ReleaseOnMainThread'''.
* The use of '''NS_ProxyRelease''' on main thread or '''NS_ReleaseOnMainThread'''.


Confirmed users
205

edits