Don't throttle disposed FrameViews

Don't throttle disposed FrameViews

After a FrameView has been disposed, don't allow throttling the rendering
pipeline for it because we can no longer reliably determine if the FrameView is
visible.

BUG=637373

[Sami, 2016-10-13 03:26:35]

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

[commit-bot: I haz the power, 2016-10-13 03:26:57]

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

[Sami, 2016-10-13 03:27:18]

Description was changed from

==========
Don't throttle disposed FrameViews

After a FrameView has been disposed, don't allow throttling the rendering
pipeline for it because we can no longer reliably determine if the FrameView is
visible.

BUG=637373
==========

to

==========
Don't throttle disposed FrameViews

After a FrameView has been disposed, don't allow throttling the rendering
pipeline for it because we can no longer reliably determine if the FrameView is
visible.

BUG=637373
==========

[Sami, 2016-10-13 03:27:18]

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

[Sami, 2016-10-13 03:27:57]

So this fixes the iframe not getting painted, but I feel like I'm still missing
something or there's something off in our lifecycle model.

[dcheng, 2016-10-13 04:41:25]

Hmm, yeah something seems really broken. Let me poke at this bug tomorrow when
I'm in the office. Once disposed, I don't think a FrameView should really be
involving itself in layout (as its LocalFrame should be in the process of being
removed from the DOM).

[Sami, 2016-10-13 04:45:02]

On 2016/10/13 04:41:25, dcheng wrote:
> Hmm, yeah something seems really broken. Let me poke at this bug tomorrow when
> I'm in the office. Once disposed, I don't think a FrameView should really be
> involving itself in layout (as its LocalFrame should be in the process of
being
> removed from the DOM).

Thanks, I'd appreciate a second pair of eyes on this!

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

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

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

Dry run: This issue passed the CQ dry run.