W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2012

Re: [whatwg] Proposal for a debugging information API

From: Gordon P. Hemsley <gphemsley@gmail.com>
Date: Thu, 15 Nov 2012 00:12:56 -0500
Message-ID: <CAH4e3M4BwhxmfFebLhKo_78q=d5e_i+dAGZ7VgxPBDxCvdEXDQ@mail.gmail.com>
To: David Barrett-Kahn <dbk@google.com>
Cc: whatwg@lists.whatwg.org
Recent blog posts that coincidentally may be useful in this discussion:


On Thu, Nov 15, 2012 at 12:07 AM, David Barrett-Kahn <dbk@google.com> wrote:

> Hi whatwg.  I have a proposal for a new web standard, and would value your
> feedback.  This is based on my experiences working on Google Docs, which
> has a well developed ability to send crash reports back to the server for
> analysis.  We often find these crash reports to be lacking in crucial
> information though, because that information is not available on the JS
> APIs.
> My proposal is to have a class of information which can be made available
> to an app only after the display of a generic 'this application has
> crashed' dialog, which could be drilled into to show what is being
> disclosed, and which of course can be denied.
> Good examples of the information in question are the system's precise
> hardware and network configuration, what Chrome extensions it has
> installed, and perhaps a screenshot of the failed application.
> I've fleshed this out in the following document, and would value opinions
> on the value of a feature of this kind, and the merits of this particular
> approach.
> https://docs.google.com/document/pub?id=1pw2Bzvy6OEn8YY3fAcZiReJPmgB79swkx-NJAdcemPk
> Thanks!
> -Dave

Gordon P. Hemsley
Received on Thursday, 15 November 2012 05:13:43 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:17 UTC