Open Bug 1579007 Opened 5 years ago Updated 10 months ago

Revisit Captive Portal UI logic and improve tests

Categories

(Core :: Networking, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: nhnt11, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 obsolete file)

Presently, when there is no active browser window when a portal is detected, we trigger a recheck when a window is opened/gets focused. Then, if the recheck completes quickly and we're still captive, we open a captive portal tab.

This is kinda useless because once we're captive, CaptiveDetect.jsm polls until we're free, and the recheck doesn't actually do anything. We should remove this logic and simply open a captive portal tab immediately.

I'm also going to take the opportunity to improve the tests and write a fake portal sjs script and a simple login page and use those to simulate a captive portal environment.

The test should help catch stuff like bug 1578633.

See Also: → 1578633

The tests fail as expected without the patch from bug 1578633.

Priority: P3 → P5
Attachment #9090657 - Attachment is obsolete: true

The work I was doing last year was abandoned.

Assignee: nhnt11 → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
Component: General → Networking
Product: Firefox → Core
Severity: S3 → N/A
Priority: P5 → P3
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: