RESOLVED FIXED309186
[iOS] fast/css/target-fragment-match.html is a constant text failure
https://bugs.webkit.org/show_bug.cgi?id=309186
Summary [iOS] fast/css/target-fragment-match.html is a constant text failure
Diego De La Toba
Reported 2026-03-04 13:23:02 PST
fast/css/target-fragment-match.html is a constant text failure on iOS. Appears to be a rebaseline. HISTORY: https://results.webkit.org/?suite=layout-tests&test=fast%2Fcss%2Ftarget-fragment-match.html DIFF: --- /Volumes/Data/Builds/Ios/Debug/TestBuild308626@main/layout-test-results/fast/css/target-fragment-match-expected.txt +++ /Volumes/Data/Builds/Ios/Debug/TestBuild308626@main/layout-test-results/fast/css/target-fragment-match-actual.txt @@ -5,5 +5,5 @@ RenderBody {BODY} at (8,16) size 784x20 RenderBlock {DIV} at (0,0) size 784x20 RenderBlock {P} at (0,0) size 784x20 - RenderText {#text} at (0,0) size 624x19 + RenderText {#text} at (0,0) size 624x20 text run at (0,0) width 624: "I should be highlighted first because of the anchor, and de-highlighted when there is no fragment." DIFF URL: https://build.webkit.org/results/Apple-iOS-26-Simulator-Debug-WK2-Tests/308626%40main%20(817)/fast/css/target-fragment-match-pretty-diff.html REPRODUCTION: Reproduced with the following on iOS 26.2 debug ToT with the following: run-webkit-tests --force --no-retry --debug --ios-simulator --iterations 100 fast/css/target-fragment-match.html I am going to mark expectations as fail.
Attachments
Radar WebKit Bug Importer
Comment 1 2026-03-04 13:23:09 PST
Diego De La Toba
Comment 2 2026-03-04 13:32:35 PST
EWS
Comment 3 2026-03-04 13:36:25 PST
Test gardening commit 308659@main (67878162222b): <https://commits.webkit.org/308659@main> Reviewed commits have been landed. Closing PR #59915 and removing active labels.
Diego De La Toba
Comment 4 2026-03-04 15:58:05 PST
EWS
Comment 5 2026-03-05 08:58:53 PST
Committed 308699@main (9f659bcc0220): <https://commits.webkit.org/308699@main> Reviewed commits have been landed. Closing PR #59929 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.