NRWT: lint warnings don't show up by default
https://bugs.webkit.org/show_bug.cgi?id=100914

Reviewed by Ryosuke Niwa.

NRWT wasn't printing any warnings if you had errors in your
TestExpectations files; this means you would only notice this
with --lint-test-files, which is probably bad. I'm not sure
when this requested, but perhaps when we changed the
warnings to not be fatal if you weren't linting the files.

Now they're still not fatal, but at least we print them.

Also fix one warning message where we were printing the test name twice.

* Scripts/webkitpy/layout_tests/models/test_expectations.py:
(TestExpectationsModel._already_seen_better_match):
(TestExpectations._report_warnings):
* Scripts/webkitpy/layout_tests/models/test_expectations_unittest.py:
(MiscTests.test_parse_warnings_are_logged_if_not_in_lint_mode(self): Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133121 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[chromium] Pass canPaintLCDText to WebContentLayerClient::paintContents
https://bugs.webkit.org/show_bug.cgi?id=99083

Reviewed by James Robinson.

Use LCD text setting passed to WebContentLayerClient::paintContents instead of turning it off for all composited layers.

Source/Platform:

* chromium/public/WebContentLayerClient.h:
(WebContentLayerClient):
(WebKit::WebContentLayerClient::paintContents):

Source/WebCore:

No new tests needed. This patch does not change anything functionally.

* platform/graphics/chromium/GraphicsLayerChromium.cpp:
(WebCore::GraphicsLayerChromium::setContentsOpaque):
(WebCore::GraphicsLayerChromium::paint):
* platform/graphics/chromium/OpaqueRectTrackingContentLayerDelegate.cpp:
(WebCore::OpaqueRectTrackingContentLayerDelegate::paintContents):
* platform/graphics/chromium/OpaqueRectTrackingContentLayerDelegate.h:
(OpaqueRectTrackingContentLayerDelegate):

Source/WebKit/chromium:

* src/LinkHighlight.cpp:
(WebKit::LinkHighlight::paintContents):
* src/LinkHighlight.h:
(LinkHighlight):
* src/NonCompositedContentHost.cpp:
(WebKit::NonCompositedContentHost::NonCompositedContentHost):
(WebKit::NonCompositedContentHost::setOpaque):
(WebKit::NonCompositedContentHost::paintContents):
* src/NonCompositedContentHost.h:
(NonCompositedContentHost):
* tests/OpaqueRectTrackingContentLayerDelegateTest.cpp:
(WebCore::TEST_F):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133122 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Make resolveReprojection() defined in ComposedShadowTreeWalker.cpp callable from outside.
https://bugs.webkit.org/show_bug.cgi?id=100832

Reviewed by Dimitri Glazkov.

InsertionPoint.h now defines resolveReprojection() so that it can be called from outside.

No new tests as no new functionality.

* dom/ComposedShadowTreeWalker.cpp:
* html/shadow/InsertionPoint.h:
(WebCore::shadowOfParentForDistribution):
(WebCore):
(WebCore::resolveReprojection):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133123 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Refactoring] Move initial style setting for ProgressValueElement from attach method to createShadowSubtree method in HTMLProgressElement.
https://bugs.webkit.org/show_bug.cgi?id=83664

Reviewed by Hajime Morita.

Source/WebCore:

The original code updates inline style during attach(). However,
the attach would be invoked from Element::recalcStyle()'s reattach().
If updating inline styles during the reattach(), style related flags,
i.e. childNeedsStyleRecalc, and needsStyleRecalc are cleared after the
reattach(). So the inline styles are not updated in next
setNeedsStyleRecalc, because ProgressValueElement has already had
InlineStyleChange (existingChanegType == InlineStyleChange) and
markAncestorsWithChildNeedsStyleRecalc is not invoked.

Test: fast/dom/HTMLProgressElement/progress-bar-set-value.html

* html/HTMLProgressElement.cpp:
(WebCore::HTMLProgressElement::attach):
Copied updateFromElement from didElementStateChange. If removing the
update, indeterminate-progress-001.html and progress-element.html
under fast/dom/HTMLProgressElement will fail. We still need attach()
and updateFromElement. To remove the attach(), need more refactoring,
i.e. investigating where attach() is invoked from and modifying all
related codes.
(WebCore::HTMLProgressElement::createShadowSubtree):
Initialize m_value by indeterminate-position. The value is default
value of progress element.

LayoutTests:

* fast/dom/HTMLProgressElement/progress-bar-set-value-expected.html: Added.
* fast/dom/HTMLProgressElement/progress-bar-set-value.html: Added.


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