[IndexedDB] Redesign propagation path (#66)

Apparently for some reason this specification uses UI Events to override the DOM Standard on some details of event dispatch. That seems extremely weird and wrong.

Having said that, DOM Standard doesn't have a hook yet for defining the propagation path (or event path as I suspect we'll end up calling it).

Would it work to have a hook where the event target defines the path? So that you invoke dispatch, dispatch asks the event target for the event path, and the event target returns a list of one or more objects implementing `EventTarget`. Or do you really need the thing you have now, where when you dispatch the event, you also provide the event path each time? (The latter kind of setup would not work at all well for DOM. That is, it would be very verbose.)

Paging @smaug---- since he might care about this.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/66