New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 795174 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 657860
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

devtools mismatches DOM of SVG elements

Reported by zambonif...@gmail.com, Dec 15 2017

Issue description

Chrome Version: 63.0.3239.84
OS: Ubuntu 17.10

It seems like devtools doesn’t update when SVG elements are updated through certain APIs. The attached file is an HTML document with a button that randomly mutates the DOM of a couple SVG elements. If you inspect the SVG elements through devtools, you will see that it fails to update its visualization of the DOM.

You can further verify that this is indeed a bug by trying to “edit the element as HTML”, which will show the updated DOM, mismatching the previous representation.
 
svgbug.html
797 bytes View Download

Comment 1 by gov...@chromium.org, Dec 15 2017

Cc: ranjitkan@chromium.org pbomm...@chromium.org brajkumar@chromium.org
Labels: Needs-Triage-M63
Cc: krajshree@chromium.org
Components: Platform>DevTools Blink>SVG
Labels: Triaged-ET Needs-Feedback
Tested the issue on ubuntu 14.04 using chrome reported version #63.0.3239.84.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened the attached file "svgbug.html"
2. Inspected the "Change things" button.
3. Clicked on the button and did not observe anything happen.
4. Tried to “edit the element as HTML” and observed a rectangle box appearing. 

zambonifofex@ - Could you please check the screen cast and please let us know the issue exactly. If possible please provide a screen cast explaining the issue.
This will help us in triaging the issue further.

Thanks...!!
795174.ogv
3.2 MB View Download

Comment 3 by f...@opera.com, Dec 15 2017

Mergedinto: 657860
Status: Duplicate (was: Unconfirmed)
Hello, krajshree@. You have been inspecting the DOM of the wrong element. You should be inspecting the `svg` and `polyline` elements, not the `button` element.

Also, I don’t think the merge as a duplicate was appropriate. The two issues seem related, but here I am not doing any asynchronous mutation. All mutation is done synchronously during the `click` event of the button.

Comment 5 by f...@opera.com, Dec 15 2017

Yes, the issue has nothing to do with asynchronous mutation (as should have been made clear by comments on the dupe.) It's a notification hook that isn't called in some code-paths related to attribute updates. (This is also why it happens to affect MutationObserver.)
Ah, I see. I had skimmed through the comments, and so that wasn’t very clear to me. Thanks for the clarification and sorry for the inconvenience.

Comment 7 by f...@opera.com, Dec 15 2017

No problem.

Sign in to add a comment