New issue
Advanced search Search tips

Issue 757776 link

Starred by 1 user
Status: Closed
Owner:
einbinder@chromium.org
Closed: Dec 10
Cc:
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Show namespace of an element somewhere

Reported by jeromin....@gmail.com, Aug 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3188.4 Safari/537.36

Steps to reproduce the problem:
jQuery does not support SVG elements and therefor can 
generate elements with the wrong namespace. 
But even with vanilla js this bite me sometimes.

If you generate the wrong namespace an element is shown in the tree, but not rendered.
See https://jsfiddle.net/7n0hvgg5/ for an clickable example.

What is the expected behavior?
The error should be visible somehow.

What went wrong?
In the example I generated an SVGTextElement and a "HTMLTextElement". 
An HTMLTextElement does not exists and no HTML element is rendered in an SVG context.
But in the devTools this problem is not easy visible.

Perhaps devTools can show the $0.namespaceURI of the active element somewhere.

Did this work before? No 

Chrome version: 62.0.3188.4  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:

Comment 1 by kkaluri@chromium.org, Aug 23 2017

Cc: kkaluri@chromium.org
Labels: Needs-Triage-M62 Needs-Feedback
Tested this issue on Windows 10 with chrome #62.0.3188.4 and also firefox

Observations:
1. In chrome browser,  didn't observe any errors in the console.
2. In Firefox browser, observed following error "Use of getAttributeNode() is deprecated. Use getAttribute() instead."

Attaching the screenshot for reference.

jeromin.holger@ could you confirm the error displayed in the FireFox, should be  displayed in the chrome browser? Please let us know your observations.

Thank You...
757776-FF.PNG
79.9 KB View Download
757776-Chrome.PNG
103 KB View Download

Comment 2 by woxxom@gmail.com, Aug 23 2017 

#1, this is a feature request for devtools UI, not a bug per se.

Currently the only visual way to discover such incorrectly namespaced elements in devtools UI is to open Properties subpanel (in the toolbar with Styles, Computed, Event listeners) where such invalid elements will have HTMLUnknownElement inheritance.

Comment 3 by jeromin....@gmail.com, Aug 23 2017 

#2 thanks for your comment.

I did not know the properties subpanel in details.

After thinking about a bit, we perhaps need no display of namespace but a console warning like: 
"Element 'text' is not rendered because elements with namespace http://www.w3.org/1999/xhtml are not supported in this subtree"
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 23 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by pnangunoori@chromium.org, Aug 24 2017

Labels: -Type-Bug Type-Feature
Status: Untriaged (was: Unconfirmed)
Assuming this as feature request, changing the status to untriage, so that the issue would be addressed.

Thank you.

Comment 6 by pfeldman@chromium.org, Aug 28 2017

Owner: einbinder@chromium.org
Status: Assigned (was: Untriaged)

Comment 7 by einbinder@chromium.org, Dec 10

Status: Closed (was: Assigned)
This is a valid feature request, but it is pretty low priority considering how rarely it is a problem for people and you can find the information through the console.
►

Sign in to add a comment