Bug 139155 - Changing the ID of an SVG element in the <defs> section should be reflected in the SVG if it has any element which is referencing the changed defined element.
Summary: Changing the ID of an SVG element in the <defs> section should be reflected i...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar, LayerBasedSVGEngine
Depends on:
Blocks:
 
Reported: 2014-12-01 14:56 PST by Said Abou-Hallawa
Modified: 2023-12-22 19:25 PST (History)
7 users (show)

See Also:


Attachments
dynamic changes to the element for a given ID are reflected in textPath (952 bytes, image/svg+xml)
2014-12-01 14:56 PST, Said Abou-Hallawa
no flags Details
Expected file (515 bytes, image/svg+xml)
2014-12-01 14:57 PST, Said Abou-Hallawa
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Said Abou-Hallawa 2014-12-01 14:56:43 PST
Created attachment 242348 [details]
dynamic changes to the element for a given ID are reflected in textPath

Open the attached test file.  Compare it with the expected file.  They should be identical.

Changing the ID of an element in the <defs> section should be reflected in the SVG if it has any element which is referencing the changed defined element.

NOTE: The attached file is a test file imported from Mozilla svg test suite.
Comment 1 Radar WebKit Bug Importer 2014-12-01 14:57:17 PST
<rdar://problem/19107404>
Comment 2 Said Abou-Hallawa 2014-12-01 14:57:34 PST
Created attachment 242349 [details]
Expected file
Comment 3 Ahmad Saleem 2022-07-14 11:25:45 PDT
I am able to reproduce this bug in Safari 15.5 on macOS 12.4 and Safari Technical Preview 148 using attached test case (named - dynamic changes...) while all other browsers (Chrome Canary 105 and Firefox Nightly 104) works as expected and matches with the output of "Expected file". Thanks!
Comment 5 Ryosuke Niwa 2023-07-27 10:25:46 PDT
This appears fixed in STP174.
Comment 6 Ahmad Saleem 2023-07-27 10:28:04 PDT
(In reply to Ryosuke Niwa from comment #5)
> This appears fixed in STP174.

I am still able to reproduce this on STP174.

It does not show any text while Chrome Canary 117 show 'Should see this' as expected test file.
Comment 7 Ahmad Saleem 2023-07-27 10:35:31 PDT
(In reply to Ahmad Saleem from comment #6)
> (In reply to Ryosuke Niwa from comment #5)
> > This appears fixed in STP174.
> 
> I am still able to reproduce this on STP174.
> 
> It does not show any text while Chrome Canary 117 show 'Should see this' as
> expected test file.

OK, if I open 'Developer Tools' then the text start showing up. :-?