A way of explicitly reporting exceptions
andrea.giammarchi at gmail.com
Mon Jun 23 13:37:48 PDT 2014
just to clarify first sentence:
On Mon, Jun 23, 2014 at 1:35 PM, Andrea Giammarchi <
andrea.giammarchi at gmail.com> wrote:
> I personally don't think it's DOM responsibility to clean up after "your"
> errors and I'd expect DOM to keep firing if a listener set by some other
> library or scope I don't know/own fails, as it has always been.
I mean that you can always wrap your listeners inside a try/catch and deal
with the case the best way you want.
Needing to change "the entire surrounding world" because of uncaught errors
does not look the right thing to do in my opinion (delegating elsewhere
problems caused by flaky listeners)
Again, just my opinion.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss