[GTK] Tries to run empty string when calling generate-gtkdoc when not using jhbuild
https://bugs.webkit.org/show_bug.cgi?id=95499

Unreviewed. One more fix to avoid trying to run the empty string.

* Scripts/webkitdirs.pm:
(buildAutotoolsProject):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127201 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Use one object instead of two for closures, eliminating ScopeChainNode
https://bugs.webkit.org/show_bug.cgi?id=95501

Reviewed by Filip Pizlo.

../JavaScriptCore: 

This patch removes ScopeChainNode, and moves all the data and related
functions that used to be in ScopeChainNode into JSScope.

Most of this patch is mechanical changes to use a JSScope* where we used
to use a ScopeChainNode*. I've only specifically commented about items
that were non-mechanical.

* runtime/Completion.cpp:
(JSC::evaluate):
* runtime/Completion.h: Don't require an explicit scope chain argument
when evaluating code. Clients never wanted anything other than the
global scope, and other arbitrary scopes probably wouldn't work
correctly, anyway.

* runtime/JSScope.cpp:
* runtime/JSScope.h:
(JSC::JSScope::JSScope): JSScope now requires the data we used to pass to
ScopeChainNode, so it can link itself into the scope chain correctly.

* runtime/JSWithScope.h:
(JSC::JSWithScope::create):
(JSC::JSWithScope::JSWithScope): JSWithScope gets an extra constructor
for specifically supplying your own scope chain. The DOM needs this
interface for setting up the scope chain for certain event handlers.
Other clients always just push the JSWithScope to the head of the current
scope chain.

../WebCore: 

Mechanical changes to update for JSC interface changes.

../WebKit/mac: 

Mechanical change to update for JSC interface change.

../WebKit/qt: 

Mechanical change to update for JSC interface change.

* Api/qwebelement.cpp:
(QWebElement::evaluateJavaScript):

../WebKit2: 

Mechanical changes to update for JSC interface change.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127202 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium-Android] Skip compositing/webgl and platform/chromium/virtual/threaded/compositing/webgl tests
https://bugs.webkit.org/show_bug.cgi?id=95400

Reviewed by Dirk Pranke.

WebGL is not enabled and should be skipped on Android (http://crbug.com/135877).

* Scripts/webkitpy/layout_tests/port/chromium_android.py:
(ChromiumAndroidPort.skipped_layout_tests):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127203 268f45cc-cd09-0410-ab3c-d52691b4dbfc
First step toward fixing the Windows build: Remove old symbols.

* JavaScriptCore.vcproj/JavaScriptCore/JavaScriptCore.def:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127204 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Try to fix the Qt build: add an #include.

* bytecode/GetByIdStatus.cpp:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127205 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Crash in RenderTable::calcBorderEnd
https://bugs.webkit.org/show_bug.cgi?id=95487

Reviewed by Abhishek Arya.

Source/WebCore:

r126590 opened the window for a race condition in RenderObjectChildList::removeChildNode.
This is caused because willBeRemovedFromTree should be strictly following by the actual removal
and wasn't.

This race condition was caused by clearSelection() being called just after willBeRemovedFromTree,
which forced a section's cells recalc and would re-add the soon-to-be-removed child, causing the
crash.

Test: fast/table/crash-clearSelection-collapsed-borders.html

* rendering/RenderObjectChildList.cpp:
(WebCore::RenderObjectChildList::removeChildNode):
Moved the clearSeletion call before willBeRemovedFromTree. Added a warning about running code
after willBeRemovedFromTree and before removing the child from the tree.

LayoutTests:

* fast/table/crash-clearSelection-collapsed-borders-expected.txt: Added.
* fast/table/crash-clearSelection-collapsed-borders.html: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127206 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Second step toward fixing the Windows build: Add new symbols.

* JavaScriptCore.vcproj/JavaScriptCore/JavaScriptCore.def:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127207 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Try to fix the Qt build: add an #include to JSArray.h, since
it's included by some of the files Qt complains about, and
some of is functions call the functions Qt complains about.

* runtime/JSArray.h:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127208 268f45cc-cd09-0410-ab3c-d52691b4dbfc
CSS 2.1 failure: margin-collapse-clear-012 fails
https://bugs.webkit.org/show_bug.cgi?id=80394

Mark fast/block/margin-collapse/empty-clear-blocks.html as an expected text failure on Mac,
not both an image and text failure, since the bots are only seeing it as a text failure.

* platform/mac/TestExpectations:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127209 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Undo Qt build fix guess, since it breaks other builds.

* runtime/JSArray.h:



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