Widget::ShouldUseNativeFrame is now meaningful on Linux.

ui/views/widget/widget.cc

Index: ui/views/widget/widget.cc
diff --git a/ui/views/widget/widget.cc b/ui/views/widget/widget.cc
index 9c7c1ec5d764d44fa905a7233779af976982e096..61a20fed0bced33aee820abb161e02ec8c91a025 100644
--- a/ui/views/widget/widget.cc
+++ b/ui/views/widget/widget.cc
@@ -870,6 +870,10 @@ bool Widget::ShouldUseNativeFrame() const {
   return native_widget_->ShouldUseNativeFrame();
 }
 
+bool Widget::ShouldWindowContentsBeTransparent() const {
+  return native_widget_->ShouldWindowContentsBeTransparent();

[Matt Giuca, 2014/02/07 09:13:11]

This is the only potential behavioural change on Windows. Note that the code
path from Tab, TabStrip and Toolbar no longer goes through
Widget::ShouldUseNativeFrame, which means it doesn't honour frame_type_ (if it
is non-default). But that is never set on browser windows, to my knowledge, so I
believe this does not change the behaviour.

+}
+
 void Widget::DebugToggleFrameType() {
   if (frame_type_ == FRAME_TYPE_DEFAULT) {
     frame_type_ = ShouldUseNativeFrame() ? FRAME_TYPE_FORCE_CUSTOM :