[oilpan]: Don't sweep while in safepoint.

Related to the test failures seen in the worker-data-view-test.html test I think this will fix the issue. Basically postpone the sweep until after we have left the safepoint. I am still testing/trying to reproduce.

R=ager@chromium.org, erik.corry@gmail.com, haraken@chromium.org, oilpan-reviews@chromium.org, sof@opera.com, tkent@chromium.org, vegorov@chromium.org, zerny@chromium.org
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177124 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add [TypeChecking=Interface] on various methods in Document.idl

This adds type checks on some Node arguments in the generated bindings
code, and lets us drop the corresponding manual null checks and exception
throwing code in the implementations.

The type of exception thrown changes from DOMException (NOT_SUPPORTED_ERR)
to TypeError as a side-effect. This matches the Web IDL specification.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177125 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Drop [TypeChecking=Nullable]; deduce from attribute type instead

[TypeChecking=Nullable] on a nullable attribute meant that the C++ getter
wasn't called with a "bool& isNull" argument, instead the C++ value in a
boolean context was used to determine nullness.

This was only used for attributes where the C++ value was a pointer, and
made perfect sense for such attributes. So much sense, in fact, that it
makes sense to let that be the default behavior for such attributes.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177126 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[DevTools] Improve emulation experience when responsive design mode is unavailable.

When emulation is unavailable (on device), only show the message about it.
When emulation is available, but without responsive design mode, move
toggle button to the OverridesView.

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177127 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove position: sticky

We would eventually like to implement position: sticky, but the current
implementation isn't designed in a way that integrates well with the existing
scrolling and compositing system. For example, position: sticky relies upon
updateLayerPositionsAfterDocumentScroll to function correctly, but that
function has no other purpose and can otherwise be removed. Similarly,
position: sticky doesn't work at all with composited overflow scrolling, which
is now the default mechanism for driving scrolling in the engine.

Once we've got our scrolling and compositing house in order, we should return
to position: sticky and implement the feature in a way that integrates well
with the rest of the engine. For now, however, this CL removes our current
implementation so we can focus on improving our implementation of the scrolling
features we've already shipped.

R=eseidel@chromium.org, esprehn@chromium.org
BUG=389638, 231752

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177128 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove wrong commented out code from RenderLayer::updateLayerPositionsAfterScroll

This comment is about ASSERTing the consistency of state that no long exists.
Also, remove m_canSkipRepaintRectsUpdateOnScroll because it's just
renderer()->isTableCell().

R=esprehn@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177129 bbb929c8-8fbe-4397-9dbb-9b2b20218538
The length of a TextIterator containing replaced element is at least 1

When a TextIterator is created for a range that contains a replaced
element then one ',' (comma) will surely be emitted. This way the
length of the created TextIterator will be at least 1. In spite of
this, the WebCore::PlainTextRange::createRangeFor method assumes that
the length of the iterator only can be one if that one character is a
newline. The patch fixes this wrong assumption.

R=tkent@chromium.org
BUG=385630

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177130 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Unflaky test inspector/timeline/timeline-network-received-data.html

It was a race between the event arrived into timeline and the script that was evaluated in the page.

BUG=316150

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

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