Open Bug 179995 Opened 23 years ago Updated 3 years ago

cleanup: Remove nsAppShell mouse/key event ordering code

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
All
defect

Tracking

()

People

(Reporter: jesup, Unassigned)

Details

(Keywords: memory-footprint)

From bug 157144: Actually this fix does *not* change the way the WIN32 GDI works. It does not attempt to fix it. It doesn't invert the order of any messages or similar nastiness, which is what is currently going on in nsAppShell by the way. In fact, we will probably be able to remove the code in nsAppShell which pulls out the mouse and key events ahead of other events once this patch goes in. It also allows embedded apps to run using unmodified msg processing loops. The WIN32 message processing does not work exactly the same way as other platforms. Thats to be expected. The Widget and Gfx modules are littered with code where we have identified native platform behavior discrepancies and make them compatible with the XP code's expectations. This is just happens to be another instance of that.
this could use a real owner
Keywords: footprint
QA Contact: rakeshmishra → trix
.
Assignee: joki → saari
QA Contact: trix → ian
Assignee: saari → nobody
QA Contact: ian → events
Component: Event Handling → User events and focus handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.