From a07dc8694e13bb2abe276680f7a043a28286f4ee Mon Sep 17 00:00:00 2001 From: npm1 Date: Thu, 26 Mar 2020 14:42:23 -0400 Subject: [PATCH] Remove unneeded viewport mentions For https://github.com/w3c/paint-timing/issues/58 --- painttiming.bs | 6 ------ 1 file changed, 6 deletions(-) diff --git a/painttiming.bs b/painttiming.bs index b858231..f29cbc8 100644 --- a/painttiming.bs +++ b/painttiming.bs @@ -25,8 +25,6 @@ urlPrefix: https://www.w3.org/TR/performance-timeline-2/; spec: PERFORMANCE-TIME text: supportedEntryTypes; url: #supportedentrytypes-attribute urlPrefix: https://www.w3.org/TR/hr-time-2/#idl-def-domhighrestimestamp; spec: HR-TIME-2; type: typedef; text: DOMHighResTimeStamp -urlPrefix: https://www.w3.org/TR/CSS2/visuren.html; spec: CSS-2; - type: dfn; url: #viewport; text: viewport urlPrefix: https://www.w3.org/TR/CSS22/visufx.html; spec: CSS-2; type: dfn; url: #propdef-visibility; text: visibility; urlPrefix: https://www.w3.org/TR/css-color-3; spec: CSS-COLOR-3; @@ -158,10 +156,6 @@ An [=element=] |el| is paintable when all of the following apply: First contentful paint entry contains a {{DOMHighResTimeStamp}} reporting the time when the user agent first rendered a [=document=] which includes at least one [=element=] that is both [=contentful=] and [=paintable=]. -Whenever a user agent preemptively paints content outside of the [=viewport=], those paints must be considered for [=first paint=] and [=first contentful paint=]. - - NOTE: a user agent has freedom to choose their own strategy for painting. Such strategy could even be to never paint content that is outside of the viewport. Therefore, different user agents can have different behaviors for [=first paint=] and [=first contentful paint=] in edge cases where the only content occurs outside of the viewport. - The {{PerformancePaintTiming}} interface {#sec-PerformancePaintTiming} =======================================