Closed
Bug 1733463
Opened 3 years ago
Closed 3 years ago
"origin" property of "Runtime.executionContextCreated" events contain URL instead of window origin
Categories
(Remote Protocol :: CDP, defect, P2)
Remote Protocol
CDP
Tracking
(firefox94 fixed)
RESOLVED
FIXED
94 Branch
| Tracking | Status | |
|---|---|---|
| firefox94 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [bidi-m2-mvp])
Attachments
(1 file)
As noticed while working on bug 1601245 the origin property of the Runtime.executionContextCreated event contains the URL of the loading/loaded page, but not the actual origin, which would just be the protocol and domain.
It's blocking my work on bug 1601245 because in case of Fission the origin property is currently null for newly opened frames. By using window.origin it can be fixed.
Adding triage flag to consider adding it to the m2 milestone.
|
Assignee | |
Comment 1•3 years ago
|
||
Depends on D127242
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/05ff9c0ed3a7 [remote] Use "window.origin" for context's origin in "Runtime.executionContextCreated". r=webdriver-reviewers,jdescottes
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox94:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
|
|
Assignee | |
Updated•3 years ago
|
Points: --- → 2
Priority: -- → P2
Whiteboard: [webdriver:triage] → [bidi-m2-mvp]
You need to log in
before you can comment on or make changes to this bug.
Description
•