From ee77b8710cea05aa1c56b32b9d7d790c39a62aef Mon Sep 17 00:00:00 2001 From: Domenic Denicola Date: Tue, 9 Feb 2016 13:16:02 -0500 Subject: [PATCH] Allow not rendering nested browsing contexts This change allows user agents to skip the "update the rendering" steps, not just for top-level browsing contexts, but also for individual nested browsing contexts within the top-level one. Chrome intends to experiment with this for third-party iframes outside the browser's viewport. --- source | 27 ++++++++++++++++++++++----- 1 file changed, 22 insertions(+), 5 deletions(-) diff --git a/source b/source index 2a5d054b6b8..4d3eee86ebe 100644 --- a/source +++ b/source @@ -85521,11 +85521,11 @@ dictionary PromiseRejectionEventInit : EventInit {
  • -

    If there is a top-level browsing context B that the user agent - believes would not benefit from having its rendering updated at this time, then remove from - docs all Document objects whose browsing context's top-level browsing context - is B.

    +

    If there are top-level browsing contexts + B that the user agent believes would not benefit from having their rendering + updated at this time, then remove from docs all Document objects whose + browsing context's top-level browsing + context is in B.

    Whether a top-level browsing context would benefit from having its rendering updated depends on various factors, such as the update frequency. For example, @@ -85539,6 +85539,23 @@ dictionary PromiseRejectionEventInit : EventInit {

  • +
  • + +

    If there are a nested browsing contexts + B that the user agent believes would not benefit from having their rendering + updated at this time, then remove from docs all Document objects whose + browsing context is in B.

    + +

    As with top-level browsing + contexts, a variety of factors can influence whether it is profitable for a browser to + update the rendering of nested browsing + contexts. For example, a user agent might wish to spend less resources rendering + third-party content, especially if it is not currently visible to the user or if resources are + constrained. In such cases, the browser could decide to update the rendering for such content + infrequently or never.

    + +
  • +
  • For each fully active Document in docs, run the resize steps for that Document, passing in now as the timestamp.