From 9270454774fc78d5fe1a85007eda2901ba461ba9 Mon Sep 17 00:00:00 2001 From: npm1 Date: Fri, 6 Mar 2020 13:59:57 -0500 Subject: [PATCH] Add link to viewport A request was made to add a link to the viewport. Fixes https://github.com/w3c/paint-timing/issues/58 --- painttiming.bs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/painttiming.bs b/painttiming.bs index 026bac7..0f5aa96 100644 --- a/painttiming.bs +++ b/painttiming.bs @@ -25,6 +25,8 @@ 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 Introduction {#intro} @@ -64,7 +66,7 @@ Formally, we consider the user agent to have "rendered" a document when it has p First Contentful Paint entry contains a {{DOMHighResTimeStamp}} reporting the time when the user agent first rendered any text, image (including background images), non-white canvas or SVG. This excludes any content of iframes, but includes text with pending webfonts. This is the first time users could start consuming page content. -Whenever a user agent preemptively paints content outside of the viewport, those paints MUST be considered for First Paint and First Contentful Paint. +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.