Fix logging of sticky scrolling tree nodes
https://bugs.webkit.org/show_bug.cgi?id=133670

Reviewed by Sam Weinig.

Source/WebCore:

ScrollingStateStickyNode::dumpProperties() dumped stickyBoxRect() twice and
didn't dump constrainingRectAtLastLayout(), so fix that.

* page/scrolling/ScrollingStateStickyNode.cpp:
(WebCore::ScrollingStateStickyNode::dumpProperties):

LayoutTests:

Rebaselined.

* platform/mac-wk2/tiled-drawing/scrolling/frames/coordinated-frame-expected.txt:
* platform/mac-wk2/tiled-drawing/scrolling/frames/coordinated-frame-in-fixed-expected.txt:
* platform/mac-wk2/tiled-drawing/scrolling/sticky/negative-scroll-offset-expected.txt:
* platform/mac-wk2/tiled-drawing/scrolling/sticky/sticky-horizontal-expected.txt:
* platform/mac-wk2/tiled-drawing/scrolling/sticky/sticky-vertical-expected.txt:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@169745 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[iOS WebKit2] Stay in "memory pressure" mode until told otherwise.
<https://webkit.org/b/133671>

When we receive the first memory pressure signal, flip the flag in
MemoryPressureHandler so that isUnderMemoryPressure() returns true
from then on, until the system tells us pressure levels are back
to normal.

The hold-off mechanism is disabled for iOS, that wasn't actually
needed in the first place, since the system is not going to spam
you with tons of notifications.

Also propagate the "critical" flag all the way from the system
to the pressure handler. Note that we don't actually do anything
differently based on the flag yet.

Reviewed by Sam Weinig.

* platform/MemoryPressureHandler.cpp:
(WebCore::MemoryPressureHandler::respondToMemoryPressure):
* platform/MemoryPressureHandler.h:
(WebCore::MemoryPressureHandler::setUnderMemoryPressure):
* platform/cocoa/MemoryPressureHandlerCocoa.mm:
(WebCore::MemoryPressureHandler::install):
(WebCore::MemoryPressureHandler::respondToMemoryPressure):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@169746 268f45cc-cd09-0410-ab3c-d52691b4dbfc