Summary: | remember data submitted into forms | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Silver Salonen <silver.salonen> |
Component: | kdewebkit | Assignee: | 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
this looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=219649 Andrea can you decide? I meant just ordinary forms' history feature. In my rekonq it doesn't work currently. Should it? does konqueror do this? yes it does. It even has an "advanced" option for it: Konqueror settings: Web Browsing -> "AutoCompletion for forms". Ah, understood. It has not been implemented (yet) in kdewebkit. It has to be reported upstream ok then, assigning to the kdewebkit product Andrea: I hope you don't mind I removed you from the assigned field :-P 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 I wonder how has Chrome implemented forms' history. And has the restriction really changed so much since KHTML? How are these things with Webkit2? |