From 47546e900bb82bbed9db0249f907f4ccec611dda Mon Sep 17 00:00:00 2001 From: jwilliams720 Date: Fri, 1 Nov 2024 12:10:33 +0000 Subject: [PATCH] remove incomplete sentence from considered alternatives and add the section to the TOCs --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 41729d1..8314e5b 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,7 @@ 1. [Shadow DOM](#shadow-dom) 1. [Security and Privacy](#security-and-privacy) 1. [Polyfill](#polyfill) +1. [Considered alternatives](#considered-alternatives) 1. [Questions](#questions) 1. [Implementation](#implementation-work) 1. [Glossary](#glossary) @@ -228,8 +229,6 @@ Element Timing can be applied to any element by the developer, but is too limite For the reasons mentioned in the [Motivation](#motivation), Largest Contentful Paint (LCP) isn't useful enough to time when specific parts of the page have loaded, it utilizes element timing for its functionality and thus has the same shortcomings as element timing. -We looked into using a user-space polyfill instead of building a feature into the - ### User-space polyfill in JavaScript As mentioned in the [Motivation](#motivation) the polyfill would need a few things in place to work properly and can add overhead to the web application.