Web Platform Team Blog

Making the web awesome

New flag for CSS Regions in Chrome Canary

Update (7/15/13): The name of the Chrome runtime flag that needs to be enabled to access these features has been changed from “Enable experimental WebKit features” to “Enable experimental Web Platform features”.

This week the flags for a number of experimental features were rolled up under a single Chrome flag. The change has already made its way to Chrome Canary builds.

To enable CSS Regions in Canary, you now need to turn on the “Enable experimental Web Platform features” in chrome://flags.

Enabling Web Platform features

If you’re unfamiliar with Chrome flags, check out Christian’s excellent video and post.

As a bonus, when you turn on this flag, you also get CSS Variables, Shadow DOM, and more. Happy hacking!

One Comment

  1. September 18, 2012 at 7:25 pm, Jon said:

    Hmpf. This hardly seems a change for the better. Isn’t the point of these flags to let developers enable things and try them out before they are fully developed? How exactly are they supposed to do that when the description of the flag obfuscates what features are being turned on or off? What if they want to test one feature but not another? Hell, why not just have a single flag for everything, saying “Enable crazy experiments!” That way developers can feel the exhilaration of turning everything on or off without any clue what to expect whatsoever.

    Furthermore, it’s inconsistent, as there are still plenty of other flags that represent experimental Webkit features, like CSS Shaders, Web Audio Input, Media Source API, Pointer Lock, Speech API, and Fixed Position Stacking Contexts. If they’re lumping disparate features under a single flag, why not lump these along with them?

    What’s really needed is for the Chrome/Chromium developers to show some discipline and clean out some of the 75 flags, some of which have been hanging around for years. It shows an astonishingly lack of faith in their own engineering that they have about two-dozen flags to disable various parts of their accelerated rendering stack. Other flags appear to be UI experiments that should either be committed to, or dropped, not perpetually retained as flags. Others, like the FPS meter aren’t “experiments” at all, they’re just developer features, and should be made part of the developer tools.