Closed
Bug 785180
Opened 12 years ago
Closed 12 years ago
Let the highlighter select non-element nodes
Categories
(DevTools :: Inspector, defect, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dcamp, Assigned: paul)
Details
(Whiteboard: [check-if-fixed-because-toolbox])
Attachments
(1 file)
|
22.26 KB,
patch
|
Details | Diff | Splinter Review |
Right now the highlighter is picky about what it will accept as the current selection. This means the markup panel sometimes has a different idea of what the currently-selected node is (because it needs to let people select text/comment nodes, for example). If we want the inspector to share a single concept of a selected node, we need to allow that node to be any node on the page.
|
Assignee | |
Comment 1•12 years ago
|
||
|
|
Assignee | |
Comment 2•12 years ago
|
||
The highlighter, the breadcrumbs, the inspector and the markup panel should all share the same selection. A node could be anything, and maybe it could be null.
|
|
Assignee | |
Updated•12 years ago
|
Assignee: nobody → paul
|
|
Assignee | |
Updated•12 years ago
|
Whiteboard: [to-close-once-toolbox-has-landed]
|
|
Assignee | |
Updated•12 years ago
|
Whiteboard: [to-close-once-toolbox-has-landed] → [check-if-fixed-because-toolbox]
|
|
Assignee | |
Comment 4•12 years ago
|
||
Fixed by the new selection mechanism. Bug triage, filter on PINKISBEAUTIFUL
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•