Bug 487372

Summary: Save cookies
Product: [Plasma] plasmashell Reporter: JustDj <fly03043090>
Component: Web Browser widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: 4wy78uwh, kde, nate
Priority: NOR    
Version First Reported In: 5.27.11   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=500752
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description JustDj 2024-05-22 16:01:57 UTC 
SUMMARY
I would like to see a feature for saving cookies in the org.kde.plasma.webbrowser widget. Why is this important? Currently, most services require authorization, which is reset upon restarting plasmashell. This necessitates re-entering login credentials and two-factor authentication each time, making it significantly more time-consuming to navigate websites than using a regular browser.

STEPS TO REPRODUCE
1. Login to any site through org.kde.plasma.webbrowser widget
2. Restart plasmashell or reboot
3. Cookie cleared

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Comment 1 Roke Julian Lockhart Beedell 2024-11-09 18:45:00 UTC 
(In reply to JustDj from comment #0)
I'd like them stored in KWallet, too. I believe that Chromium already does this.
Comment 2 he.si 2025-02-16 16:22:48 UTC 
I would also like to see this feature. I run a number of self-hosted services on localhost, and accessing them from the widget is annoying, since cookies get cleared on every logout. Locally run services often need login credentials for their web UIs. As a result this widget is far less useful than it potentially could be.
Comment 3 Roke Julian Lockhart Beedell 2025-02-16 17:26:58 UTC 
(In reply to he.si from comment #2)  
Perhaps, instead of directly embedding QtWebEngine, this would be more feasible if we embeeded Falkon like a KPart?
Comment 4 Roke Julian Lockhart Beedell 2025-02-16 17:27:15 UTC 
(In reply to Roke Julian Lockhart Beedell from comment #3)  
*embedded, oops
Comment 5 Roke Julian Lockhart Beedell 2025-03-18 15:29:58 UTC 
(In reply to JustDj from comment #0)  
As in https://bugs.kde.org/show_bug.cgi?id=482273#c1:  
> Why has this been triaged as affecting 5.27.11, when the reporter reproduces with 6.0.0?