[BlackBerry] Pass http headers to loader in download request
https://bugs.webkit.org/show_bug.cgi?id=87449

Reviewed by Rob Buis.

PR# 149283

This is to support byte-range download and we could pass http headers like
"Range" in download request to loader.

Reviewed internally by Lyon Chen.

* Api/WebPage.cpp:
(BlackBerry::WebKit::WebPage::download):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118526 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: put paint and compositing timeline events in a new category of their own
https://bugs.webkit.org/show_bug.cgi?id=86852

Reviewed by Pavel Feldman.

- add forth timeline category, "Painting"; make it light-purple;
- assign paint and compositing events to Painting category;

* WebCore.gypi: added timelineBarLightPurple.png;
* inspector/front-end/Images/timelineBarLightPurple.png: Added.
* inspector/front-end/Images/timelineCheckmarks.png: added light-purple icon;
* inspector/front-end/Images/timelineDots.png: ditto.
* inspector/front-end/TimelineOverviewPane.js:
(WebInspector.TimelineCategoryStrips.prototype.update.appendRecord): do not merge bars in same raw if these are from different categories;
(WebInspector.TimelineCategoryStrips.prototype.update):
* inspector/front-end/TimelinePresentationModel.js:
(WebInspector.TimelinePresentationModel.categories):
(WebInspector.TimelinePresentationModel.recordStyle):
* inspector/front-end/WebKit.qrc: added timelineBarLightPurple.png;
* inspector/front-end/timelinePanel.css: added styles for painting category;
(.timeline-category-statusbar-item.timeline-category-painting .timeline-category-checkbox):
(.timeline-category-painting .timeline-graph-bar):
(.popover .timeline-painting):
(.timeline-category-scripting .timeline-tree-icon):
(.timeline-category-rendering .timeline-tree-icon):
(.timeline-category-painting .timeline-tree-icon):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118527 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: Speed up edges iteration in heap profiler
https://bugs.webkit.org/show_bug.cgi?id=87286

Add an extra node to nodes array that points to the end of edges array.
It allows to eliminate a check for the last node in iteration code.

Patch by Alexei Filippov <alexeif@chromium.org> on 2012-05-25
Reviewed by Yury Semikhatsky.

Source/WebCore:

* inspector/front-end/HeapSnapshot.js:
(WebInspector.HeapSnapshotNode.prototype._edgeIndexesStart):
(WebInspector.HeapSnapshotNode.prototype._edgeIndexesEnd):
(WebInspector.HeapSnapshotNodeIterator):
(WebInspector.HeapSnapshot.prototype._buildRetainers):
(WebInspector.HeapSnapshot.prototype._bfs):
(WebInspector.HeapSnapshot.prototype._buildAggregates):
(WebInspector.HeapSnapshot.prototype._buildPostOrderIndex):
(WebInspector.HeapSnapshot.prototype._buildDominatorTree):
(WebInspector.HeapSnapshot.prototype._markQueriableHeapObjects):

LayoutTests:

* inspector/profiler/heap-snapshot-test.js:
(initialize_HeapSnapshotTest.InspectorTest.createHeapSnapshotMockObject):
(initialize_HeapSnapshotTest.InspectorTest._postprocessHeapSnapshotMock):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118528 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: speed-up HeapSnapshot._bfs method.
https://bugs.webkit.org/show_bug.cgi?id=87502

It had containmentEdges.length call in the loop that forced deoptimization.

Reviewed by Yury Semikhatsky.

* inspector/front-end/HeapSnapshot.js:
(WebInspector.HeapSnapshot.prototype._calculateObjectToWindowDistance):
(WebInspector.HeapSnapshot.prototype._bfs):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118529 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[BlackBerry] History navigation caused google.com scale not kept
https://bugs.webkit.org/show_bug.cgi?id=87438

Reviewed by Antonio Gomes.
Patch by Jacky Jiang <zhajiang@rim.com>

PR: 159923
For back/forward history navigation, we were trying to keep the values
set by dispatchViewportDataDidChange. However, when we went back from
the previous page, if the current page didn't contain the meta viewport
tag, then those values set by previous page would never be reset.
Although the current page could get correct saved scale when restoring
view state, the scale would still be clamped by zoomToFitScale which
was based on the virtual viewport of the previous page which could make
the scale incorrect.
Since we know the viewport arguments of the current document before
setLoadState on back/forward history navigation, we can reset these
previous values if the document doesn't have viewport arguments during
setLoadState.

* Api/WebPage.cpp:
(BlackBerry::WebKit::WebPagePrivate::setLoadState):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118530 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed; rolling chromium deps.

* DEPS:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118531 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed chromium test expectations update.

* platform/chromium/test_expectations.txt:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118532 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: Clean up Inspector.json after r118367
https://bugs.webkit.org/show_bug.cgi?id=87499

Reviewed by Yury Semikhatsky.

This cleans up the semantic inconsistencies introduced into type/field names r118367.

No new tests, as this is a refactoring.

* inspector/Inspector.json:
* inspector/InspectorCSSAgent.cpp:
(WebCore::InspectorCSSAgent::asInspectorStyleSheet):
(WebCore::InspectorCSSAgent::viaInspectorStyleSheet):
(WebCore::InspectorCSSAgent::detectOrigin):
* inspector/InspectorCSSAgent.h:
(InspectorCSSAgent):
* inspector/InspectorStyleSheet.cpp:
(WebCore::InspectorStyleSheet::create):
(WebCore::InspectorStyleSheet::InspectorStyleSheet):
(WebCore::InspectorStyleSheet::buildObjectForRule):
(WebCore::InspectorStyleSheet::resourceStyleSheetText):
(WebCore::InspectorStyleSheetForInlineStyle::create):
(WebCore::InspectorStyleSheetForInlineStyle::InspectorStyleSheetForInlineStyle):
* inspector/InspectorStyleSheet.h:
(InspectorStyleSheet):
(WebCore::InspectorStyleSheet::canBind):
(InspectorStyleSheetForInlineStyle):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118533 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Remove the Windows platform-specific results for window-domurl-crash.

r115582 changed this test to use Blob instead of WebKitBlobBuilder, so the fact that Windows
doesn't support WebKitBlobBuilder no longer affects this test.

* platform/chromium-win/fast/dom/window-domurl-crash-expected.txt: Removed.
* platform/win/fast/dom/window-domurl-crash-expected.txt: Removed.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118534 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Remove test expectation for video-cookie.html now that the issue
is fixed on the Chromium side.
https://bugs.webkit.org/show_bug.cgi?id=87459

Unreviewed gardening.

* platform/chromium/test_expectations.txt:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118535 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Remove/restore test expectations for html5lib tests.
https://bugs.webkit.org/show_bug.cgi?id=87275

Unreviewed gardening.

* platform/chromium/test_expectations.txt:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118536 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Widen CRASH expectation for visibility-simple-canvas2d-layer.html to include Mac10.6.

Unreviewed gardening.

* platform/chromium/test_expectations.txt:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118537 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: Hangup when continuously changing a css width value in Inspector
https://bugs.webkit.org/show_bug.cgi?id=85802

Reviewed by Vsevolod Vlasov.

Source/WebCore:

An error in the property whitespace prefix detection algorithm would append the previous line trailing whitespace,
thereby enormously increasing the actual prefix during multiple incremental property changes.

* inspector/InspectorStyleSheet.cpp:
(WebCore::InspectorStyle::newLineAndWhitespaceDelimiters):

LayoutTests:

* inspector/styles/styles-formatting-expected.txt:
* inspector/styles/styles-formatting.html:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118538 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Adding Ken Buchanan to committers.py
https://bugs.webkit.org/show_bug.cgi?id=87443

Unreviewed.

Adding self to committers.py as a Committer.


* Scripts/webkitpy/common/config/committers.py:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118539 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Win] fast/events/keydown-leftright-keys.html failing since introduction in r118001
https://bugs.webkit.org/show_bug.cgi?id=87511

Reviewed by Alexey Proskuryakov.

Update the Windows implementation of keyDown to match the Mac one changed in r118001.

* DumpRenderTree/win/EventSender.cpp:
(keyDownCallback):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118540 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Implement LayoutTest's eventSender.beginDragWithFiles interface in windows platform
https://bugs.webkit.org/show_bug.cgi?id=86296

Add more affected tests to the Windows Skipped list.

* platform/win/Skipped:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118541 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Layout root not getting cleared for anonymous renderers geting destroyed
https://bugs.webkit.org/show_bug.cgi?id=84002

Reviewed by Abhishek Arya.

This is a follow-up to r109406, which added a check to clear layout
roots when they point to a renderer that is being destroyed. The
thinking was that layout roots would never be anonymous renderers,
but there are some cases where this is not true (in particular,
generated content containers with overflow clips can be layout roots).

As in r109406, this patch has no layout test. This is because any test
that exercises this behavior is caused by an existing layout bug where
a child is not properly getting layout (or a renderer is getting dirtied
out of order during layout) and will fail multiple ASSERTs:
in particular, ASSERT(!m_layoutRoot->container() || !m_layoutRoot->
container()->needsLayout()) in FrameView::scheduleRelayoutOfSubtree(),
and ASSERT_NOT_REACHED() in RenderObject::clearLayoutRootIfNeeded().
We are preventing those bugs from manifesting as security issues with
this patch.

This also removes an ASSERT from the RenderObject destructor. This is
redundant with the condition in RenderObject::clearLayoutRootIfNeeded()
which is always called in RenderObject::willBeDestroyed(), so the check
is not needed. It had to be removed because it fails when I try to
adjust the ASSERT condition by removing the !node()
check, due to RenderWidget clearing its node() during destruction.

* rendering/RenderObject.cpp:
(WebCore::RenderObject::~RenderObject):
(WebCore::RenderObject::willBeDestroyed):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118542 268f45cc-cd09-0410-ab3c-d52691b4dbfc
New baselines for http://crbug.com/129184

Unreviewed rebaselining.

Patch by Elliot Poger <epoger@chromium.org> on 2012-05-25

* platform/chromium-linux/svg/filters/subRegion-one-effect-expected.png:
* platform/chromium-linux/svg/filters/subRegion-two-effects-expected.png:
* platform/chromium-linux/svg/transforms/svg-css-transforms-expected.png:
* platform/chromium-linux/transforms/svg-vs-css-expected.png:
* platform/chromium-mac/svg/filters/subRegion-one-effect-expected.png:
* platform/chromium-mac/svg/filters/subRegion-two-effects-expected.png:
* platform/chromium-mac/svg/transforms/svg-css-transforms-expected.png:
* platform/chromium-mac/transforms/svg-vs-css-expected.png:
* platform/chromium-win/svg/filters/subRegion-one-effect-expected.png:
* platform/chromium-win/svg/filters/subRegion-two-effects-expected.png:
* platform/chromium-win/svg/transforms/svg-css-transforms-expected.png:
* platform/chromium-win/transforms/svg-vs-css-expected.png:
* platform/efl/svg/filters/subRegion-one-effect-expected.txt: Removed.
* platform/efl/svg/filters/subRegion-two-effects-expected.txt: Removed.
* platform/gtk/svg/filters/subRegion-one-effect-expected.txt: Removed.
* platform/gtk/svg/filters/subRegion-two-effects-expected.txt: Removed.
* platform/mac/svg/filters/subRegion-one-effect-expected.txt: Removed.
* platform/mac/svg/filters/subRegion-two-effects-expected.txt: Removed.
* platform/qt/svg/filters/subRegion-one-effect-expected.txt: Removed.
* platform/qt/svg/filters/subRegion-two-effects-expected.txt: Removed.
* svg/filters/subRegion-one-effect-expected.txt: Added.
* svg/filters/subRegion-two-effects-expected.txt: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118543 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Gtk] Remove configuration options that do not apply anymore
https://bugs.webkit.org/show_bug.cgi?id=87509

Reviewed by Martin Robinson.

Remove configuration options for enabling or disabling HTML5 datagrid,
DOM storage, image resizer API and sandboxed iframe support. These
features were either turned on by default with the feature defines
removed from the code or removed from the source.

* configure.ac:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@118544 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Skip more WebGL tests on Windows.

* platform/win/Skipped:

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