Commit d9cc5d20 authored by abarth@chromium.org's avatar abarth@chromium.org

InspectorOverlay should call layout in the normal way

The InspectorOverlay does a bunch of manual poking and prodding of the layout
state machine. Instead, InspectorOverlay should just use
updateLayoutAndStyleForPainting like the regular engine does.

R=esprehn@chromium.org, pfeldman@chromium.org

Review URL: https://codereview.chromium.org/465033002

git-svn-id: svn://svn.chromium.org/blink/trunk@180114 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent e9349a36
......@@ -378,23 +378,16 @@ bool InspectorOverlay::handleMouseEvent(const PlatformMouseEvent& event)
return false;
EventHandler& eventHandler = toLocalFrame(overlayPage()->mainFrame())->eventHandler();
bool result;
switch (event.type()) {
case PlatformEvent::MouseMoved:
result = eventHandler.handleMouseMoveEvent(event);
break;
return eventHandler.handleMouseMoveEvent(event);
case PlatformEvent::MousePressed:
result = eventHandler.handleMousePressEvent(event);
break;
return eventHandler.handleMousePressEvent(event);
case PlatformEvent::MouseReleased:
result = eventHandler.handleMouseReleaseEvent(event);
break;
return eventHandler.handleMouseReleaseEvent(event);
default:
return false;
}
toLocalFrame(overlayPage()->mainFrame())->document()->updateLayout();
return result;
}
bool InspectorOverlay::handleTouchEvent(const PlatformTouchEvent& event)
......@@ -503,11 +496,8 @@ void InspectorOverlay::update()
drawPausedInDebuggerMessage();
drawViewSize();
// Position DOM elements.
toLocalFrame(overlayPage()->mainFrame())->document()->setNeedsStyleRecalc(SubtreeStyleChange);
toLocalFrame(overlayPage()->mainFrame())->document()->updateLayout();
toLocalFrame(overlayPage()->mainFrame())->view()->updateLayoutAndStyleForPainting();
// Kick paint.
m_client->highlight();
}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment