Bug 467991 - Inline QtWebview-based captive portal view, so you don't need to open the default browser for this
Summary: Inline QtWebview-based captive portal view, so you don't need to open the def...
Status: REPORTED
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 5.27.3
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-31 07:15 UTC by Henning
Modified: 2023-04-04 21:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henning 2023-03-31 07:15:30 UTC
SUMMARY
Android has this integrated Captive portal viewing browser, allowing you to accept the public wifis TOS or enter a code etc. then giving you internet Access. Currently on Linux the only way is through your default Browser, and especially Firefox doesnt really handle that well, it uses their own Servers only and seems not to work when hardened.

EXPECTED RESULT
A button opening something like the Webbrowser applet, that opens a small browser page with a user defined HTTP URL like http://httpforever.com that gets then redirected to the portal. The tools for that should be already present and a button either appearing if a connected wifi doesnt have internet access, or always, next to the airplane for example, could be really useful.
Comment 1 Nate Graham 2023-04-04 18:34:47 UTC
Out of curiosity, what's wrong with using the default browser for this? You said that Firefox was "hardened"; what does that mean exactly?
Comment 2 Henning 2023-04-04 21:49:52 UTC
By default firefox searches a lot for captive portals. It uses their own domain, which you can change, but the defaults are pretty much IP tracking if you dont change that.

I dont know why but even after I reenabled that, the arkenfox presets (with very soft mods) still make captive portals not work. Also because in general the "HTTPS-only" policy seems to kill it, idk actually.

having a seperate browser dealing with that, and potentially being whitelisted by the VPN so you dont have to turn it off, and also only connecting if you want to. As QTWebengine is integrated, this would be the alternative to androids captive portal checker. 

And you dont need internet only through the browser. You need it also for other applications like updating, which has no GUI at all. You may not have a browser open. Using QTWebengine could be way better, as you could add a button to the Network manager applet.

I dont know how placing the qtwebengine window would work, left of the window would work but only on the standard KDE layout. Above would look weird possibly.