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

Re: [whatwg] Meta "bugreport" proposal

From: Kang-Hao (Kenny) Lu <kanghaol@oupeng.com>
Date: Thu, 01 Nov 2012 14:30:56 +0800
Message-ID: <50921720.7090107@oupeng.com>
To: Nicolas Froidure <froidure_nicolas@yahoo.fr>
Cc: WHAT Working Group <whatwg@whatwg.org>
Overall, I think this is interesting and something some browser
developers would really like to see, as they often want to report site
compatibility issues. Therefore, I think you might want to write down a
proposal that's more detailed and create an entry in the registry[1] so
that people know such an idea exists. I don't think it's particularly
important to get an "Accepted" status and popularizing the idea is
probably more important.

Also, you might want to share your idea on public-vocab@w3.org[2] as
there are more people on that list who are in general more interested in
features like this.

(12/10/31 17:21), Nicolas Froidure wrote:
> The uri could be :
> - mailto: to send a report by mail (ex: mailto:webmaster@example.org)
> - http: to send the bug report a a simple HTTP POST request (ex:
> http://example.org/bugreport).
> - bug: something more customizable to allow webmasters to fit bug
> reports with their systems (ex:
> bug:http?uri=/bug.dat&method=POST&captcha=/captcha.jpg )

I am not sure a new scheme is a good idea. For embedding data in a URL,
you might consider something like

  data:text/plain,http?uri=/bug.dat&method=POST&captcha=/captcha.jpg

but I am not an expert on this to say whether this is a good idea.

> - etc (ws:, irc: ...)
> 
> In order to test this i just made a Chrome extension illustrating how
> browsers could handle this meta markup :
> https://chrome.google.com/webstore/detail/bugmeback/hgmagcomobmjhaomdoihiggpdekaehmg
> 
> The code is there : https://github.com/nfroidure/BugMeBack

Thanks for moving this forward with a concrete implementation instead of
an abstract idea!

I am not familiar Chrome extension API and what
chrome.extension.sendRequest does, but if it does send an email when
@href is a mailto: URL, you might want to either:

1. Discuss with whoever creates the entry for rel=webmaster in [1] to
see if either rel=webmaster can be dropped or rel=bugreport can be
merged into it.
2. Extract mailto: URL from rel=webmaster too and treat it as if it is
rel=bugreport.

> Are you interested in that kind of approach for bug reporting ?

I think a lot of people do dream of an automatic Web but unfortunately
it's never easy to make one.


[1] http://wiki.whatwg.org/wiki/RelExtensions
[2] http://lists.w3.org/Archives/Public/public-vocabs/


Cheers,
Kenny
-- 
Web Specialist, Oupeng Browser, Beijing
Try Oupeng: http://www.oupeng.com/
Received on Thursday, 1 November 2012 06:31:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT