Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 285249 - [Text] Editing with 'delete'-key sometimes doesn't work in IE
Summary: [Text] Editing with 'delete'-key sometimes doesn't work in IE
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.3   Edit
Hardware: PC Windows All
: P3 normal (vote)
Target Milestone: 1.3 M2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://www.eclipse.org/newsportal/art...
Whiteboard: qx-close
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-31 03:32 EDT by Asen Draganov CLA
Modified: 2010-02-22 06:22 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Asen Draganov CLA 2009-07-31 03:32:10 EDT
Build ID: 20090619-0625

Steps To Reproduce:
1. Open the RAP Controls Demo in IE (my version is IE8)
2. Go to Focus Tab. 
3. Click with mouse in the Text field next to the Check Box
4. Press the 'delete' key: it works as expected in my browser.
5. Now click with mouse in the next Text field (it is a multiline field).
6. Press the 'delete' key: no character will be deleted. This is an unexpected behavior.
7. Click a second time in the same field and then press again the 'delete' key: now it works fine.
8. Leave the last text field with 'tab' key pressing.
9. Now repeat again steps 5-6: the same unexpected  behavior.

More information:
This bug appears only in IE. It could be reproduced, according to me, in different scenarios, but only in layouts that contain at least two editable text fields.
P.S. There is a thread in the RAP Newsgroup, called "setFocus widget in IE8 vs. Mozilla" (http://www.eclipse.org/newsportal/article.php?id=7162&group=eclipse.technology.rap#7162), that indicates this issue for the first time. Please, look at the complaint there for completeness.
Comment 1 Asen Draganov CLA 2009-08-27 09:50:47 EDT
This bug appeared after patching the qx-library with patch, proposed by Qooxdoo  to fix bug 264195 (see Comment #3). After revert to the previous state (before the mentioned patch), the bug explained here doesn't appear. Bug 264195 also is not experienced any more (tested with scenarios explained in the bug). Tested with IE 8, FF 3.5.2, Safari 4, Chrome 2.
Comment 2 Asen Draganov CLA 2009-08-28 08:24:32 EDT
Corresponding Qooxdoo bug has been opened: http://bugzilla.qooxdoo.org/show_bug.cgi?id=2734
Comment 3 Asen Draganov CLA 2009-09-01 11:20:55 EDT
Qooxdoo reverted their bug fix, mentioned in comment #1. I have tested it once again in RAP. It looks OK - this bug doesn't appear, bug 264195 also.
Comment 4 Ivan Furnadjiev CLA 2009-09-02 06:55:46 EDT
Fixed by removing the patch for bug 264195.
Comment 5 Sudheer CLA 2010-02-22 02:17:29 EST
(In reply to comment #4)
> Fixed by removing the patch for bug 264195.

This problem is not only with 'Del' button, but with ctrl+v too, copy some text and click on any text field and then press ctrl+v, notice that nothing appeares in the selected text field. Now click again and then press ctrl+v, now the content from clip board appears in the text field.  All text fields in dailog need two clicks, this a big usability issue. Strangely this problem doesn't happen with FF. Is there any work around for this issue? I am using rap 1.2.
Comment 6 Rüdiger Herrmann CLA 2010-02-22 04:00:43 EST
(In reply to comment #5)
> (In reply to comment #4)
> > Fixed by removing the patch for bug 264195.
> [ ... ]
> Strangely this problem doesn't
> happen with FF. Is there any work around for this issue? I am using rap 1.2.
Does the problem also appear with 1.3M5 or with CVS HEAD?
Comment 7 Sudheer CLA 2010-02-22 05:16:52 EST
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > Fixed by removing the patch for bug 264195.
> > [ ... ]
> > Strangely this problem doesn't
> > happen with FF. Is there any work around for this issue? I am using rap 1.2.
> Does the problem also appear with 1.3M5 or with CVS HEAD?

I didnot check with 1.3M5, I am using rap 1.2, what I want is a work around to solve this issue.  setting focus on one of the text field doesn't solve the problem.  Can I do something as a workaround till I move to 1.3?
Comment 8 Rüdiger Herrmann CLA 2010-02-22 06:22:00 EST
(In reply to comment #7)
> [ ... ]
> I didnot check with 1.3M5, I am using rap 1.2, what I want is a work around to
> solve this issue.  setting focus on one of the text field doesn't solve the
> problem.  Can I do something as a workaround till I move to 1.3?
I am afraid there is no workaround - at least I am not aware of.