On Fri, 26 Jul 2013, James Greene wrote:
>
> My last name ends with an 'e' ('Greene' vs. 'Green'). Please correct
> that when you get a chance. Thanks!
Oops, my apologies. Fixed.
> You had mentioned earlier that there is already a window 'error' event
> that can be listened to via `window.add
Ian —
So Paul Irish pointed out to me that the spec has just been updated to
include this:
http://html5.org/tools/web-apps-tracker?from=8085&to=8086
Yay, that's awesome! :)
*Two things:*
*
*
*#1.*
My last name ends with an 'e' ('Greene' vs. 'Green'). Please correct that
when you get a cha
Rick —
Thanks for clarifying/correcting both my comment and Hixie's!
Sincerely,
James Greene
On Wed, Jul 24, 2013 at 4:24 PM, Rick Waldron wrote:
> On Wed, Jul 24, 2013 at 2:50 PM, Ian Hickson wrote:
>
> > On Fri, 12 Jul 2013, James Greene wrote:
> > > On Fri, Jul 12, 2013 at 12:17 PM, Ia
On Wed, Jul 24, 2013 at 2:50 PM, Ian Hickson wrote:
> On Fri, 12 Jul 2013, James Greene wrote:
> > On Fri, Jul 12, 2013 at 12:17 PM, Ian Hickson wrote:
> > > On Tue, 5 Feb 2013, Nathan Broadbent wrote:
> > > >
> > > > The current information passed to window.onerror rarely provides
> > > > suffi
On Fri, 12 Jul 2013, James Greene wrote:
> On Fri, Jul 12, 2013 at 12:17 PM, Ian Hickson wrote:
> > On Tue, 5 Feb 2013, Nathan Broadbent wrote:
> > >
> > > The current information passed to window.onerror rarely provides
> > > sufficient information to find the cause of the error. The column
> >
On Fri, Jul 12, 2013 at 5:51 PM, Garrett Smith wrote:
> On 7/12/13, James Greene wrote:
> > Ian —
>
> Hi James -
>
> I've interleaved, combined with your top post below.
>
> > I'm curious: would do you say that? All evergreen browsers already
> include
> > a `stack` property on their core `Error
On 7/12/13, James Greene wrote:
> Ian —
Hi James -
I've interleaved, combined with your top post below.
> I'm curious: would do you say that? All evergreen browsers already include
> a `stack` property on their core `Error` prototypes, so it seems to me that
> the only thing preventing us from
Ian —
I'm curious: would do you say that? All evergreen browsers already include
a `stack` property on their core `Error` prototypes, so it seems to me that
the only thing preventing us from getting that useful information for
unhandled errors is the fact that `window.onerror` does not provide us
On Tue, 5 Feb 2013, Nathan Broadbent wrote:
>
> The current information passed to window.onerror rarely provides
> sufficient information to find the cause of the error. The column number
> argument will be a big step forward, but a stack trace would be
> especially useful. I would like to add
