Feature flags are not accessible in JavaScript.

[Aaron Bentley]

We sometimes wish to enable and disable javascript-based features, so there should be a uniform way of accessing feature flags in JavaScript.

[Robert Collins (lifeless)]

Thanks for doing this, I'm very glad to see you took a whitelist
approach where only select flags are exposed. Nice (and necessary -
some flag values may be confidential).

speculation: I wonder if we should also expose a list of *requestable*
flags, to let browsers opt in (e.g. via cookies) similar to google
labs.

[Martin Pool (mbp)]

On 18 November 2011 08:30, Robert Collins <email address hidden> wrote:
> Thanks for doing this, I'm very glad to see you took a whitelist
> approach where only select flags are exposed. Nice (and necessary -
> some flag values may be confidential).
>
> speculation: I wonder if we should also expose a list of *requestable*
> flags, to let browsers opt in (e.g. via cookies) similar to google
> labs.

I think that would be great, especially in conjunction with the new
"you're in a beta" banner.

This can be done somewhat adequately at the moment by making an open
team per feature.

It would be nice if even the availability of a lab was itself
dynamically controllable.

--
Martin

[Aaron Bentley (abentley)]

We were thinking of allowing people to opt out of features, forcing the default value to be used. That wouldn't require additional functionality. Not sure whether we'll be able to get to that.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r14333 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/14333>.