| Aoyuan Zuo | 00831ec | 2024-06-04 16:34:26 | [diff] [blame] | 1 | # Interaction to Next Paint Changes in Chrome 111 |
| 2 | |
| 3 | ## Bug fix: Event Timing API no longer reports very long durations when interaction leads to "open in new tab" |
| 4 | |
| 5 | This bug fix causes the Event Timing API to ignore the presentation time if |
| 6 | the page visibility changed. Before the bug fix, if the interaction caused the |
| 7 | page to be hidden, the `duration` in Event Timing would report the time the |
| 8 | page became visible again. This is technically the "next paint", but since it |
| 9 | involves waiting for the user to switch back to the page, it's not representative |
| 10 | of performance, so it is now ignored. |
| 11 | |
| 12 | This bug affected the Event Timing API _only_. The correct data has always been |
| 13 | reported to the Chrome User Experience report. So this is an issue developers |
| 14 | may see in real user monitoring analytics. |
| 15 | |
| 16 | [Source code](https://chromium-review.googlesource.com/c/chromium/src/+/3926369) |
| 17 | |
| 18 | ## When were users affected? |
| 19 | |
| 20 | Chrome 111 was released the week of March 7, 2023. |
