Bug 411897 - Fire events in protocol order
Summary: Fire events in protocol order
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 2.2   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 411484
  Show dependency tree
 
Reported: 2013-06-28 11:45 EDT by Ralf Sternberg CLA
Modified: 2013-06-28 14:01 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 Ralf Sternberg CLA 2013-06-28 11:45:45 EDT 
Currently, the order in which events are fired is based on a predefined list of event types (EventTypes.EVENT_ORDER). This does not always reflect the order in which events actually occurred.

For example, FocusOut events are fired before Modify, but it's possible to have a modification and a focus out for the same text field in the same message.

We should fire events in the exact order they appear in the protocol message.