Closed Bug 1579052 Opened 2 years ago Closed 2 years ago

Markup view uses currentTarget walker, instead of nodeFront walker

Categories

(DevTools :: Inspector, task, P1)

task

Tracking

(firefox71 fixed)

RESOLVED FIXED
Firefox 71
Tracking Status
firefox71 --- fixed

People

(Reporter: ystartsev, Assigned: ystartsev)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission dt-fission-m1)

Attachments

(1 file)

At the moment, in the markup view we use the inspector.walker walker, which is the currentTarget walker. However we use this for accessing information about nodes which might be remote. We should instead use the nodeFront's walkerFront

Priority: -- → P1
Summary: Use relative walker for markup view → Markup view uses currentTarget walker, instead of nodeFront walker
Blocks: 1579053
Attachment #9090694 - Attachment description: Bug 1579052 - use relative nodeFront walker in markup view; r=pbro → Bug 1579052 - use relative nodeFront walker in markup view; r=rcaliman
Assignee: nobody → ystartsev
Status: NEW → ASSIGNED
Whiteboard: dt-fission
Attachment #9090694 - Attachment description: Bug 1579052 - use relative nodeFront walker in markup view; r=rcaliman → Bug 1579052 - use relative nodeFront walker in markup view; r=pbro
Pushed by ystartsev@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0eb8f05cf5b6
use relative nodeFront walker in markup view; r=rcaliman
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71
Whiteboard: dt-fission → dt-fission dt-fission-m1
You need to log in before you can comment on or make changes to this bug.