Closed
Bug 1644695
Opened 4 years ago
Closed 4 years ago
DOM.describeNode for a frame doesn't return its own id but the parent id
Categories
(Remote Protocol :: CDP, defect, P1)
Remote Protocol
CDP
Tracking
(firefox79 fixed)
RESOLVED
FIXED
Firefox 79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [puppeteer-beta-reserve])
Attachments
(1 file)
The broken behavior for this API actually blocks my work on bug 1637640. If there is a frameset and DOM.describeNode()
is called on the frame element, CDP returns the frame's id and not the one from the parent.
Assignee | ||
Updated•4 years ago
|
Summary: Caling DOM.describeNode for a frame doesn't return its own id but the parent id → DOM.describeNode for a frame doesn't return its own id but the parent id
Assignee | ||
Comment 1•4 years ago
|
||
Depends on D79450
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0704e56577ad [remote] Return the frameId of the frame when DOM.describeNode is called with a frame element. r=remote-protocol-reviewers,maja_zf
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 79
Updated•3 years ago
|
Component: CDP: DOM → CDP
You need to log in
before you can comment on or make changes to this bug.
Description
•