Assert fDeviceClipBounds is always empty when clip is empty

Assert fDeviceClipBounds is always empty when clip is empty

I've fixed a few issues where this assert triggers.  The
nastiest case is when the client sets the clip to a strange
version of an empty rect (Ex: L,T,R,B=0,0,0,10).

I think I've made sufficient fixes so that
fDeviceClipBounds is always empty when clip is empty.

Let's test it though.

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003

Committed: https://skia.googlesource.com/skia/+/0c685ee188a5e500df25a34fa6edfceb4cbb795c

[msarett, 2016-08-12 15:11:32]

Description was changed from

==========
Assert fDeviceClipBounds is always empty when clip is empty

BUG=skia:
==========

to

==========
Assert fDeviceClipBounds is always empty when clip is empty

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003
==========

[msarett, 2016-08-12 15:14:27]

Description was changed from

==========
Assert fDeviceClipBounds is always empty when clip is empty

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003
==========

to

==========
Assert fDeviceClipBounds is always empty when clip is empty

I've fixed a few issues where this assert triggers.  The
nastiest case is when the client sets the clip to a strange
version of an empty rect (Ex: L,T,R,B=0,0,0,10).

I think I've made sufficient fixes so that
fDeviceClipBounds is always empty when clip is empty.

Let's test it though.

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003
==========

[msarett, 2016-08-12 15:20:02]

The CQ bit was checked by msarett@google.com to run a CQ dry run

[commit-bot: I haz the power, 2016-08-12 15:20:12]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-12 15:40:24]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-12 15:40:25]

Dry run: This issue passed the CQ dry run.

[msarett, 2016-08-12 15:50:30]

msarett@google.com changed reviewers:
+ mtklein@google.com, reed@google.com

[msarett, 2016-08-12 15:50:30]

Planning to land this after/if the roll succeeds on the original change.

[mtklein, 2016-08-12 16:27:04]

lgtm

[reed1, 2016-08-12 22:28:21]

lgtm

[msarett, 2016-08-14 20:16:27]

The CQ bit was checked by msarett@google.com

[commit-bot: I haz the power, 2016-08-14 20:16:33]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-14 20:51:19]

Description was changed from

==========
Assert fDeviceClipBounds is always empty when clip is empty

I've fixed a few issues where this assert triggers.  The
nastiest case is when the client sets the clip to a strange
version of an empty rect (Ex: L,T,R,B=0,0,0,10).

I think I've made sufficient fixes so that
fDeviceClipBounds is always empty when clip is empty.

Let's test it though.

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003
==========

to

==========
Assert fDeviceClipBounds is always empty when clip is empty

I've fixed a few issues where this assert triggers.  The
nastiest case is when the client sets the clip to a strange
version of an empty rect (Ex: L,T,R,B=0,0,0,10).

I think I've made sufficient fixes so that
fDeviceClipBounds is always empty when clip is empty.

Let's test it though.

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2246503003

Committed:
https://skia.googlesource.com/skia/+/0c685ee188a5e500df25a34fa6edfceb4cbb795c
==========

[commit-bot: I haz the power, 2016-08-14 20:51:20]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/0c685ee188a5e500df25a34fa6edfceb4cbb795c