SVG <image> element not rerendering after removeAttribute("xlink:href")
Categories
(Core :: SVG, defect)
Tracking
()
People
(Reporter: marti.kanera, Assigned: longsonr)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:129.0) Gecko/20100101 Firefox/129.0
Steps to reproduce:
- Create an SVG element with an <image> tag in the HTML.
- Set the xlink:href attribute on the <image> tag to point to an image URL.
- Use JavaScript to call image.removeAttribute('xlink:href') on the <image> element.
Actual results:
Even though retrieving the attribute using image.getAttribute("xlink:href") returns null, the image itself remains visible.
Expected results:
The image should no longer be visible when the xlink:href attribute is removed.
Updated•2 years ago
|
| Reporter | ||
Comment 1•2 years ago
|
||
Here is an example demonstrating the issue: https://codepen.io/martinkanera/pen/VwJvdZX
| Assignee | ||
Comment 2•2 years ago
|
||
Comment 3•2 years ago
|
||
regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2601aa4526288006e2dc3f4e84f5735db5da60e9&tochange=4d770d6a88770f9af267a8a34e002f955b0c37cd
Probably regression from this commit in there:
Emilio Cobos Álvarez — Bug 1756750 - Don't reframe <svg:image> on loading / broken changes. r=jfkthame
Comment 4•2 years ago
|
||
Comment on attachment 9413650 [details]
testcase 1 (using removeAttributeNS)
Note, Robert adjusted the testcase to use removeAttributeNS (whereas the reporter's original testcase used removeAttribute), in case removeAttributeNS worked better here.
In fact both versions work before the regression-range, and both fail after the regression-range.
Comment 5•2 years ago
|
||
Comment 6•2 years ago
|
||
Set release status flags based on info from the regressing bug 1756750
:emilio, since you are the author of the regressor, bug 1756750, could you take a look?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 7•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Comment 8•2 years ago
|
||
Comment 11•2 years ago
•
|
||
I triggered lando at longsonr's request (he's AFK but wanted to get this in), but then I noticed some minor things I'd like to improve in the tests -- and I think one of the changes might reveal a piece of this that's not-yet-fixed. I'll file a followup bug or two.
Comment 12•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Comment 14•2 years ago
|
||
The patch landed in nightly and beta is affected.
:longsonr, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox129towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 15•2 years ago
|
||
Given that it regressed two years ago, I imagine it's not encountered that much.
Updated•2 years ago
|
Description
•