Closed Bug 1459829 Opened 6 years ago Closed 6 years ago

Clicking on "reveal" from Inspector doesn't move the selection to the corresponding node.

Categories

(DevTools :: Inspector, defect, P2)

Product:
DevTools
Component:
Inspector
Type:
defect

Tracking

(firefox62 affected)

Status:
RESOLVED DUPLICATE of bug 1449959
Tracking Flags:
Tracking Status
firefox62 --- affected

People

(Reporter: Ovidiu, Assigned: jdescottes)

References

Details

[Affected versions]:

Tested on Nightly 62.0a1(2018-05-07)

[Affected platforms]:

Tested on Mac OS X 10.12, Ubuntu 16.04 and Windows 10 

[Steps to reproduce]:

Prerequisites:
 Go to about:config and enable this 2 preferences:

dom.webcomponents.shadowdom.enabled
dom.webcomponents.customelements.enabled (should already be true on Nightly)

 
1. Open Firefox and go to https://juliandescottes.github.io/webcomponents-playground/lazy/
2. Click on "Attach shadow root" button.
3. Open the Inspector
4. Right click on <body> and select "Expand All"
5. Under the <slot id="slot1" name="slot1"> there are 2 <div> elements. 
Hover over both of them and click on "reveal".-----Clicking on reveal will move the selection to the corresponding node.
6. Refresh the web page.
7. Click on "Attach shadow root" button.
8. Expand the <body>
9. Under the <test-component id="component2" background=""> there are 5 <div> elements. 
Hover over both of them and click on "reveal"


[Expected result]:

Clicking on reveal will move the selection to the corresponding node.

[Actual result]:

If you click on reveal the selection is not moved to the corresponding node. 

Note: Please see the video for a better understanding. https://streamable.com/58m77
status-firefox62: --- → affected
Depends on: 1449959
Blocks: devtools-webcomponents-63
Severity: normal → enhancement
Priority: -- → P3
Product: Firefox → DevTools
Just tested this against my WIP patches from Bug 1449959, and it really looks like it's just the issue triggered in a different way because they also solve this Bug.
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Priority: P3 → P2
Should be fixed together with Bug 1449959
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.