To make my position clear, I support improving the error messages on Inspector. I'm just worried about exposing that to the Web because this area is already terribly under-spec'ed.
On Mon, Oct 1, 2012 at 5:48 PM, Ryosuke Niwa <[email protected]> wrote: > On Mon, Oct 1, 2012 at 5:18 PM, Ojan Vafai <[email protected]> wrote: > >> This isn't spec'ed anywhere. I agree it would be ideal to get a spec for >> this, but I don't think we need to block on that in this instance. > > > I would like to see us posting this on public-webapps or www-dom. I've > seen js code that tried to parse exception messages to get more information > about the failure. > > >> This is an area where browsers are completely incompatible already. I >> don't see much benefit from blocking on creating a specification to make >> this situation better for web developers. It's actually not that big of a >> deal if the error messages from different browsers are different. > > > If Web developers wanted to know the details of failures on their websites > as opposed to on Inspector, wouldn't it better to add some sort of API that > could interoperate on all browsers? > > - Ryosuke > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
