scheduler: Don't throttle 0x0 frames

scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
Committed: https://crrev.com/b83d755a52a7fe9792af9ee360e551c157ad576e
Cr-Commit-Position: refs/heads/master@{#418174}

[Sami, 2016-09-12 10:14:54]

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

[commit-bot: I haz the power, 2016-09-12 10:15:13]

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

[Sami, 2016-09-12 10:15:31]

Description was changed from

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
==========

to

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
==========

[Sami, 2016-09-12 10:15:31]

skyostil@chromium.org changed reviewers:
+ ojan@chromium.org

[commit-bot: I haz the power, 2016-09-12 11:49:11]

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

[commit-bot: I haz the power, 2016-09-12 11:49:12]

Dry run: This issue passed the CQ dry run.

[ojan, 2016-09-13 05:12:37]

The CQ bit was checked by ojan@chromium.org

[ojan, 2016-09-13 05:12:38]

lgtm

[commit-bot: I haz the power, 2016-09-13 05:12:56]

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-09-13 05:16:41]

Description was changed from

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
==========

to

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
==========

[commit-bot: I haz the power, 2016-09-13 05:16:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-13 05:18:54]

Description was changed from

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217
==========

to

==========
scheduler: Don't throttle 0x0 frames

This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG=644217

Committed: https://crrev.com/b83d755a52a7fe9792af9ee360e551c157ad576e
Cr-Commit-Position: refs/heads/master@{#418174}
==========

[commit-bot: I haz the power, 2016-09-13 05:18:55]

Patchset 1 (id:??) landed as
https://crrev.com/b83d755a52a7fe9792af9ee360e551c157ad576e
Cr-Commit-Position: refs/heads/master@{#418174}