pFad - Phone/Frame/Anonymizer/Declutterfier! Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

URL: http://github.com/WebKit/WebKit/pull/60805

ssets/global-52276e82f63bb403.css" /> [iOS debug] http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html is a flaky text failure by diegodelatoba · Pull Request #60805 · WebKit/WebKit · GitHub
Skip to content

[iOS debug] http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html is a flaky text failure#60805

Open
diegodelatoba wants to merge 1 commit intoWebKit:mainfrom
diegodelatoba:eng/iOS-debug-http-wpt-navigation-api-scroll-behavior-manual-scroll-reload-html-is-a-flaky-text-failure
Open

[iOS debug] http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html is a flaky text failure#60805
diegodelatoba wants to merge 1 commit intoWebKit:mainfrom
diegodelatoba:eng/iOS-debug-http-wpt-navigation-api-scroll-behavior-manual-scroll-reload-html-is-a-flaky-text-failure

Conversation

@diegodelatoba
Copy link
Contributor

@diegodelatoba diegodelatoba commented Mar 17, 2026

eaf86ba

[iOS debug] http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html is a flaky text failure
rdar://172757985
https://bugs.webkit.org/show_bug.cgi?id=310111

Reviewed by NOBODY (OOPS!).

This test is flakily failing since scroll position is reported as 0 instead of 8.
The issue is that scroll positions do not settle in time on (slow) debug builds
due to overlapping async scroll updates through the scrolling coordinator.

Fix in manual-scroll-reload.html:
- Add rAF before navigate_event.scroll() so that the scroll anchoring
  from buffer.remove() can settle in the UI process.
- Add rAF after navigate_event.scroll() so that the scroll-to-fragment
  can settle in the UI process before asserting.

* LayoutTests/http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html:
* LayoutTests/platform/ios/TestExpectations:

eaf86ba

Misc iOS, visionOS, tvOS & watchOS macOS Linux Windows
✅ 🧪 style ✅ 🛠 ios ✅ 🛠 mac ✅ 🛠 wpe ✅ 🛠 win
✅ 🛠 ios-sim ✅ 🛠 mac-AS-debug ✅ 🧪 wpe-wk2 ✅ 🧪 win-tests
✅ 🧪 webkitperl ✅ 🧪 ios-wk2 ✅ 🧪 api-mac ✅ 🧪 api-wpe
✅ 🧪 ios-wk2-wpt ✅ 🧪 api-mac-debug ✅ 🛠 gtk3-libwebrtc
✅ 🧪 api-ios ✅ 🧪 mac-wk1 ✅ 🛠 gtk
✅ 🧪 mac-wk2 ✅ 🧪 gtk-wk2
✅ 🛠 vision ✅ 🧪 mac-AS-debug-wk2 ✅ 🧪 api-gtk
✅ 🛠 vision-sim ✅ 🧪 mac-wk2-stress ✅ 🛠 playstation
✅ 🧪 vision-wk2 ❌ 🧪 mac-intel-wk2
✅ 🛠 tv
✅ 🛠 tv-sim
✅ 🛠 watch
✅ 🛠 watch-sim

…oad.html is a flaky text failure

rdar://172757985
https://bugs.webkit.org/show_bug.cgi?id=310111

Reviewed by NOBODY (OOPS!).

This test is flakily failing since scroll position is reported as 0 instead of 8.
The issue is that scroll positions do not settle in time on (slow) debug builds
due to overlapping async scroll updates through the scrolling coordinator.

Fix in manual-scroll-reload.html:
- Add rAF before navigate_event.scroll() so that the scroll anchoring
  from buffer.remove() can settle in the UI process.
- Add rAF after navigate_event.scroll() so that the scroll-to-fragment
  can settle in the UI process before asserting.

* LayoutTests/http/wpt/navigation-api/scroll-behavior/manual-scroll-reload.html:
* LayoutTests/platform/ios/TestExpectations:
@diegodelatoba diegodelatoba self-assigned this Mar 17, 2026
@webkit-ews-buildbot webkit-ews-buildbot added the merging-blocked Applied to prevent a change from being merged label Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merging-blocked Applied to prevent a change from being merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

pFad - Phonifier reborn

Pfad - The Proxy pFad © 2024 Your Company Name. All rights reserved.





Check this box to remove all script contents from the fetched content.



Check this box to remove all images from the fetched content.


Check this box to remove all CSS styles from the fetched content.


Check this box to keep images inefficiently compressed and original size.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy