RESOLVED WORKSFORME 169484
Uncaught Exception: null is not an object (evaluating 'this.treeOutline.isXMLMimeType')
https://bugs.webkit.org/show_bug.cgi?id=169484
Summary Uncaught Exception: null is not an object (evaluating 'this.treeOutline.isXML...
Devin Rousso
Reported 2017-03-10 14:28:40 PST
------- Inspected URL: https://webkit.org/ Loading completed: true Frontend User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/604.1.10+ (KHTML, like Gecko) Dispatch Source: Protocol Command Response Protocol Command Response: {"result":{"nodeId":218},"id":105} Protocol Command Request: {"id":105,"method":"DOM.setNodeName","params":{"nodeId":131,"name":"h3"}} Uncaught Exceptions: - null is not an object (evaluating 'this.treeOutline.isXMLMimeType') (at DOMTreeElement.js:1322:76) _nodeTitleInfo @ DOMTreeElement.js:1322:76 updateTitle @ DOMTreeElement.js:1162:55 _updateModifiedNodes @ DOMTreeUpdater.js:123:42 _updateModifiedNodes @ DOMTreeOutline.js:470:59 changeTagNameCallback @ DOMTreeElement.js:1096:45 ? @ DOMNode.js:806:31 _dispatchResponseToCallback @ Connection.js:146:27 _dispatchResponse @ Connection.js:116:45 dispatch @ Connection.js:69:35 dispatch @ InspectorBackend.js:154:49 dispatchNextQueuedMessageFromBackend @ MessageDispatcher.js:42:34 Additional Details: cause --> An uncaught exception was thrown while dispatching response callback for command DOM.setNodeName. ------- * STEPS TO REPRODUCE 1. Go to <https://webkit.org> 2. Open WebInspector 3. Enter "Inspect Element" mode 4. Select the element with the text "WebKit for Web Developers" 5. Change the type of that node (which should be <h2>) to a different type (such as <h3>)
Attachments
Blaze Burg
Comment 1 2017-03-10 14:35:02 PST
While the bug makes me sad, I am impressed at the details we were able to auto generate!
Blaze Burg
Comment 2 2017-10-13 15:45:42 PDT
Devin, I can't reproduce this. How did you change the tag name? I tried Edit as HTML and nothing bad happened.
Devin Rousso
Comment 3 2017-10-13 16:09:21 PDT
(In reply to Brian Burg from comment #2) > Devin, I can't reproduce this. How did you change the tag name? I tried Edit > as HTML and nothing bad happened. Double click on the tag name in the DOM tree. I just tried it again, and I am not seeing this exception.
Note You need to log in before you can comment on or make changes to this bug.