diff options
| author |  Jacob Groß <kurtextrem@gmail.com>
| 2023-08-25 14:43:52 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2023-08-25 08:43:52 -0400 |
| commit | acf652fc1d5db166231e87e22d0d50444f5556d8 (patch) | |
| tree | 95f80b04a9c6cb208433f403558d11671ce56031 /benchmark/bench/_util.js | |
| parent | a35c21cfc8e6074a8effd0529dd6e852bbd769a6 (diff) | |
| download | astro-acf652fc1d5db166231e87e22d0d50444f5556d8.tar.gz astro-acf652fc1d5db166231e87e22d0d50444f5556d8.tar.zst astro-acf652fc1d5db166231e87e22d0d50444f5556d8.zip | |
feat(ViewTransitions): use `scrollend` instead of `scroll` where supported (#8156)
* feat(ViewTransitions): use `scrollend` instead of `scroll` where supported
The [scrollend](https://developer.chrome.com/blog/scrollend-a-new-javascript-event/#event-details) mechanism seems like a better way to record the scroll position compared to throttling, so we could use it whenever a browser supports it.
Additionally, I've removed the `{passive}` flag from the `scroll` event, as it does nothing ([source](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener?retiredLocale=de#improving_scrolling_performance_with_passive_listeners:~:text=You%20don%27t%20need%20to%20worry%20about%20the%20value%20of%20passive%20for%20the%20basic%20scroll%20event.%20Since%20it%20can%27t%20be%20canceled%2C%20event%20listeners%20can%27t%20block%20page%20rendering%20anyway.)).
* Create long-chefs-jump.md
* fix typo / update comment
Diffstat (limited to 'benchmark/bench/_util.js')
0 files changed, 0 insertions, 0 deletions