Bug 415208 - [WebClient] Check client for events/properties order
Summary: [WebClient] Check client for events/properties order
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 412517 414915
Blocks:
  Show dependency tree
 
Reported: 2013-08-16 04:19 EDT by Ivan Furnadjiev CLA
Modified: 2013-09-04 03:50 EDT (History)
0 users

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 Ivan Furnadjiev CLA 2013-08-16 04:19:11 EDT 
With the operation handlers in place we will process the operations in the order they appear in the protocol message. We have to ensure that this order is correctly set by the client. For example the Text widget should set the "text" before "selectionStart" and "selectionLength" properties (maybe rename to "selection" only) if they are set in two different set operation. In case of a same set operation the correct order is handled by the server. Same for MouseDown/MouseUp (KeyDown/KeyUp??!!) and Selection events for different controls.
Comment 1 Ivan Furnadjiev CLA 2013-08-16 06:13:38 EDT 
Another example: set shell "mode" before "bounds".