Open
Bug 1453891
Opened 6 years ago
Updated 2 years ago
Captive portal service never signals "clear" on Android
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox61 | --- | affected |
People
(Reporter: bagder, Unassigned)
Details
(Whiteboard: [necko-triaged])
CP is not active on Android (since it is handled by the OS itself) and thus it never sends the "clear" signal and internal code that assumes one will malfunction (see example Bug 1452616). We could either use the Android check as signal and then send the ordinary CP clear message, or we might even use working HTTPS to any source as a clue that CP is fine. To avoid us having to add specific knowledge to code paths about it being Android or not.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•