SuggestionPicker min width is two pixels wider than it should be
https://bugs.webkit.org/show_bug.cgi?id=97645

Reviewed by Kent Tamura.

Suggestion picker's minimum width should match inputWidth.

No new tests. Added later in Bug 97645.

* Resources/pagepopups/suggestionPicker.js:
(SuggestionPicker.prototype._measureMaxContentWidth):
(SuggestionPicker.prototype._fixWindowSize): We shouldn't be adding ListBorder to inputWidth.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@129622 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: compare objects counted by the memory instrumentation with those allocated in the heap
https://bugs.webkit.org/show_bug.cgi?id=97641

Reviewed by Pavel Feldman.

Source/WebCore:

Added code that allows to check if all objects counted by the memory instrumentation
were allocated by the underlying memory allocator. It requires support
from the memory allocator. The code works only if the set of allocated objects
is not empty and should only be used for debugging purposes.

* inspector/InspectorClient.h:
(InspectorClient):
(WebCore::InspectorClient::getAllocatedObjects):
* inspector/InspectorController.cpp:
(WebCore::InspectorController::InspectorController):
* inspector/InspectorMemoryAgent.cpp:
(WebCore::collectDomTreeInfo):
(WebCore::InspectorMemoryAgent::getProcessMemoryDistribution):
(WebCore::InspectorMemoryAgent::InspectorMemoryAgent):
* inspector/InspectorMemoryAgent.h:
(WebCore):
(WebCore::InspectorMemoryAgent::create):
(InspectorMemoryAgent):
* inspector/MemoryInstrumentationImpl.cpp:
(WebCore::MemoryInstrumentationImpl::MemoryInstrumentationImpl):
(WebCore::MemoryInstrumentationImpl::countObjectSize):
(WebCore):
(WebCore::MemoryInstrumentationImpl::checkCountedObject):
* inspector/MemoryInstrumentationImpl.h:
(MemoryInstrumentationImpl):

Source/WebKit/chromium:

Added code that allows to check if all objects counted by the memory instrumentation
were allocated by the underlying memory allocator. It requires support
from the memory allocator this is why WebDevToolsAgentClient API is extended with a
method that allows to visit pointers to all live heap objects if the memory allocator
supports that.

The code should only be used for debugging purposes.

* public/WebDevToolsAgentClient.h:
(AllocatedObjectVisitor):
(WebKit::WebDevToolsAgentClient::AllocatedObjectVisitor::~AllocatedObjectVisitor):
(WebKit::WebDevToolsAgentClient::visitAllocatedObjects):
(WebDevToolsAgentClient):
* src/InspectorClientImpl.cpp:
(WebKit):
(WebKit::InspectorClientImpl::getAllocatedObjects):
* src/InspectorClientImpl.h:
(InspectorClientImpl):
* src/WebDevToolsAgentImpl.cpp:
(WebKit):
(WebKit::WebDevToolsAgentImpl::getAllocatedObjects):
* src/WebDevToolsAgentImpl.h:
(WebDevToolsAgentImpl):

Source/WTF:

Added a method for checking if reported object was actually allocated in the heap.

* wtf/MemoryInstrumentation.h:
(MemoryInstrumentation):
(WTF::MemoryInstrumentation::addObjectImpl):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@129623 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: [chromium] add a test for inspector overlay update frequency
https://bugs.webkit.org/show_bug.cgi?id=97567

Reviewed by Yury Semikhatsky.

Added a test for reasonable number of frames caused by inspector page overlay.
We expect changes in nodes being inspected to cause an update, while just idling
should not cause large numbers of unexpected updates.

* src/js/Tests.js:
(.TestSuite.prototype.testPageOverlayUpdate):
(.TestSuite.prototype.testPageOverlayUpdate.innerAddRecord):
(.TestSuite.prototype.testPageOverlayUpdate.populatePage):
(.TestSuite.prototype.testPageOverlayUpdate.step2):
(.TestSuite.prototype.testPageOverlayUpdate.step4):
(.TestSuite.prototype.testPageOverlayUpdate.step5):

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