The flip side being that you can needlessly spend time fixing a bug in Chrome st... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

recuter on Nov 2, 2012 | parent | context | favorite | on: Chrome Canary for Developers

The flip side being that you can needlessly spend time fixing a bug in Chrome stable only to have it go away on its own in the next version.

So is it really practical to develop in canary? Possibly. Try it.

swampthing on Nov 2, 2012 | [–]

Once you've figured out it's a bug in Chrome stable, you can generally look to see if there's a bug report and track its status:

http://code.google.com/p/chromium/issues/list

masklinn on Nov 2, 2012 | [–]

Alternatively, you can needlessly spend time fixing a bug in Canary which doesn't exist in stable and will in fact go away before release.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact