DOMException in inspectorActor.querySelector

RESOLVED DUPLICATE of bug 962647

Status

RESOLVED DUPLICATE of bug 962647
5 years ago
2 months ago

People

(Reporter: paul, Assigned: paul)

Tracking

Trunk
x86
All

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

5 years ago
Once connected to the message app, searching for "#messages-input" remove the red halo (so the node is found), but the node is not selected in the markup view.

adb logcat tells me:

I/Gecko   ( 6048): console.error:
I/Gecko   ( 6048): DOMException
I/Gecko   ( 6048):   - prototype DOMExceptionPrototype
I/Gecko   ( 6048):     - ABORT_ERR = 20
I/Gecko   ( 6048):     - DATA_CLONE_ERR = 25
I/Gecko   ( 6048):     - DOMSTRING_SIZE_ERR = 2
I/Gecko   ( 6048):     - HIERARCHY_REQUEST_ERR = 3
I/Gecko   ( 6048):     - INDEX_SIZE_ERR = 1
I/Gecko   ( 6048):     - INUSE_ATTRIBUTE_ERR = 10
I/Gecko   ( 6048):     - INVALID_ACCESS_ERR = 15
I/Gecko   ( 6048):     - INVALID_CHARACTER_ERR = 5
I/Gecko   ( 6048):     - INVALID_MODIFICATION_ERR = 13
I/Gecko   ( 6048):     - INVALID_NODE_TYPE_ERR = 24
I/Gecko   ( 6048):     - INVALID_STATE_ERR = 11
I/Gecko   ( 6048):     - NAMESPACE_ERR = 14
I/Gecko   ( 6048):     - NETWORK_ERR = 19
I/Gecko   ( 6048):     - NOT_FOUND_ERR = 8
I/Gecko   ( 6048):     - NOT_SUPPORTED_ERR = 9
I/Gecko   ( 6048):     - NO_DATA_ALLOWED_ERR = 6
I/Gecko   ( 6048):     - NO_MODIFICATION_ALLOWED_ERR = 7
I/Gecko   ( 6048):     - QUOTA_EXCEEDED_ERR = 22
I/Gecko   ( 6048):     - SECURITY_ERR = 18
I/Gecko   ( 6048):     - SYNTAX_ERR = 12
I/Gecko   ( 6048):     - TIMEOUT_ERR = 23
I/Gecko   ( 6048):     - TYPE_MISMATCH_ERR = 17
I/Gecko   ( 6048):     - URL_MISMATCH_ERR = 21
I/Gecko   ( 6048):     - VALIDATION_ERR = 16
I/Gecko   ( 6048):     - WRONG_DOCUMENT_ERR = 4
I/Gecko   ( 6048):     - code = 12
I/Gecko   ( 6048):     - columnNumber = 0
I/Gecko   ( 6048):     - data = null
I/Gecko   ( 6048):     - filename = resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/inspector.js
I/Gecko   ( 6048):     - inner = null
I/Gecko   ( 6048):     - lineNumber = 1413
I/Gecko   ( 6048):     - location = {"language":2,"languageNa

(it stops here, logcat trunks the output)
(Assignee)

Updated

5 years ago
Assignee: nobody → paul
(Assignee)

Updated

5 years ago
Blocks: 893669
(Assignee)

Comment 1

5 years ago
I don't get the error message anymore, but there's a very weird bug here:

First, searching for "#messages-input" doesn't appear to fail, but nothing is selected in the markup view

Picking a node doesn't appear to work correctly: node is highlighted (red rectangle), but nothing is selected in the markupview.

Also, browsing the markup view down to #message-edit-form exposes some weird behavior. I don't think the right elements are highlighted. The markup view looks out of sync. In this screenshot for example: http://i.imgur.com/3k9II1X.png , clicking on the empty line will highlight the message input form.
(In reply to Paul Rouget [:paul] from comment #1)
> I don't get the error message anymore, but there's a very weird bug here:
> 
> First, searching for "#messages-input" doesn't appear to fail, but nothing
> is selected in the markup view

bug 962647
The DOMException you're seeing is cause by the selector-search but isn't the root cause of the nodes not appearing in the markup-view. 
What's happening here is that when you first type `#`, that character gets sent, but doing a doc.qsa('#') throws a DOMException invalid string. It's not a big deal though because right after that, new characters are being typed and eventually, a valid selector is sent, nodes are found, and sent back to the client.

The reason why the markup-view then doesn't update correctly is because the nodes returned aren't attached to the walker's tree. I have a fix for bug 962647 that should resolve this.
I'll dup the bug when I'm sure.
Closing this as dup of 962647.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 962647
Filter on 86b7095e-2bd0-499e-a704-d00f2524aeef / PAUL STOP SETTING QA CONTACT TO THE DEVTOOLS COMPONENT'S WATCHERS EMAIL FOR BUGS YOU FILE :)
QA Contact: developer.tools

Updated

2 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.