Add INP changelog and log changes for M111
Change-Id: I9e3d8db92006921897f6bf28b8ca825de2e8446e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4455780
Reviewed-by: Michal Mocny <[email protected]>
Commit-Queue: Annie Sullivan <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1134778}
diff --git a/docs/speed/metrics_changelog/2023_01_inp.md b/docs/speed/metrics_changelog/2023_01_inp.md
new file mode 100644
index 0000000..11f6f029
--- /dev/null
+++ b/docs/speed/metrics_changelog/2023_01_inp.md
@@ -0,0 +1,20 @@
+# Interaction to Next Paint Changes in Chrome 109
+
+## Chrome prioritizes compositing after input events
+
+A change in the Chrome scheduler to prioritize rendering after user interaction
+resulted in multiple improvements to user-experienced Interaction to Next Paint.
+
+Applications with a large amount of typing on desktop saw improvements to their
+slowest interaction times as many keypresses right after another displayed on
+screen more quickly.
+
+Mobile sites in which users were tapping multiple times due to slow interactions
+saw large improvements to interaction times, as 500ms+ interactions no longer
+"piled up" waiting for the user to stop tapping before the screen began to update.
+
+Source code of the change is linked [in the chromium issue tracker](https://bugs.chromium.org/p/chromium/issues/detail?id=853771)
+
+## When were users affected?
+
+Chrome 109 was released the week of January 10, 2023.
diff --git a/docs/speed/metrics_changelog/2023_04_inp.md b/docs/speed/metrics_changelog/2023_04_inp.md
new file mode 100644
index 0000000..1c519cb
--- /dev/null
+++ b/docs/speed/metrics_changelog/2023_04_inp.md
@@ -0,0 +1,20 @@
+# Interaction to Next Paint Changes in Chrome 111
+
+## Bug fix: Event Timing API no longer reports very long durations when interaction leads to "open in new tab"
+
+This bug fix causes the Event Timing API to ignore the presentation time if
+the page visibility changed. Before the bug fix, if the interaction caused the
+page to be hidden, the `duration` in Event Timing would report the time the
+page became visible again. This is technically the "next paint", but since it
+involves waiting for the user to switch back to the page, it's not representative
+of performance, so it is now ignored.
+
+This bug affected the Event Timing API _only_. The correct data has always been
+reported to the Chrome User Experience report. So this is an issue developers
+may see in real user monitoring analytics.
+
+[Source code](https://chromium-review.googlesource.com/c/chromium/src/+/3926369)
+
+## When were users affected?
+
+Chrome 111 was released the week of March 7, 2023.
diff --git a/docs/speed/metrics_changelog/README.md b/docs/speed/metrics_changelog/README.md
index 54e552c..528ee1f 100644
--- a/docs/speed/metrics_changelog/README.md
+++ b/docs/speed/metrics_changelog/README.md
@@ -6,7 +6,9 @@
* [First Input Delay](fid.md)
* [Cumulative Layout Shift](cls.md)
* [First Contentful Paint](fcp.md)
+ * [Interaction to Next Paint](inp.md)
See also:
- * [Lighthouse performance scoring changelog](https://web.dev/performance-scoring/)
\ No newline at end of file
+ * [Lighthouse performance scoring changelog](https://web.dev/performance-scoring/)
+ * [Chrome UX Report Release Notes](https://developer.chrome.com/docs/crux/release-notes/)
\ No newline at end of file
diff --git a/docs/speed/metrics_changelog/inp.md b/docs/speed/metrics_changelog/inp.md
new file mode 100644
index 0000000..1da0c89e
--- /dev/null
+++ b/docs/speed/metrics_changelog/inp.md
@@ -0,0 +1,10 @@
+# Interaction to Next Paint Changelog
+
+This is a list of changes to [Interaction to Next Paint](https://web.dev/inp).
+
+* Chrome 111
+ * Metric bug fix: [Event Timing API no longer reports very long durations when interaction leads to "open in new tab"](2023_04_inp.md)
+* Chrome 109
+ * Implementation optimizations: [A change in Chrome to prioritize compositing after input events caused a significant improvement to INP](2023_01_inp.md)
+* Chrome 96
+ * Experimental metric exposed via API: [Event Timing InteractionID](https://web.dev/inp/) available via [PerformanceObserver API](https://www.w3.org/TR/event-timing/)
