Re: [w3ctag/design-reviews] Element Timing API for text (#395)

So looking at the [modifications to CSS](https://wicg.github.io/element-timing/#sec-modifications-CSS), I'm a little concerned that this refers to "When the user agent is executing the painting order", since I don't think that's particularly well-defined.  Different UAs might render into surfaces/layers at different times or for different reasons.  If the intent is that the element be visible on screen, it might be worth saying that more explicitly.  That said, maybe the cases where UAs will differ are edge cases and it's OK for the performance timeline to differ in those edge cases (e.g., which parts of an animating transformed element that's partially offscreen are rendered initially).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/395#issuecomment-561315836