Closed Bug 1932162 Opened 1 year ago Closed 1 year ago

Expose initiatorType in parent channel and expose fetch destination in LoadInfo

Categories

(Core :: Networking, task, P2)

task
Points:
2

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox134 --- fixed

People

(Reporter: jdescottes, Assigned: jdescottes)

References

Details

(Whiteboard: [webdriver:m14][necko-triaged])

Attachments

(2 files)

To help with Webdriver BiDi, we want to sync initiatorType between the child channel and the parent channel and expose the fetch destination directly on nsILoadInfo.idl.

Component: WebDriver BiDi → Networking
Product: Remote Protocol → Core

Depends on D229378

Expose a getter on nsILoadInfo to easily retrieve the fetch destination as a string
This avoids duplicating the mapping logic in JS for webdriver bidi

This changeset synchronizes the initiatorType from the child channel to the parent channel in asyncOpen.
It also removes noscript from initiatorType in nsITimedChannel

Severity: -- → N/A
Priority: -- → P2
Whiteboard: [necko-triaged]
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/67593cbd0172 Set the initiatorType in HttpChannelParent and expose to scripts r=necko-reviewers,valentin https://hg.mozilla.org/integration/autoland/rev/21a1acee6519 Expose fetch destination on nsILoadInfo r=necko-reviewers,valentin

(we are setting points for our own tracking, hopefully it doesn't mess up with Necko's triage, if that's an issue let us know we can track it elsewhere!)

Points: --- → 2
Whiteboard: [necko-triaged] → [webdriver:m14][necko-triaged]
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: