Bug 226473

Summary: remember data submitted into forms
Product: [Unmaintained] kdelibs Reporter: Silver Salonen <silver.salonen>
Component: kdewebkitAssignee: webkit-devel
Status: RESOLVED UPSTREAM    
Severity: wishlist CC: adawit, pano_90
Priority: NOR    
Version: SVN   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Silver Salonen 2010-02-12 08:51:23 UTC
Version:           0.3.90 (using KDE 4.4.0)
Installed from:    openSUSE RPMs

One essential thing in browser is to remember data submitted into forms. Currently Rekonq doesn't seem to do that.
Comment 1 Panagiotis Papadopoulos 2010-02-16 18:46:03 UTC
this looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=219649

Andrea can you decide?
Comment 2 Silver Salonen 2010-02-17 08:12:19 UTC
I meant just ordinary forms' history feature. In my rekonq it doesn't work currently. Should it?
Comment 3 Andrea Diamantini 2010-03-20 22:21:59 UTC
does konqueror do this?
Comment 4 Panagiotis Papadopoulos 2010-03-20 22:28:28 UTC
yes it does. It even has an "advanced" option for it:

Konqueror settings:

Web Browsing -> "AutoCompletion for forms".
Comment 5 Andrea Diamantini 2010-03-26 17:07:11 UTC
Ah, understood. It has not been implemented (yet) in kdewebkit. It has to be reported upstream
Comment 6 Panagiotis Papadopoulos 2010-03-26 17:17:05 UTC
ok then, assigning to the kdewebkit product
Comment 7 Panagiotis Papadopoulos 2010-03-26 17:22:02 UTC
Andrea: I hope you don't mind I removed you from the assigned field :-P
Comment 8 Dawit Alemayehu 2010-03-26 19:10:28 UTC
Form completion support is something that has to be implemented upstream in QtWebKit. Since WebKit does not allow access to its user input widgets, there is no easy way to provide form completion support without resorting to a major hack. Note that this issue does not only affect kdewebkit based browsers such as reKonq, but also pure qtwebkit based ones such as arora ; so the best thing to do is fix the problem at the source. As such, a ticket has been opened upstream for this issue. See...

https://bugs.webkit.org/show_bug.cgi?id=36668
http://websvn.kde.org/trunk/KDE/kdelibs/kdewebkit/ISSUES?view=markup
Comment 9 Silver Salonen 2010-04-12 08:21:34 UTC
I wonder how has Chrome implemented forms' history. And has the restriction really changed so much since KHTML?

How are these things with Webkit2?