Closed Bug 11938 Opened 25 years ago Closed 24 years ago

MapNotify lossage in xlib mainloop

Categories

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

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: blizzard, Assigned: blizzard)

Details

The MapNotify event is required in the xlib mainloop to notify the widget code
that a window has been mapped.  Without this information you can't safely
use XSetInputFocus() on a window.  The mIsMapped member variable in the nsWidget
object holds this state information.

Also, the tight loop in HandleConfigureNotifyEvent that will get the last
ConfigureEvent will drop MapNotify events on the floor without passing Go or
collecting $200.  This is because it will use a XCheckWindowEvent() with a
StructureNotifyMask and not handle any MapNotify events.  Badness.  Must fix.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Figured out how to work around this.  Also, not needing to track MapNotify
anymore.  Closing this chapter.
Keywords: verifyme
Please ignore the spam.  Changing address.
Assignee: blizzard → blizzard
Status: RESOLVED → NEW
bustage from my reassign
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Updating QA Contact.
QA Contact: ckritzer → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
QA contact updated
QA Contact: gerardok → madhur
VERIFIED ON BUILD 2001-07-30-08-TRUNK
Status: RESOLVED → VERIFIED
Keywords: verifyme
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.