DevTools: remove BreakpointsSidebarPaneBase and breakpointsList.css

third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css

Index: third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css
diff --git a/third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css b/third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css
index fe842e2a1f060d094b178b865b972984c38080bd..a94eb2491bc76dc69e659fd3bc8f0e3bef5af5fb 100644
--- a/third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css
+++ b/third_party/WebKit/Source/devtools/front_end/sources/eventListenerBreakpoints.css
@@ -28,15 +28,6 @@
     display: none;
 }
 
-.breakpoint-hit {
-    background-color: rgb(255, 255, 194);

[dgozman, 2017/05/31 17:36:33]

Why is this not needed anymore?

[luoe, 2017/05/31 18:22:37]

breakpoint-hit-marker is the only element that actually needs the
background-color.  The breakpoint-hit element's bounding box (outlined in red in
the link) is always contained inside the marker: http://imgur.com/a/ixHyp

Since this actually falls outside of this CL's scope, I can undo this change.

-}
-
-:host-context(.-theme-with-dark-background) .breakpoint-hit {
-    background-color: hsl(46, 98%, 22%);
-    color: #ccc;
-}
-
 .breakpoint-hit .breakpoint-hit-marker {
     background-color: rgb(255, 255, 194);
     height: 18px;
@@ -46,3 +37,8 @@
     right: -4px;
     z-index: -1;
 }
+
+:host-context(.-theme-with-dark-background) .breakpoint-hit .breakpoint-hit-marker {
+    background-color: hsl(46, 98%, 22%);
+    color: #ccc;
+}