The captive portal error page is an alternate UI that is shown for cert errors. If the portal login page itself causes a cert error, this means the user can't add an exception and login, making the network unusable unless they use an alternate browser to log in. We should expose the cert info/exception UI in the captive portal error page or never show the captive portal error page in the captive portal tab. I'd go with the former because it's easier to implement and also does not force the user to use our flow to open the login page.
Bug 1613477 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
[edited] The "advanced" section in the captive portal error page currently looks like it's missing information, and the "accept risk and continue" button doesn't seem to do anything.