Remove will-change: contents GPU rasterization hint

Remove will-change: contents GPU rasterization hint

We've decided not to ship this configuration. The implementation also doesn't
work because it incorrectly changes the paint order of elements with
will-change: contents by make them into a NormalLayer.

R=esprehn@chromium.org
BUG=370604
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=173557

[ajuma, 2014-05-07 20:08:24]

https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h
File public/web/WebSettings.h (right):

https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h#new...
public/web/WebSettings.h:69: virtual void
setAcceleratedCompositingForGpuRasterizationHintEnabled(bool) { };
The chromium-side caller has already been removed (in r268321), so this should
be removable too.

[abarth-chromium, 2014-05-07 20:28:00]

On 2014/05/07 20:08:24, ajuma wrote:
> https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h
> File public/web/WebSettings.h (right):
> 
>
https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h#new...
> public/web/WebSettings.h:69: virtual void
> setAcceleratedCompositingForGpuRasterizationHintEnabled(bool) { };
> The chromium-side caller has already been removed (in r268321), so this should
> be removable too.

Thanks, would you be wiling to approve this CL given that it's got green try
bubbles?  I can remove the public API in a followup CL.

[ajuma, 2014-05-07 20:28:46]

On 2014/05/07 20:28:00, abarth wrote:
> On 2014/05/07 20:08:24, ajuma wrote:
> > https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h
> > File public/web/WebSettings.h (right):
> > 
> >
>
https://codereview.chromium.org/270383002/diff/1/public/web/WebSettings.h#new...
> > public/web/WebSettings.h:69: virtual void
> > setAcceleratedCompositingForGpuRasterizationHintEnabled(bool) { };
> > The chromium-side caller has already been removed (in r268321), so this
should
> > be removable too.
> 
> Thanks, would you be wiling to approve this CL given that it's got green try
> bubbles?  I can remove the public API in a followup CL.

lgtm

[esprehn, 2014-05-07 20:29:47]

lgtm

[abarth-chromium, 2014-05-07 20:38:33]

Thanks!

[abarth-chromium, 2014-05-07 20:38:37]

The CQ bit was checked by abarth@chromium.org

[commit-bot: I haz the power, 2014-05-07 20:39:30]

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

[commit-bot: I haz the power, 2014-05-07 20:55:26]

Change committed as 173557

[kenneth.r.christiansen, 2014-05-12 11:28:32]

Why don't you use the official specced (resolution: 2dppx) media query feature
instead of the unofficial -webkit-device-pixel-ratio?

[kenneth.r.christiansen, 2014-05-12 11:52:33]

On 2014/05/12 11:28:32, kenneth.r.christiansen wrote:
> Why don't you use the official specced (resolution: 2dppx) media query feature
> instead of the unofficial -webkit-device-pixel-ratio?

I commented on the wrong CL... please ignore