Add PPB_Fullscreen;0.5.

webkit/plugins/ppapi/ppapi_webplugin_impl.cc

Index: webkit/plugins/ppapi/ppapi_webplugin_impl.cc
===================================================================
--- webkit/plugins/ppapi/ppapi_webplugin_impl.cc	(revision 99979)
+++ webkit/plugins/ppapi/ppapi_webplugin_impl.cc	(working copy)
@@ -118,7 +118,8 @@
 }
 
 void WebPluginImpl::paint(WebCanvas* canvas, const WebRect& rect) {
-  if (!instance_->IsFullscreenOrPending())
+  if (!instance_->IsFullscreenOrPending() &&
+      !instance_->IsFullscreenOrPending_Dev())
     instance_->Paint(canvas, plugin_rect_, rect);

[piman, 2011/09/09 01:33:44]

Maybe I'm confused about the implementation, but shouldn't Paint be called here
if in the "new" fullscreen mode? If not, when/how does Paint get called? Same
with ViewChanged and HandleInputEvent below.

[jeremya, 2011/09/09 17:45:35]

I think you're right -- in the old fullscreen mode, the widget did its own
painting, event handling, etc.

[polina, 2011/09/26 21:57:00]

I did not have the full background on the differences between the old and the
new implementation. The code should make more sense now.

 }
 
@@ -128,7 +129,8 @@
     const WebVector<WebRect>& cut_outs_rects,
     bool is_visible) {
   plugin_rect_ = window_rect;
-  if (!instance_->IsFullscreenOrPending())
+  if (!instance_->IsFullscreenOrPending() &&
+      !instance_->IsFullscreenOrPending_Dev())
     instance_->ViewChanged(plugin_rect_, clip_rect);
 }
 
@@ -145,7 +147,8 @@
 
 bool WebPluginImpl::handleInputEvent(const WebKit::WebInputEvent& event,
                                      WebKit::WebCursorInfo& cursor_info) {
-  if (instance_->IsFullscreenOrPending())
+  if (instance_->IsFullscreenOrPending() ||
+      instance_->IsFullscreenOrPending_Dev())
     return false;
   return instance_->HandleInputEvent(event, &cursor_info);
 }