Roll up patch for running layout tests under Aura.

public/platform/default/WebThemeEngine.h

Index: public/platform/default/WebThemeEngine.h
diff --git a/public/platform/default/WebThemeEngine.h b/public/platform/default/WebThemeEngine.h
index f84f292d7f878e30ee3498089c8d976c15e8044b..f78147a72194a65bee318c84948dfd35637779a7 100644
--- a/public/platform/default/WebThemeEngine.h
+++ b/public/platform/default/WebThemeEngine.h
@@ -71,11 +71,16 @@ public:
         StateHover,
         StateNormal,
         StatePressed,
+        StateFocused,
+        StateReadonly,
+        StateHot,
     };
 
     // Extra parameters for drawing the PartScrollbarHorizontalTrack and
     // PartScrollbarVerticalTrack.
     struct ScrollbarTrackExtraParams {
+        bool isBack; // Whether this is the 'back' part or the 'forward' part.

[jamesr, 2013/11/06 21:54:09]

in other parts of theming code, this is handled by having different Parts for
the forward and backward parts of the track. not sure if that'd be more useful
here than what you're doing

[Dirk Pranke, 2013/11/06 22:29:11]

Yup. I was trying to avoid changes to the WebThemeEngine that would impact the
other implementations. Arguably, since no other theme actually cares about
whether the part is a forward or backward part, we shouldn't either and we don't
need this, but we wouldn't match the existing baselines that way, so I'd prefer
to revisit this later.

+
         // The bounds of the entire track, as opposed to the part being painted.
         int trackX;
         int trackY;
@@ -105,7 +110,9 @@ public:
         bool hasBorderRadius;
         int arrowX;
         int arrowY;
+        int arrowHeight;
         WebColor backgroundColor;
+        bool fillContentArea;
     };
 
     // Extra parameters for PartSliderTrack and PartSliderThumb