Suppress -Wpartial-availability warnings that arise from NSWindowDelegate methods only available on…

ui/views/cocoa/bridged_native_widget_unittest.mm

Index: ui/views/cocoa/bridged_native_widget_unittest.mm
diff --git a/ui/views/cocoa/bridged_native_widget_unittest.mm b/ui/views/cocoa/bridged_native_widget_unittest.mm
index 3cf3dc2ec9e755f440312d4299d86314fe842bcf..1bf91db51893f24909fac3312e6076ca4ccd7d9c 100644
--- a/ui/views/cocoa/bridged_native_widget_unittest.mm
+++ b/ui/views/cocoa/bridged_native_widget_unittest.mm
@@ -490,7 +490,8 @@ TEST_F(BridgedNativeWidgetSimulateFullscreenTest, FailToEnterAndExit) {
   // is no equivalent notification for failure). Called via id so that this
   // compiles on 10.6.
   id window_delegate = [window delegate];
-  [window_delegate windowDidFailToEnterFullScreen:window];
+  [window_delegate performSelector:@selector(windowDidFailToEnterFullScreen:)
+                        withObject:window];

[Nico, 2015/05/12 22:29:38]

why this change?

[erikchen, 2015/05/12 22:41:39]

The method windowDidFailToEnterFullScreen: is only available on 10.7+ and is
defined in a protocol. Switching to a perform-selector suppresses the warning.
If you prefer, I could use clang preprocessor directives.

[Nico, 2015/05/12 22:45:00]

Huh, if you declare it it should be possible to call it, no?

[erikchen, 2015/05/12 23:49:19]

Just to confirm: You would prefer it if I cast window_delegate to
ViewsNSWindowDelegate, add redeclarations of the relevant methods to
ViewsNSWindowDelegate, and add VIEWS_EXPORT to ViewsNSWindowDelegate?

[Nico, 2015/05/13 00:18:30]

Are you sure that you need the cast and the export? Does just adding the
declaration there suffice?

[erikchen, 2015/05/13 00:26:21]

Ah, they are not necessary. 

One caveat: This class currently doesn't include "views_nswindow_delegate.h",
which is where the redeclaration would happen. I can add an include, but there
will be no visibility as to why the include is necessary. I guess I could wrap
the include the ifdefs? It's not very clear that we're using the redeclarations
in views_nswindow_delegate.h to suppress a warning on this "id window_delegate".

[erikchen, 2015/05/13 16:56:43]

Hm. Removing NSWindowDelegateFullScreenAdditions from sdk_forward_declarations.h
prevents this code from compiling against 10.6 SDK. That...doesn't make sense to
me. I don't understand why defining a protocol that is never used removes the
compile failure. The code was introduced here:
https://codereview.chromium.org/665823002/

The name of the protocol itself doesn't matter - I changed it to "sdfasdf" and
its existence still removed the compile failure.

I think that switching to performSelector: and removing this "magic" protocol
from sdk_forward_declarations.h is the best solution. wdyt?

   EXPECT_FALSE(bridge()->target_fullscreen_state());
 
   // Now perform a successful fullscreen operation.
@@ -508,7 +509,8 @@ TEST_F(BridgedNativeWidgetSimulateFullscreenTest, FailToEnterAndExit) {
 
   // On a failure, Cocoa sends a failure message, but then just dumps the window
   // out of fullscreen anyway (in that order).
-  [window_delegate windowDidFailToExitFullScreen:window];
+  [window_delegate performSelector:@selector(windowDidFailToExitFullScreen:)
+                        withObject:window];
   EXPECT_FALSE(bridge()->target_fullscreen_state());
   [center postNotificationName:NSWindowDidExitFullScreenNotification
                         object:window];