Issue metadata
Sign in to add a comment
|
Dynamic updates to foreignObject element aren't reflected in the UI
Reported by
k...@evolphin.com,
Jun 29 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Render the follow tree: <svg><foreignObject><p>hello</p></foreignObject></svg> 2. Remove the <foreignObject> via JS (or simply via the Elements panel). 3. The element was removed from the DOM tree but remains in the UI. What is the expected behavior? Removing the element from the DOM tree should remove the element from the UI. What went wrong? The <foreignObject> element was removed from the DOM tree but remains rendered in the UI until subsequent DOM updates trigger a repaint. Did this work before? Yes Does this work in other browsers? Yes Chrome version: 67.0.3396.99 Channel: stable OS Version: OS X 10.13.4 Flash Version:
,
Jun 29 2018
Thanks for filing the issue! @Reporter: Could you please share a sample test file/URL which helps us to triage the issue in a better way. Any further inputs from your end may help us.
,
Jun 29 2018
We can produce a test case form what you have given us (although it would save us some time if you already have it). Does this reproduce in Chrome Canary? We have been fixing a lot of issues related to SVG invalidation recently and this might now work as expected.
,
Jun 29 2018
Hi guys, thanks for the response.
I just tried Canary -- the issue is happening there too.
I'm working on a simple test case. The issue is occurring in my application, but it doesn't seem to occur in the simplest of pages, i.e.:
<html>
<body>
<svg>
<foreignObject>
<p>hello</p>
</foreignObject>
</svg>
</body>
</html>
...so I'm still trying to figure out what I need to introduce for the issue to surface.
Thanks again for the response and for the wonderful browser :)
,
Jun 29 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 29 2018
Thanks very much. Keep trying to reproduce in a reasonable test case. We check back in a couple of weeks if we don't hear from you.
,
Jul 16
Any update? I seem to recall a recent change that adjusted invalidation for foreign object. There's a chance that this may be fixed shortly in Canary. Am I correct in understanding that a workaround is to do some other Dom manipulation to force a repaint?
,
Jul 16
Hi, sorry, haven't been able to put together a simpler test case yet, but I will definitely update you if/when I do. Yes, other DOM manipulations eventually get the foreignObject to update. Even just scrolling the page up or down fixes the issue after a little while (1 to 10 seconds in my app). Thanks again.
,
Jul 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 17
Thanks. I'll put a NextAction of a month or so. Just let us know whenever you get new info, no rush.
,
Jul 31
As per comment#8 adding Needs-Feedback label and awaiting the sample test case from reporter. Thanks!
,
Aug 20
The NextAction date has arrived: 2018-08-20
,
Aug 20
Marking this as external dependency due to the need for a reduced test case. I'll close it when it rolls around again next year.
,
Aug 20
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by vamshi.kommuri@chromium.org
, Jun 29 2018