WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
310683
[Tahoe Debug] editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash.html is a flaky text failure.
https://bugs.webkit.org/show_bug.cgi?id=310683
Summary
[Tahoe Debug] editing/execCommand/apply-inline-style-to-element-with-no-rende...
Diego De La Toba
Reported
2026-03-24 17:38:54 PDT
editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash.html is a flaky text failure on Tahoe Debug. HISTORY:
https://results.webkit.org/?suite=layout-tests&test=editing%2FexecCommand%2Fapply-inline-style-to-element-with-no-renderer-crash.html&style=debug
DIFF: --- /Volumes/Data/worker/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/build/layout-test-results/editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash-expected.txt +++ /Volumes/Data/worker/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/build/layout-test-results/editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash-actual.txt @@ -1,3 +1,4 @@ +%uef5f%u9776%u63 PASS apply-inline-style-to-element-with-no-renderer-crash DIFF URL:
https://build.webkit.org/results/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/309871@main%20(1429)/editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash-pretty-diff.html
REPRODUCTION: I was able to reproduce on macOS 26.3 debug with the following: run-webkit-tests --no-build --no-retry --no-show-results --exit-after-n-failures=1 --expect-pass --iterations=266 --force --debug editing/execCommand/apply-inline-style-to-element-with-no-renderer-crash.html I am marking expectations as pass fail while this pends investigation.
Attachments
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2026-03-24 17:39:01 PDT
<
rdar://problem/173282462
>
Diego De La Toba
Comment 2
2026-03-24 17:47:01 PDT
Test gardening pull request:
https://github.com/WebKit/WebKit/pull/61297
EWS
Comment 3
2026-03-24 17:48:50 PDT
Test gardening commit
309882@main
(b6d3eda7fbfd): <
https://commits.webkit.org/309882@main
> Reviewed commits have been landed. Closing PR #61297 and removing active labels.
Diego De La Toba
Comment 4
2026-03-25 12:36:14 PDT
The test is flaky because the editing commands (Transpose, CreateLink, Undo) leave the DOM in a restructured state where text content from the SVG <tspan> element (%uef5f%u9776%u638a) non-deterministically appears in the text dump. Since the test's goal is only to verify that these operations don't cause a crash, it is safe to remove the SVG element from the DOM after the test completes to ensure deterministic output. A potential test adjustment is to remove the SVG element before the test runner captures the text dump. Putting this up as a PR, please review.
Diego De La Toba
Comment 5
2026-03-25 12:38:04 PDT
Pull request:
https://github.com/WebKit/WebKit/pull/61345
EWS
Comment 6
2026-03-26 12:14:22 PDT
Committed
310011@main
(c93f90c3bb07): <
https://commits.webkit.org/310011@main
> Reviewed commits have been landed. Closing PR #61345 and removing active labels.
Alexey Proskuryakov
Comment 7
2026-03-27 18:00:18 PDT
Isn't this covering up for a WebKit bug? There is no such thing as a "mangled DOM state" supposed to result in nondeterministic rendering.
Diego De La Toba
Comment 8
2026-03-30 10:35:39 PDT
Yes if the edits should result in a deterministic output then this is masking a genuine WebKit bug with how it applies style changes. Since the test's goal is only to verify that these operations don't cause a crash, I think this change is appropriate for now while this gets escalated for nondeterministic rendering.
Alexey Proskuryakov
Comment 9
2026-03-30 11:16:05 PDT
Would you be willing to file a bug about that?
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug