[NSApplication sharedApplication] call is no longer needed in platformInitializeWebProcess as [NSApplication _accessibilityInitialize] will call [NSApplication sharedApplication].
Created attachment 355912 [details] Patch
Comment on attachment 355912 [details] Patch r=me
Comment on attachment 355912 [details] Patch Clearing flags on attachment: 355912 Committed r238681: <https://trac.webkit.org/changeset/238681>
All reviewed patches have been landed. Closing bug.
<rdar://problem/46349668>
Comment on attachment 355912 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=355912&action=review > Source/WebKit/WebProcess/cocoa/WebProcessCocoa.mm:187 > // Currently, it is also needed to allocate and initialize an NSApplication object. The patch should have removed this comment, too. It now makes no sense!
Comment on attachment 355912 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=355912&action=review >> Source/WebKit/WebProcess/cocoa/WebProcessCocoa.mm:187 >> // Currently, it is also needed to allocate and initialize an NSApplication object. > > The patch should have removed this comment, too. It now makes no sense! I think the statement still makes sense as [NSApplication _accessibilityInitialize] allocates and initializes an NSApplication object before doing the accessibility initialization. This patch only removes the double call to [NSApplication sharedApplication], not the dependency of initializing an NSApplication object.