Although it is supposedly bleeding edge, with no user testing (Chrome Canary users are supposed to be the testers ;-) ) prior to the launch of a new version, I have been using it without any problems at all. Until I was trying to view a webpage that demonstrates HTML5 features at http://html5-demos.appspot.com/static/html5-whats-new/template/index.html#1
Chrome Canary crashes, whilst my stable version of Chrome (version 12 at the time of testing) worked perfectly fine. Sounds like a defect to me.
Reporting the Defect
How do you report an issue in Chrome? Very simple, just click on Google Chrome controls (spanner) icon, Tools -> Report an issue...
You will be redirected to this internal page chrome://bugreport/#6
Some of the details are already pre-filled on your behalf: the URL where the defect occurs, and a screenshot of the page. Select the type of defect, type in the description, and click Send feedback.
Alternatively, you can submit the bug report online at http://code.google.com/p/chromium/issues/entry
Contrast this with Microsoft's Internet Explorer. There is no obvious option within Internet Explorer itself. You need to
- Go to http://connect.microsoft.com/ie/
- Register for Microsoft Connect
- Sign up for IE Public Feedback program
- Then submit your bug report
To be fair, there is behaviour tracking in IE itself, which will submit information directly to Microsoft when IE crashes. Still not very re-assuring when you do not know if the issue is being worked upon or not.
Getting A Response
Once the bug is accepted by the Issue Tracking system, I can access it via its unique URL http://code.google.com/p/chromium/issues/detail?id=89316
I reported it on the 15th July 2011. On 18th July, the bug is picked up by a developer. 19th July falls on a Saturday, mind you!
On 20th of July, the developer updated me (via an automated email in the Issue Tracking system) that the bug is fixed in the latest release. Since Chrome automatically push out updates, I did not even realize the bug is fixed. Did a quick test, and confirm Chrome Canary no longer crashes.
All within 6 days. It took less than a week to resolve a bug in Chrome. See the timeline below
I reported it on the 15th July 2011. On 18th July, the bug is picked up by a developer. 19th July falls on a Saturday, mind you!
On 20th of July, the developer updated me (via an automated email in the Issue Tracking system) that the bug is fixed in the latest release. Since Chrome automatically push out updates, I did not even realize the bug is fixed. Did a quick test, and confirm Chrome Canary no longer crashes.
All within 6 days. It took less than a week to resolve a bug in Chrome. See the timeline below
Yet another reason Chrome is simple awesome!
0 comments:
Post a Comment