[Qt][WK2] Unreviewed gardening, add Qt-WK2 specific expected
file, because this doesn't fail as expected, but passes.

* platform/qt-5.0-wk2/css3/compositing/should-have-compositing-layer-expected.txt: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127265 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: Update $ to alias to querySelector rather than getElementById
https://bugs.webkit.org/show_bug.cgi?id=92648

Reviewed by Yury Semikhatsky.

Source/WebCore:

Completed implementation started by Addy Osmani. Updates $ to alias to querySelector
with more flexible handling of selectors. Also adds a warning about the change (as per Firebug).

* inspector/InjectedScriptSource.js:
(.):

LayoutTests:

* inspector/console/command-line-api-expected.txt:
* inspector/console/command-line-api-inspect.html:
* inspector/console/command-line-api.html:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127266 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[New Multicolumn] Implement unforced breaking in the new column layout.
https://bugs.webkit.org/show_bug.cgi?id=95498

Reviewed by Dan Bernstein.

This patch implements unforced breaking for lines and objects inside columns. Forced breaks are
not yet handled properly and will be covered in a separate patch.

* rendering/LayoutState.cpp:
(WebCore::LayoutState::LayoutState):
Eliminate the flow thread constructor for LayoutState. Flow threads were doing a double push of
layout states, once in RenderFlowThread::layout() and then again in RenderBlock::layout(). This
double push was unnecessary, so I refactored the code to ensure the RenderBlock push does the
right thing for RenderFlowThreads.

(WebCore):
* rendering/LayoutState.h:
(LayoutState):
Eliminate the flow thread constructor for LayoutState.

* rendering/RenderBlock.cpp:
(WebCore::RenderBlock::checkForPaginationLogicalHeightChange):
This function now handles RenderFlowThreads and properly sets a non-zero page height as well
as querying the flow thread to ask if the pagination logical height has changed. The flow thread
has a new member that it sets in layout() so that it can answer this question.

(WebCore::RenderBlock::hasNextPage):
Make sure RenderRegionSets always claim to have a next page when they are the last region, since
we know columns/pages can always generate additional boxes as needed.

* rendering/RenderFlowThread.cpp:
(WebCore::RenderFlowThread::RenderFlowThread):
Add the m_pageLogicalHeightChanged member variable for tracking whether regions changed dimensions,
thus forcing us to repaginate everything.

(WebCore::RenderFlowThread::layout):
Remove the redundant push of layout state now that RenderBlock's covers it.

(WebCore::RenderFlowThread::regionAtBlockOffset):
Always return the last region if it's a set, regardless of the extendLastRegion boolean.
This reflects the fact that the last region set can always generate new page/column boxes.

(WebCore::RenderFlowThread::pageLogicalTopForOffset):
Refactored to call into the region it finds for a given offset, so that the region itself
can answer the question of where the top of the page is. This enables sets to return the top of
specific columns/pages within the set.

(WebCore::RenderFlowThread::pageRemainingLogicalHeightForOffset):
Changed to be written in terms of pageLogicalTop and pageLogicalHeight so that it correctly uses
only the current column/page when determining remaining height.

* rendering/RenderFlowThread.h:
Added pageLogicalHeightChanged() so that RenderBlock can ask the flow thread if its regions changed
dimensions.

* rendering/RenderMultiColumnBlock.cpp:
(WebCore::RenderMultiColumnBlock::checkForPaginationLogicalHeightChange):
Tweaked to no longer turn on pagination, since the RenderMultiColumnFlowThread does that and we
want to avoid a double push of paginated states. Instead it now just sets the column height ahead
of time so that the RenderMultiColumnSets know how big their columns are.

* rendering/RenderMultiColumnSet.cpp:
(WebCore::RenderMultiColumnSet::pageLogicalTopForOffset):
Subclassed to return the top of a specific column.

(WebCore):
* rendering/RenderMultiColumnSet.h:
Add the subclassed method for pageLogicalTopForOffset.
        
* rendering/RenderRegion.cpp:
(WebCore::RenderRegion::pageLogicalTopForOffset):
The code from RenderFlow::pageLogicalTopForOffset moved here. Just returns the top of the flow
thread portion rect in the region (same as before).

(WebCore::RenderRegion::layout):
Changed to check only the page logical width and height, since we only consider a region as
invalidating how you break if there is an actual page height change.

* rendering/RenderRegion.h:
(WebCore::RenderRegion::isRenderRegionSet):
Added an isRenderRegionSet() virtual function so that we can test for sets.

* rendering/RenderRegionSet.h:
(WebCore::RenderRegionSet::isRenderRegionSet):
Subclassed isRenderRegionSet() to return true.

* rendering/RenderView.cpp:
* rendering/RenderView.h:
(LayoutStateMaintainer):
(WebCore::LayoutStateMaintainer::push):
Remove the pushes of LayoutState that were specific to RenderFlowThreads.



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127267 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Qt] ImageDiff output is not in the expected form if image dimensions differ
https://bugs.webkit.org/show_bug.cgi?id=95575

Reviewed by Csaba Osztrogonác.

Output 100% difference in the case of differing image dimensions so
the test harness knows that we won't produce any output further.
This matches the behavior of other ports.

* DumpRenderTree/qt/ImageDiff.cpp:
(main):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127268 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[CSS Regions] It should be possible to specify ::BEFORE/AFTER as regions
https://bugs.webkit.org/show_bug.cgi?id=90079

Patch by Andrei Bucur <abucur@adobe.com> on 2012-08-31
Reviewed by David Hyatt.

Source/WebCore:

The calls for RenderRegion::node() have been replaced with RenderRegion::generatingNode() to allow pseudo-elements to have RenderRegion renderers.
The compare function that establishes the region order was adapted to take into account pseudo-regions.
A renderer for the pseudo-element is now generated if it's a region even though there's no content property specified.

Test: fast/regions/content-flowed-into-pseudo-regions.html

* rendering/RenderFlowThread.cpp:
(WebCore::RenderFlowThread::computeOverflowStateForRegions):
* rendering/RenderNamedFlowThread.cpp:
(WebCore::compareRenderRegions):
* rendering/RenderObjectChildList.cpp:
(WebCore::ensureBeforeAfterContainer):
(WebCore):
(WebCore::RenderObjectChildList::updateBeforeAfterContent):
* rendering/RenderRegion.cpp:
(WebCore::RenderRegion::nodeAtPoint):
(WebCore::RenderRegion::checkRegionStyle):
(WebCore::RenderRegion::computeStyleInRegion):
* rendering/RenderTreeAsText.cpp:
(WebCore::writeRenderNamedFlowThreads):

LayoutTests:

The new ref-test has a block with both a :before and :after pseudo-elements marked as regions.
In the block there's another region.

The test verifies the content is correctly flowed (the region order is respected) in the region chain:
:before region -> child region -> :after region

As a region a pseudo-element should also be displayed if there's no content property specified in the style sheet.

* fast/regions/content-flowed-into-pseudo-regions-expected.html: Added.
* fast/regions/content-flowed-into-pseudo-regions.html: Added.
* fast/regions/resources/region-style.css:
(.regionArticleAfter::after, .regionArticleBefore::before):
(.borderBoxNoFloat):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127269 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[New Multicolumn] Make RenderFlowThreads into selection roots.
https://bugs.webkit.org/show_bug.cgi?id=95580

Reviewed by Dan Bernstein.

Make RenderFlowThreads selection roots so that they paint their own selection gaps.
This fixes multicolumn selection rendering so that the gaps paint correctly and stop
at the edge of the flow thread instead of going out to the edges of enclosing blocks.

* rendering/RenderBlock.cpp:
(WebCore::RenderBlock::isSelectionRoot):



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127270 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Web Inspector: sort object properties when dumping them in tests
https://bugs.webkit.org/show_bug.cgi?id=95459

Fix the expected results for timeline-paint to actually be in order.

* inspector/timeline/timeline-paint-expected.txt:
'height' comes before 'width' alphabetically.
* platform/chromium/inspector/timeline/timeline-paint-expected.txt: Removed.
Once the cross-platform results were fixed, this file was identical to the cross-platform
file. Remove it.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127271 268f45cc-cd09-0410-ab3c-d52691b4dbfc
REGRESSION (127047): Crash in PluginProxy::windowVisibilityChanged when changing tabs
<rdar://problem/12211180> and https://bugs.webkit.org/show_bug.cgi?id=95515

Reviewed by Dan Bernstein.

Plug-ins created in background tabs don't get initialized until they first become visible,
so telling them they are now invisible leads to messaging on behalf of an uninitialized plug-in.

Many other methods related to visibility and focus only call through if the plug-in is initialized,
so setWindowIsVisible should do the same.

* WebProcess/Plugins/PluginView.cpp:
(WebKit::PluginView::setWindowIsVisible): Only tell initialized plug-ins of window visibility changes.

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