Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365864 - [Table] Activating cell editor causes unnecessary secondary request
Summary: [Table] Activating cell editor causes unnecessary secondary request
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 05:24 EST by Rüdiger Herrmann CLA
Modified: 2012-04-24 05:29 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-12-07 05:24:13 EST 
When tabbing through a table with cell editors, each tab key causes a request that creates and positions a cell editor on the target cell.
With the attached example project I observed, that there is an extra request sent after the reqeust which activated the cell editor:
requestCounter=xyz
uiRoot=w1
w1.cursorLocation.x=584
w1.cursorLocation.y=167
w1.focusControl=w68
w2.activeControl	=w68
w68.selectionLength=0
w68.selectionStart=0

"w86" references the cell editor (a text widget in this case)
I think this request is unnecessary. Moreover I am wondering why the selection of the text widget is reset even though visually, all text stays selected.
Comment 1 Tim Buschtoens CLA 2012-01-09 04:44:56 EST 
A wild guess, but perhaps the widget has a focus listener that adds the event before the selection is set by the server?. This should be prevented by the "org.eclipse.swt.EventUtil.setSuspended( true );" however.
Comment 2 Ivan Furnadjiev CLA 2012-03-22 09:18:45 EDT 
After the client-side Text widget re-factorings (bug 371192) I can't reproduce it anymore. Please reopen if the issue persists.
Comment 3 Ivan Furnadjiev CLA 2012-04-24 05:29:05 EDT 
Just for the record - the actual problem has been fixed in this Bug 377406.