Qualify the generated includes in core (partial)

This CL takes care the dom, editing, events subdirs under core.

BUG=381876

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176068 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Removing using declarations that import names in the C++ Standard library.

This is as per the the coding guidelines for blink, which disallows the
use of "using" declarations of any kind to import names in the C++ Standard
library.

This is in continuation of the CL https://codereview.chromium.org/329183002/
Effected Folders: Source/core/html/

BUG=NONE

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176069 bbb929c8-8fbe-4397-9dbb-9b2b20218538
updateLayerPositionsAfterLayout shouldn't have a RenderGeometryMap

This CL remove the RenderGeometryMap from updateLayerPositionsAfterLayout. The
only remaining use of the geometry map was to compute an argument for
RenderLayerScrollableArea::positionOverflowControls. However, it turns out it
doesn't matter what value we pass to positionOverflowControls at this point. By
removing the RenderGeometryMap, this CL makes updateLayerPositionsAfterLayout
twice as fast.

Historically, the overflow controls were backed by NSViews, which meant they
needed to be positioned in absolute space by the widget tree. Now, however,
they're either drawn by Blink or composited by cc. If the overflow controls
are painted by Blink, we're reposition them immediately before painting. If the
overflow controls are composited, we'll subtract out the offsetFromRoot before
passing the values to cc. In both cases, it doesn't matter care what value we
pass here.

We should eventually remove this function call from this codepath. This isn't
the correct codepath in which to position the overflow controls. However, we
can save that work for a future CL.

R=esprehn@chromium.org
BUG=383636,382548

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176070 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Report correct touch hit rects when
RuntimeEnabledFeatures::overlayFullscreenVideoEnabled is true and have a touch
handler on the document or body.

We had an optimization in the cc touch hit rect calculation that if there was a
handler on the document or body then we'd short circuit the computation and
report a single rect at the root layer covering the whole page. Now when making
an HTML5 video element fullscreen with this flag turned on the
RenderLayerCompositor removes the root cc::layer and reattaches the video layer
causing the compositor to think that there are no handlers registered.


BUG=372314

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176071 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use ScriptWrappable::init less

Use ScriptWrappable::init less, it is only needed for most derived classes usually, but these SVG classes are not exposed as JS type.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176073 bbb929c8-8fbe-4397-9dbb-9b2b20218538