Turning on clip anti-aliasing by default in Chrome.

third_party/WebKit/Source/core/frame/Settings.in

Index: third_party/WebKit/Source/core/frame/Settings.in
diff --git a/third_party/WebKit/Source/core/frame/Settings.in b/third_party/WebKit/Source/core/frame/Settings.in
index 29e768238341c3a73fafad0309244c50add99a60..4c292758da4edfca7fdd69ded7169c845ec3e34c 100644
--- a/third_party/WebKit/Source/core/frame/Settings.in
+++ b/third_party/WebKit/Source/core/frame/Settings.in
@@ -87,7 +87,7 @@ webGLEnabled initial=false
 
 webGLErrorsToConsoleEnabled initial=true
 antialiased2dCanvasEnabled initial=true
-antialiasedClips2dCanvasEnabled initial=false
+antialiasedClips2dCanvasDisabled initial=false

[Justin Novosad, 2016/09/21 21:27:02]

This is not correct. We do not do inverted logic for flags.  Keep 'Enabled' like
before, just change the default to true.

[xlai (Olivia), 2016/09/22 14:11:34]

I assume you want to enforce antialiasedClips to be enabled by default.
According to the previous comment, we want to keep the
antialiazedClips2dCanvasEnabled flag name unchanged. Then if we set this flag to
be true, what happened if users append this flag in command line? There would be
no effect (you're turning on something that is already on by default).

I checked chrome://flags and couldn't find this flag available to be modified in
GUI. It seems that it can only be passed on in command line. 

 accelerated2dCanvasMSAASampleCount type=int, initial=0
 
 hyperlinkAuditingEnabled initial=false