Closed Bug 339353 Opened 19 years ago Closed 1 year ago

Mac nsAppShell::ProcessNextNativeEvent implementations should always process one event

Categories

(Core Graveyard :: Widget: Mac, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mark, Assigned: mark)

References

Details

Bug 338249 comment 17 (Cocoa) Bug 339051 comment 7, bug 339051 comment 9 (Carbon) After making sure that ScheduleNativeEventCallback is working properly in all cases (doubt raised by bug 337550 comment 24), the Mac AppShell implementations should be changed to function like the implementations on other platforms, and only process a single native event during each call, even when aMayWait is true. nsBaseAppShell manages the native loop, so the extra loop in the nsAppShell classes is redundant and is only being left in place: - to ensure bug 337550 is fully resolved and - to isolate any perf regressions as we move away from system-managed loops If all goes according to plan, at the very latest, this should be done within two weeks.
No longer depends on: 338249
Depends on: 338249
I'm satisfied. I'll do this.
Product: Core → Core Graveyard
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.