Skip to content

Commit

Permalink
Remove one "mark paint timing call" in update the rendering
Browse files Browse the repository at this point in the history
This addresses the concern surfaced in
w3c/paint-timing#58 (comment).
This call was added to address concerns about visited link issues, but
the agreement on that issue is that this edge case is solved by
requiring user agents to paint when such a link is present even if such
link is styled by color: white (or whichever default background color).
  • Loading branch information
npm1 authored Mar 12, 2020
1 parent 916a923 commit 7eef537
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -92540,8 +92540,7 @@ dictionary <dfn>PromiseRejectionEventInit</dfn> : <span>EventInit</span> {
rendering would have no visible effect and which possess no <code>Document</code> objects with
a non-empty <span>map of animation frame callbacks</span>, then remove from <var>docs</var>
all <code>Document</code> objects whose <span data-x="concept-document-bc">browsing
context</span> is in <var>browsingContexts</var>. Invoke the <span>mark paint timing</span>
algorithm for each <code>Document</code> object removed.</p></li>
context</span> is in <var>browsingContexts</var>.</p></li>

<li>
<p>If there are <span data-x="browsing context">browsing contexts</span>
Expand Down

0 comments on commit 7eef537

Please sign in to comment.