This will help with the labeling effort. I think the easiest way to do this would be to make nsIRunnable inherit from nsINamed. Then every nsIRunnable would be required to have a name.
I think this is superseded by your recent work in bug 1372405?
Bug 1372405 only covered stuff that inherits from mozilla::Runnable. We have some runnables that inherit directly from nsIRunnable. We could just fix those I guess so that they inherit from Runnable. But there are probably some legitimate use cases. This is a probably complete list: http://searchfox.org/mozilla-central/search?q=public%20nsIRunnable I guess JS runnables also fall into this category. Depending on how important they are, we could probably convince xpconnect to label them automatically.
I didn't mean to assign this to myself.
Assignee: wmccloskey → nobody
This would be desirable for moving more behavior into nsIRunnable/mozilla::Runnable.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.