Bug 223371 - Implement undo feature for text boxes
Summary: Implement undo feature for text boxes
Status: RESOLVED DUPLICATE of bug 223370
Alias: None
Product: kwebkitpart
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 05:31 UTC by Jonathan Thomas
Modified: 2010-01-23 17:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Thomas 2010-01-19 05:31:19 UTC
Version:           svn 1073627 (using Devel)
Installed from:    Compiled sources

The undo feature really needs to be implemented. If you accidentally erase something (or bug 223370), it's very nice to be able to get it back. Arora has this feature, so I don't think it's a limitation of QtWebKit.
Comment 1 Dawit Alemayehu 2010-01-19 05:50:35 UTC
On Monday 18 January 2010 23:31:19 Jonathan Thomas wrote:
> https://bugs.kde.org/show_bug.cgi?id=223371
> 
>            Summary: Implement undo feature for text boxes
>            Product: webkitkde
>            Version: unspecified
>           Platform: Compiled Sources
>         OS/Version: unspecified
>             Status: NEW
>           Severity: wishlist
>           Priority: NOR
>          Component: general
>         AssignedTo: webkit-devel@kde.org
>         ReportedBy: echidnaman@kubuntu.org
> 
> 
> Version:           svn 1073627 (using Devel)
> Installed from:    Compiled sources
> 
> The undo feature really needs to be implemented. If you accidentally erase
> something (or bug 223370), it's very nice to be able to get it back. Arora
>  has this feature, so I don't think it's a limitation of QtWebKit.

The undo/redo features are completely implemented in the upstream (QtWebKit) 
widgets themselves. Neither kdelibs/kdewebkit nor the webkit part have 
anything to do with it. As such, this issue is something that is likely caused 
by the 223370 bug you reported and fixing it might automatically resolve this 
issue...
Comment 2 Urs Wolfer 2010-01-23 17:02:21 UTC
If you still can reproduce this after testing with a more recent version (see bug 223370), please reopen.

*** This bug has been marked as a duplicate of bug 223370 ***