Closed Bug 1329546 Opened 4 years ago Closed 4 years ago
Get rid of Captive
Portal Watcher and unify captive portal tests
After bug 1313568 lands, captive portal frontend code and tests will be found in browser/modules as well as browser/base. We should get rid of CaptivePortalWatcher.jsm and move the relevant tests to browser/base/content/test/captivePortal. This means that all captive portal logic will be handled per-window, meaning that the logic/UX around portal detection when there is no browser window open, and automatically showing the portal tab when one is opened, will need to be tweaked. Possible new logic: automatically open captive portal tab in a newly opened browser window, if no other browser window exists at the time of opening (and possibly only if it was opened with Cmd/Ctrl+N, i.e. with no URLs to immediately load).
Taking care of this in bug 1313568.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.