Great question. As of now, this isn't in any of the channels. It's a bit complicated but I'm going to try my best to explain it. Tip: think of trees, makes it easier.
The Chromium Project uses a handful of "trunks" for each major aspect. Blink has its own trunk, but Chrome browser, Chrome OS, Chrome for Android, and Chrome for iOS all share a single trunk of the tree. Any changes made to any of those projects are added to the trunk first.
According to a schedule set by the developers, every so often a copy of the trunk is made and is given a branch number. It is then assigned a milestone number (30, 31, 32). From there, it is promoted to the dev channel. From then on, changes made to the project are committed to the trunk and not that branch
, unless a change is specifically merged into that branch
. This is how things are kept stable without slowing down the ongoing project development. Each branch is allowed to grow slowly, while the majority of development stays on the trunk (and the trunk grows past where the branch happens to be).
So in other words, this will become available in the other channels when one of the following happens:
- It is specifically merged into them.
- One of the channels ships a build that is cut off after this change was committed.
Chromium OS doesn't have a channel system, so all changes are constantly
available as of the last time you "built" it. If you build Chromium OS now, it will contain this change. If you had built it 3 hours ago, it would not have.
Just to be safe, here's a visual representation:http://ftagada.files.wordpress.com/2011/01/chrome-releases23.png
In English: It's only available for Chromium at the moment, but will be available elsewhere "soon" (I really can't be more specific with that time frame, sorry).