NEW314085
mathml/relations/html5-tree/href-click-004.tentative.html is failing for annotation/annotation-xml element
https://bugs.webkit.org/show_bug.cgi?id=314085
Summary mathml/relations/html5-tree/href-click-004.tentative.html is failing for anno...
Frédéric Wang Nélar
Reported 2026-05-05 07:02:02 PDT
See https://searchfox.org/wubkat/rev/68f2a0d2a5f6fc91cbfb573ccf94fceaaa2f162c/LayoutTests/imported/w3c/web-platform-tests/mathml/relations/html5-tree/href-click-004.tentative-expected.txt#2 This test perform a click on annotation/annotation-xml elements with a href, to check the href attribute has no effect. But the test runner is enabled to execute the click and returns a promise failure: Unhandled rejection with value: object "Error: element click intercepted error" Note that the test uses the following rules: annotation, annotation-xml { display: initial; } .element { background: lightblue; padding: 50px; } to avoid the default display: none and empty size, but that don't seem enough. As explained in bug 314084, the annotation/annotation-xml rendering seems quite broken, and nothing will be rendered in that case. That won't be the proper way to solve this, but it's worth mentioning that tweaking the test to set an opacity on the annotations makes them visible, and the test passes: diff --git a/LayoutTests/imported/w3c/web-platform-tests/mathml/relations/html5-tree/href-click-004.tentative.html b/LayoutTests/imported/w3c/web-platform-tests/mathml/relations/html5-tree/href-click-004.tentative.html index 764222dd1f..5e84fa85ca 100644 --- a/LayoutTests/imported/w3c/web-platform-tests/mathml/relations/html5-tree/href-click-004.tentative.html +++ b/LayoutTests/imported/w3c/web-platform-tests/mathml/relations/html5-tree/href-click-004.tentative.html @@ -13,7 +13,7 @@ <style> annotation, annotation-xml { display: initial; } mphantom { visibility: visible; } - .element { background: lightblue; padding: 50px; } + .element { background: lightblue; padding: 50px; opacity: .9; } </style> </head> <body>
Attachments
Note You need to log in before you can comment on or make changes to this bug.