Closed Bug 1891028 Opened 1 year ago Closed 19 days ago

Opening a new browser window should potentially wait for the "browser-delayed-startup-finished" notification

Categories

(Remote Protocol :: Agent, enhancement, P3)

enhancement
Points:
2

Tracking

(firefox148 fixed)

RESOLVED FIXED
148 Branch
Tracking Status
firefox148 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [webdriver:m18])

Attachments

(1 file)

Right now we only wait for this notification for the initial window, but not when using any WebDriver BiDi or Marionette commands to open a new context. As such our commands may return too early and causing issues. See bug 1837949 comment 5.

I would wait with any work here until bug 1837949 has been fixed to not influence test scenarios and make it harder to see.

Summary: Opening a tab or window should potentiall wait for the "browser-delayed-startup-finished" notification → Opening a tab or window should potentially wait for the "browser-delayed-startup-finished" notification
Priority: -- → P2
Whiteboard: [webdriver:backlog]
Whiteboard: [webdriver:backlog] → [webdriver:m14]
Points: --- → 2
Duplicate of this bug: 1507276
Whiteboard: [webdriver:m14] → [webdriver:m15]
Whiteboard: [webdriver:m15] → [webdriver:m16]
Whiteboard: [webdriver:m16] → [webdriver:m17]
Priority: P2 → P3

Actually this might cause issues when interacting with a window that is not ready yet and certain components like safe browsing, or the blocklist not yet working. See bug 1975796 comment 5 as example.

I'll try to find some time this week to come up with a patch.

No longer depends on: 1837949
Whiteboard: [webdriver:m17] → [webdriver:m18]

It would be good to only have to modify the TabManager and WindowManager and not as well Marionette. As such I've checked if the patch on bug 1795841 now works and indeed with the newer Linux versions it seems to be fine now. So lets wait until this landed.

Depends on: 1795841

Actually this observer notification is only sent when opening a new browser window but not for new tabs. So we are not blocked on a solution for bug 1795841.

No longer depends on: 1795841
Summary: Opening a tab or window should potentially wait for the "browser-delayed-startup-finished" notification → Opening a new browser window should potentially wait for the "browser-delayed-startup-finished" notification
Assignee: nobody → hskupin
Blocks: 1791951
Status: NEW → ASSIGNED
Pushed by hskupin@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b20d5047f418 https://hg.mozilla.org/integration/autoland/rev/de0ac808a5aa [remote] Wait for "browser-delayed-startup-finished" when opening a new browser window. r=Sasha
Pushed by agoloman@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/be62884d661c https://hg.mozilla.org/integration/autoland/rev/0d0cb00a3838 Revert "Bug 1891028 - [remote] Wait for "browser-delayed-startup-finished" when opening a new browser window. r=Sasha" for causing wpt failures.

Backed out for causing wpt failures.

Flags: needinfo?(hskupin)
Regressions: 2007666
No longer regressions: 2007666

All these failures are on Android where we actually do not have to wait for this observer notification because only a single window exists anyway and we check the status early when Marionette / Remote Agent starts-up. Also there is no gBrowserInit object available for Thunderbird and SeaMonkey so we should limit the check for window.gBrowserInit.delayedStartupFinished to just Firefox for now.

Flags: needinfo?(hskupin)
Pushed by hskupin@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/7a41387427e9 https://hg.mozilla.org/integration/autoland/rev/bbfd8b52707a [remote] Wait for "browser-delayed-startup-finished" when opening a new browser window. r=Sasha
Status: ASSIGNED → RESOLVED
Closed: 19 days ago
Resolution: --- → FIXED
Target Milestone: --- → 148 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: