If you'd like to help Chrome development you can file bugs for these at the Chromium bug tracker (use this for bugs you find in Stable/Beta channel too!) In Canary and Dev, you're more likely to run into unintentional bugs that creep in during development. You can find upcoming changes to Web APIs at ChromeStatus In general, changes that occur in Canary, Dev, and especially Beta, are intended to make it to Stable channel so it's a good idea to test your apps against Beta to make sure your app will continue to function as expected once the Beta is promoted to Stable. A Chromium build is basically equivalent to Chrome but doesn't include proprietary bits (Flash plugin, codecs, etc) or official Google branding (icons, etc).Ĭompatibility in terms of web-facing APIs between the different versions should be essentially the same except, of course, for intended upcoming changes. The order from "freshness" to "stable": Canary -> Dev -> Beta -> StableĬhromium is the name of the open-source project from which Chrome is built. Beta channel is a long running branch that's the upcoming release and is generally quite stable/bug free. (Aside from building ToT yourself)Īside from Canary, there's also the Dev channel which is a slightly longer development release, usually about weekly, but still built from the bleeding edge tip-of-tree. It's the bleeding edge of development and so you should expect crashes and bugs but it's the quickest way to test recent changes to chrome. Canary is basically a (near) nightly release built from the current tip of tree of the Chrome repo.
0 kommentar(er)
