Remove mark paint timing call

[npm1]

This PR addresses the concern surfaced on w3c/paint-timing#58 (comment). I think this call to mark paint timing was added to address concerns about visited link issues, but it seems that people agree 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). Having this call adds confusion and thus is being removed.

---

/webappapis.html ( diff )

[npm1]

@domenic could you take a look?

[rniwa]

This makes sense. If UA didn't execute steps 5-12 when based on the visited link state, then such a behavior difference is trivially observable by the numerous callbacks & API being invoked there (by observing that they're not invoked).

[domenic]

I'm happy to trust you all that this makes sense, but I'll note that in #3923 we seem to have separated out the three "skip update the rendering" steps (10.2 Rendering opportunities, 10.3 Unnecessary rendering, and 10.4 "for other reasons") in part so that we could add "mark paint timing" to 10.3.

The separation still makes sense, so my intuition is that we we should not re-combine them. But I wanted to check what other folks thought.

[rniwa]

Yeah, I don't think we want to re-combine those steps.

[npm1]

I agree, the current steps make sense to me.