[whatwg] Proposal for a debugging information API

[David Barrett-Kahn]

Yes, thanks, these are just the sorts of systems which would be used to
collect this information were it available.  I believe that as it becomes
easier for less well resourced development teams to have crash reporting of
this kind its use will become more widespread, and that it will eventually
become part of the standard toolkit.

-Dave


On Wed, Nov 14, 2012 at 9:12 PM, Gordon P. Hemsley <gphemsley at gmail.com>wrote:

> Recent blog posts that coincidentally may be useful in this discussion:
>
> http://vocamus.net/dave/?p=1532
> http://www.twobraids.com/2012/11/socorro-as-service.html
>
>
> On Thu, Nov 15, 2012 at 12:07 AM, David Barrett-Kahn <dbk at 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
> me at gphemsley.org
> http://gphemsley.org/ • http://gphemsley.org/blog/
>



-- 
-Dave