This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I needed to define a task source for a simple thing in the Screen Orientation API specification (when the device orientation changes, a task is queued to change a value and fire an event) but no task source listed in the specification was making sense and defining a new one would be quite an overhead. I would not be surprised if vendors already use the "DOM Manipulation" task source as the default task source and I wonder if the specification should encourage that at some extent.
If there's no ordering correlation between when your event fires and anything else, then you should invent a new one. The only reason two events should use the same event source is if they are in some way required to fire in a predictabel order.
Please reopen this if you disagree or if I missed the point somehow. Thanks.