Enable DirectWrite by default

Enable DirectWrite by default

Flips the sense of the flag for now. If all seems OK as we move through
channels, I will remove it later.

R=cpu@chromium.org, jam@chromium.org
BUG=25541
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=275860

[scottmg, 2014-06-06 22:28:22]

cpu:
chrome/app/generated_resources.grd
chrome/browser/about_flags.cc
content/common/sandbox_win.cc

jam:
content/browser/renderer_host/render_process_host_impl.cc
content/public/common/content_switches.*

[eae, 2014-06-06 22:30:12]

Yay!

[eae, 2014-06-06 22:31:12]

We might want to keep a --disable-direct-write flag for content_shell (and only
for content shell) to allow us to test the GDI code path on our win7 bots and
for debugging.

[scottmg, 2014-06-06 22:48:07]

Ah, do we need to land --disable-direct-write somewhere in Blink first to
avoid breaking layout_test bots then?


On Fri, Jun 6, 2014 at 3:31 PM, <eae@chromium.org> wrote:

> We might want to keep a --disable-direct-write flag for content_shell (and
> only
> for content shell) to allow us to test the GDI code path on our win7 bots
> and
> for debugging.
>
> https://codereview.chromium.org/323563005/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[cpu_(ooo_6.6-7.5), 2014-06-07 00:58:40]

lgtm

[eae, 2014-06-07 19:11:39]

On 2014/06/06 22:48:07, scottmg wrote:
> Ah, do we need to land --disable-direct-write somewhere in Blink first to
> avoid breaking layout_test bots then?

All blink tests have been running with directwrite for the last week and a half
now.
No need to wait.

[jam, 2014-06-09 15:38:54]

lgtm

[scottmg, 2014-06-09 15:53:58]

The CQ bit was checked by scottmg@chromium.org

[commit-bot: I haz the power, 2014-06-09 15:54:50]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/scottmg@chromium.org/323563005/1

[scottmg, 2014-06-09 21:47:42]

Committed patchset #1 manually as r275860 (presubmit successful).