Bug 1248985 - Fix Spelling Error in nsAppShell.mm draft
authorKirk Steuber <ksteuber@mozilla.com>
Wed, 17 Feb 2016 07:09:39 -0800
changeset 331557 7d085c252a36dd7fe05d1452fae8619fa14da0f5
parent 331237 6ea654cad929c9bedd8a4161a182b6189fbeae6a
child 514411 fbf3820d37f8a9fc8d978f76c6bdc46708f91ea3
push id11015
push userksteuber@mozilla.com
push dateWed, 17 Feb 2016 16:31:11 +0000
bugs1248985
milestone47.0a1
Bug 1248985 - Fix Spelling Error in nsAppShell.mm MozReview-Commit-ID: LqJrA0UOUfi
widget/cocoa/nsAppShell.mm
--- a/widget/cocoa/nsAppShell.mm
+++ b/widget/cocoa/nsAppShell.mm
@@ -359,17 +359,17 @@ nsAppShell::ProcessGeckoEvents(void* aIn
     self->mRunningEventLoop = false;
 
     // The run loop may be sleeping -- [NSRunLoop runMode:...]
     // won't return until it's given a reason to wake up.  Awaken it by
     // posting a bogus event.  There's no need to make the event
     // presentable.
     //
     // But _don't_ set windowNumber to '-1' -- that can lead to nasty
-    // wierdness like bmo bug 397039 (a crash in [NSApp sendEvent:] on one of
+    // weirdness like bmo bug 397039 (a crash in [NSApp sendEvent:] on one of
     // these fake events, because the -1 has gotten changed into the number
     // of an actual NSWindow object, and that NSWindow object has just been
     // destroyed).  Setting windowNumber to '0' seems to work fine -- this
     // seems to prevent the OS from ever trying to associate our bogus event
     // with a particular NSWindow object.
     [NSApp postEvent:[NSEvent otherEventWithType:NSApplicationDefined
                                         location:NSMakePoint(0,0)
                                    modifierFlags:0