Bug 219531

Summary: <use> fails to target <path> inserted later
Product: WebKit Reporter: Kaiido <tristan.fraipont>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, rniwa, sabouhallawa, simon.fraser, smoley, webkit-bug-importer, zalan, zimmermann
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
test case none

Kaiido
Reported 2020-12-03 22:50:16 PST
Created attachment 415389 [details] test case https://jsfiddle.net/g36aokvt/ When a <use> element targets a <path> element that will be appended in the DOM after the <use>, the <use> element fails to update and to clone the target correctly. This works fine in every browsers and in WebKit too when the target is a <rect> or a <circle>. I guess this is a recent regression, but I was unable to run bisect-builds correctly to be sure.
Attachments
test case (648 bytes, text/html)
2020-12-03 22:50 PST, Kaiido 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Smoley
Comment 1 2020-12-07 13:42:48 PST
Thanks for filing, I can reproduce this on Safari 13.1.3 as well as STP 116.
Radar WebKit Bug Importer
Comment 2 2020-12-07 13:43:01 PST
<rdar://problem/72062144>
Ahmad Saleem
Comment 3 2022-08-12 00:26:45 PDT
I am able to reproduce this bug in Safari 15.6 and Safari Technical Preview 151 where the test case does not show "red" square like other browsers (Chrome Canary 106 and Firefox Nightly 105) after some time. Just wanted to share updated test results. Thanks!
Ahmad Saleem
Comment 4 2023-05-30 10:46:17 PDT
It seems to work in WebKit ToT (264678@main) and I think it is fixed now. Will wait for someone else also to confirm since I do have some SVG patches in my local builds with above ToT.
Said Abou-Hallawa
Comment 5 2023-05-30 11:10:33 PDT
This was fixed by the fix of bug 216363 (264085@main). *** This bug has been marked as a duplicate of bug 216363 ***
Note You need to log in before you can comment on or make changes to this bug.