2051397 - Restore speculative connection for the Urlbar actor message path

Status: RESOLVED DUPLICATE of bug 2051959

(Firefox :: Address Bar, task)

Description

[Dão Gottwald [:dao]]

UrlbarParentController.speculativeConnect() pre-warms a TCP/TLS connection to the heuristic result's search engine or autofill URL while the user types, to cut first-navigation latency. It reads this.input / this.browserWindow and runs from receiveResults().

As of the Phase 4 IPC Urlbar work (Bug 2050399), when a <moz-urlbar> runs on the actor message path -- browser.urlbar.ipc.chromeMessagePassing on, or a content-process urlbar such as about:newtab -- the parent controller has no in-process input or window, so receiveResults() skips the onFirstResult/speculativeConnect block and the speculative connection never happens.

This is a performance-only gap: nothing breaks, and the default in-process chrome path (direct, pref off) is unaffected.

Restoring it cross-process needs the connection context derived parent-side from the actor (e.g. the JSWindowActor's browsingContext) instead of a DOM browserWindow, or routing the request over the actor.