Move computation of "prefer compositing to LCD text" into WidgetBase.

The "prefer compositing to LCD text" moves into the callback
notification where other screen properties adjust the settings.
This is ok because after the screen bounds are updating a Resize of
the Widget will occur.

BUG=1097816

Change-Id: I9b27af51386cb85ab8f0ecc87f60cf5ad5dd7226
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366669
Commit-Queue: Dave Tapuska <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Cr-Commit-Position: refs/heads/master@{#802346}
diff --git a/third_party/blink/common/features.cc b/third_party/blink/common/features.cc
index 63a16660..0382c76 100644
--- a/third_party/blink/common/features.cc
+++ b/third_party/blink/common/features.cc
@@ -754,5 +754,10 @@
 const char kBackForwardCacheABExperimentGroup[] =
     "experiment_group_for_http_header";
 
+// Whether we should composite a PLSA (paint layer scrollable area) even if it
+// means losing lcd text.
+const base::Feature kPreferCompositingToLCDText = {
+    "PreferCompositingToLCDText", base::FEATURE_DISABLED_BY_DEFAULT};
+
 }  // namespace features
 }  // namespace blink