Don't expand empty rect during rect mapping

Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.

Committed: https://crrev.com/67c516aaed2486295a98d7f0ff2235b921cd7933
Cr-Commit-Position: refs/heads/master@{#424970}

[Xianzhu, 2016-10-12 22:27:37]

The CQ bit was checked by wangxianzhu@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-12 22:28:05]

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

[Xianzhu, 2016-10-12 22:50:00]

Description was changed from

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.
==========

to

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.
==========

[Xianzhu, 2016-10-12 23:30:41]

The CQ bit was checked by wangxianzhu@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-12 23:30:49]

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

[Xianzhu, 2016-10-12 23:31:03]

wangxianzhu@chromium.org changed reviewers:
+ chrishtr@chromium.org

[commit-bot: I haz the power, 2016-10-13 00:14:09]

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

[commit-bot: I haz the power, 2016-10-13 00:14:10]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[chrishtr, 2016-10-13 00:21:46]

The CQ bit was checked by chrishtr@chromium.org

[chrishtr, 2016-10-13 00:21:46]

lgtm

[commit-bot: I haz the power, 2016-10-13 00:22:00]

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-10-13 00:38:36]

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

[commit-bot: I haz the power, 2016-10-13 00:38:37]

Exceeded global retry quota

[Xianzhu, 2016-10-13 03:16:24]

The CQ bit was checked by wangxianzhu@chromium.org

[Xianzhu, 2016-10-13 03:16:25]

The patchset sent to the CQ was uploaded after l-g-t-m from
chrishtr@chromium.org
Link to the patchset: https://codereview.chromium.org/2416693002/#ps60001
(title: "Rebaseline")

[commit-bot: I haz the power, 2016-10-13 03:16:41]

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-10-13 06:47:07]

Description was changed from

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.
==========

to

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.
==========

[commit-bot: I haz the power, 2016-10-13 06:47:08]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-10-13 06:48:21]

Description was changed from

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.
==========

to

==========
Don't expand empty rect during rect mapping

For example, enclosingIntRect(LayoutRect(0.5, 0.5, 0, 0)) results
IntRect(0, 0, 1, 1). This causes unnecessary non-empty visual rects
mapped from empty LayoutRects.

This CL is mainly to reduce the difference between the old path and
slimmingPaintInvalidation with pixel snapping feature.

Committed: https://crrev.com/67c516aaed2486295a98d7f0ff2235b921cd7933
Cr-Commit-Position: refs/heads/master@{#424970}
==========

[commit-bot: I haz the power, 2016-10-13 06:48:22]

Patchset 4 (id:??) landed as
https://crrev.com/67c516aaed2486295a98d7f0ff2235b921cd7933
Cr-Commit-Position: refs/heads/master@{#424970}

[Xianzhu, 2016-11-30 20:10:02]

A revert of this CL (patchset #4 id:60001) has been created in
https://codereview.chromium.org/2545573002/ by wangxianzhu@chromium.org.

The reason for reverting is: It changed
  transform->mapRect(enclosingIntRect(rect))
to
  transform->mapRect(FloatRect(enclosingIntRect(rect)))
causing missing enclosingIntRect() after the transform.

We may also need enclosingIntRect for empty rects because even empty
object can have visible filter depending on pixel snapping here.

BUG=669774.