Closed Bug 892562 Opened 11 years ago Closed 11 years ago

[inspector] when the "inspect" button is toggled on, hovering the nodes in the markup view should highlight the elements in the browser

Categories

(DevTools :: Inspector, defect, P2)

21 Branch
x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: julienw, Unassigned)

References

Details

Attachments

(1 file)

STR: * open a webpage * open the dev tools * open the inspector tab * toggle the inspect button if it's not done already * hover the nodes in the "HTML" view Expected: * the associated elements should be highlighted in the browser view
Summary: [inspector] when the "inspect" button is toggled on, hovering the nodes should highlight the elements in the browser → [inspector] when the "inspect" button is toggled on, hovering the nodes in the markup view should highlight the elements in the browser
Assignee: nobody → paul
Attached patch Patch v1 (deleted) — Splinter Review
Per paul's request
I won't have time to work on that.
Assignee: paul → nobody
This bug becomes irrelevant when bug 916443 lands as this bug changes the whole highlighter logic in that we will only highlight on markup-view hover.
An addition to this would be the ability of the document to scroll the relevant area into view when hovering over its corresponding node in the inspector, or (if that behaviour is too shocking) only scrolling the relevant document area into view when a node in the inspector has been clicked. At the moment the dashed selector highlighter just sort of plants itself against the boundaries of the viewport when the area in the document is out of view, which is what all inspector tools do at the moment, but shouldn't really. Not to mention, the reverse does happen: when hovering over sections in the document, the corresponding inspector nodes are scrolled into view. I figure if when searching for nodes in the search bar can cause the document to scroll the found section into view, then it shouldn't be too far off from that.
I think this bug has been made obsolete because it just works now. Dane, you should file a new bug :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: