[Windows, WinCairo] Stop individually building WTF files in JSC.
https://bugs.webkit.org/show_bug.cgi?id=114705

Reviewed by Anders Carlsson.

* JavaScriptCore.vcproj/JavaScriptCore/JavaScriptCoreExports.def:
Export additional String/fastMalloc symbols needed by JSC program.
* JavaScriptCore.vcproj/jsc/jsc.vcproj: Don't manually build
WTF implementation files (a second time!) in this project.
* JavaScriptCore.vcxproj/JavaScriptCoreExportGenerator/JavaScriptCoreExports.def.in:
Export additional String/fastMalloc symbols needed by JSC program.
* JavaScriptCore.vcxproj/jsc/jsc.vcxproj: Don't manually
build WTF implementation files (a second time!) in this project.
* JavaScriptCore.vcxproj/jsc/jsc.vcxproj.filters: Ditto.



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@148576 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed. Build fix for Windows.

* WebCoreSupport/WebContextMenuClient.cpp:
* WebCoreSupport/WebDragClient.cpp:
* WebFrame.cpp:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@148577 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Further unreviewed build fix: protect JSAudioBufferCustom with a ENABLE(WEB_AUDIO) check.

* bindings/js/JSAudioBufferCustom.cpp:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@148579 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[CSS Shaders] Add a test with a vertex, fragment shader pair that compiles but don't link
https://bugs.webkit.org/show_bug.cgi?id=114636

Added a test to check that unavailable varyings in fragment shaders
don't lead to unexpected crashes due to linking errors.
The current implementation does not crash, and this makes sure it
won't in future.

Reviewed by Dean Jackson.

* css3/filters/custom/custom-filter-unavailable-varying-expected.html: Added.
* css3/filters/custom/custom-filter-unavailable-varying.html: Added.
* css3/filters/resources/unavailable-varying.fs: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@148581 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[CSS Exclusions] polygon shape-inside layout fails
https://bugs.webkit.org/show_bug.cgi?id=114402

Source/WebCore:

Reviewed by Dirk Schulze.

The firstIncludedIntervalLogicalTop() method's implementation relied on optimistic
assumptions about floating point accuracy which, in rare cases, caused it to discard
first-fit locations based on the intersection of the minLogicalIntervalTop offset edge
and a polygon offset edge. Now: we do not verify that first-fit locations based on the
intersection of an offset edge and the minLogicalIntervalTop offset edge are below
the horizontal minLogicalIntervalTop line. They're essentially below the line "by definition".

Test: fast/exclusions/shape-inside/shape-inside-polygon-layout.html

* rendering/ExclusionPolygon.cpp:
(WebCore::ExclusionPolygon::firstIncludedIntervalLogicalTop): Avoid floating point problems
    when checking intersections with the offset edge based on minLogicalIntervalTop.
* rendering/ExclusionPolygon.h:
(WebCore::OffsetPolygonEdge::OffsetPolygonEdge): Initialize the basis field.
(WebCore::OffsetPolygonEdge::basis): Report what the offset edge is "based on": a polygon
    edge, the top of the line, or a (reflex) vertex.
(OffsetPolygonEdge): Added the Basis enum to enable tracking what the geometry of
    an offset edge is based on.

LayoutTests:

Verify that subsequent polygon shape-inside lines are vertically adjacent.

Reviewed by Dirk Schulze.

* fast/exclusions/shape-inside/shape-inside-polygon-layout-expected.txt: Added.
* fast/exclusions/shape-inside/shape-inside-polygon-layout.html: Added.


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