Turn on shared workers by default (remove --enable-shared-workers, replace with

Turn on shared workers by default (remove --enable-shared-workers, replace with
--disable-shared-workers).

BUG=26223

[jam, 2009-11-13 23:31:58]

Has the security review completed?

[Andrew T Wilson (Slow), 2009-11-14 00:21:25]

My understanding is this is not necessary. From my previous email with mark
larson regarding notifications :


>>>

> Your next step is to get this enabled by default on the dev channel, making
> sure there's an easy way for us to disable it on the Beta branch if things
> blow up. (Typically the --enable-x flag gets converted to a --disable-x
> flag.)


> We also want to make sure of the following:


   -

   Security review. (*in progress is fine for Beta*; need to make sure
   issues are resolved for Stable)

   -

   Bug tracking: make sure your bugs and tasks to make the feature
   release-ready are tracked at http://crbug.com/. Use a label to identify
   your bugs (you can use any label you want; I can make it an official label
   at any time).

   -

   Test plan: contact Anantha Keesara and Jason Arbon to make sure they have
   a plan for QA to verify Notifications in release candidates and do other
   testing that's not covered by automated tests.

   -

   Final strings checked in (by next Friday the 13th).


<<<

So I don't think the lack of a security review should be a blocker for dev
channel.


On Fri, Nov 13, 2009 at 3:31 PM, <jam@chromium.org> wrote:

> Has the security review completed?
>
>
> http://codereview.chromium.org/395006
>

[jam, 2009-11-14 01:00:15]

lgtm

for anyone else watching, we're going to start requiring security reviews before
enabling on trunk _after this feature_