Bug 272040 - when pressing return key in a html form text input field the cursor steps down two lines
Summary: when pressing return key in a html form text input field the cursor steps dow...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwebkitpart
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.1
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 272039 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-30 10:45 UTC by Martin Steigerwald
Modified: 2011-06-25 05:33 UTC (History)
2 users (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 Martin Steigerwald 2011-04-30 10:45:36 UTC
Version:           unspecified
OS:                Linux

When pressing return in a html form text input field the cursor steps down two
lines instead of one.

Like this.

Reproducible: Sometimes

Steps to Reproduce:
Enter some text like this.

Actual Results:  
Line one

Line two: with an empty line in there should shouldn't be there.

Expected Results:  
Line one
Line two: with an empty line in there should shouldn't be there.

Cause I just pressed return *once*.

I am using KDE 4.6.2 from Debian Experimental and Qt 4.7.2 from Debian
Unstable.

I first noticed it in rekonq, but then it also happened in Konqueror two. Maybe it happens in Konqueror only after I have started rekonq once. Cause before that it worked okay.

Thus see also and probably mark this one as duplicate of

Bug 272039 - when pressing return key in a html form text input field the cursor steps down two lines
Comment 1 Dawit Alemayehu 2011-05-17 00:35:52 UTC
*** Bug 272039 has been marked as a duplicate of this bug. ***
Comment 2 Dawit Alemayehu 2011-05-17 00:38:15 UTC
There is no reason to open two tickets. Opening a ticket against kdewebkit is
sufficient since both reKonq and konqueror use that. Anyhow, this is most
definitely upstream QtWebKit issue and not something we can do nothing about.
It also seems to be a known issue. See the first item in the weekly checklist
at

https://lists.webkit.org/pipermail/webkit-qt/2011-May/001525.html

So that the issue won't fall through the cracks a new ticket has been opened
upstream. See http://webkit.org/b/60929.