Add CSS parsing recovery to functions
https://bugs.webkit.org/show_bug.cgi?id=117500

Reviewed by Andreas Kling.

From Blink r150205 by <serya@chromium.org>

Source/WebCore:

Add parsing recovery capabilities to functions. Errors were
correctly detected without this change but then the whole
declaration was invalidated. By using expr_recovery to handle them
we can recover from those errors and go on with the parsing.

* css/CSSGrammar.y.in:

LayoutTests:

* fast/css/parsing-error-recovery.html: added some test cases for
parsing recovery inside functions.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@151488 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[GTK] Parameter 'pseudoElement' from function 'webkit_dom_dom_window_get_computed_style' should be allowed to be NULL
https://bugs.webkit.org/show_bug.cgi?id=117332

Patch by Diego Pino Garcia <dpino@igalia.com> on 2013-06-12
Reviewed by Xan Lopez.

Source/WebCore:

Add parameter 'pseudoElement' to the list of parameters that are allowed to
be NULL.

* bindings/scripts/CodeGeneratorGObject.pm:
(GetGReturnMacro):

Source/WebKit/gtk:

Add test for function 'webkit_dom_dom_window_get_computed_style'.

* tests/testdomdomwindow.c:
(dom_dom_window_fixture_setup): Test setup for function
'dom_dom_window_get_computed_style'.
(dom_dom_window_fixture_teardown): Test teardown for function
'dom_dom_window_get_computed_style'.
(loadedCallback):
(test_dom_dom_window_get_computed_style): Checks function
'dom_dom_window_get_computed_style'.
(main):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@151489 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed GTK build fix.

* GNUmakefile.list.am: Adding missing build targets to the plugin process after r151480.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@151490 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Remove memoryInfoEnabled, quantizedMemoryInfoEnabled settings
https://bugs.webkit.org/show_bug.cgi?id=117512

Reviewed by Darin Adler.

Source/WebCore: 

* page/Settings.in: Remove the memoryInfoEnabled and the quantizedMemoryInfoEnabled settings. These are not used
anywhere anymore after r151199 which simplified and moved the MemoryInfo interface under window.internals.

Source/WebKit/blackberry: 

* Api/WebPage.cpp:
(BlackBerry::WebKit::WebPagePrivate::init): Remove the call to Settings::setMemoryInfoEnabled, the setting is being removed.

Source/WebKit/mac: 

* WebKit.order: Remove the memoryInfoEnabled entry.
* WebView/WebPreferenceKeysPrivate.h: Remove WebKitMemoryInfoEnabledPreferenceKey.
* WebView/WebPreferences.mm: Remove memoryInfoEnabled, setMemoryInfoEnabled methods.
(+[WebPreferences initialize]): Don't set the default value for the WebKitMemoryInfoEnabledPreferenceKey, the preference is being removed.
* WebView/WebPreferencesPrivate.h: Remove memoryInfoEnabled, setMemoryInfoEnabled method declarations.
* WebView/WebView.mm:
(-[WebView _preferencesChanged:]): Remove the call to Settings::setMemoryInfoEnabled, the setting is being removed.

Source/WebKit/win: 

* Interfaces/IWebPreferencesPrivate.idl: Remove memoryInfoEnabled, setMemoryInfoEnabled entries.
* WebPreferenceKeysPrivate.h: Remove the WebKitMemoryInfoEnabledPreferenceKey definition.
* WebPreferences.cpp: Remove the memoryInfo, setMemoryInfoEnabled methods.
(WebPreferences::initializeDefaultSettings): Remove the WebKitMemoryInfoEnabledPreferenceKey entry initialization.
* WebPreferences.h: Remove the memoryInfo, setMemoryInfoEnabled method declarations.
* WebView.cpp:
(WebView::notifyPreferencesChanged): Remove the Settings::setMemoryInfoEnabled call, the method is being removed.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@151491 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[GTK] Remove the WebCoreLayer(Gtk2).a archives before regenerating them
https://bugs.webkit.org/show_bug.cgi?id=116723

Reviewed by Carlos Garcia Campos.

Source/WebKit2: 

* GNUmakefile.am: When generating the WebCoreLayerGtk2.a archive from all the dependency archives, remove the
current archive (if any). Updating an existent archive in an incremental build is not bulletproof and can lead
to corrupt archives and subsequent build failures. On the other hand, the archive generation is not expensive
and produces a working archive without problems even on incremental builds.

Tools: 

* TestWebKitAPI/GNUmakefile.am: When generating the WebCoreLayer.a archive from all the dependency archives,
remove the current archive (if any). Updating an existent archive in an incremental build is not bulletproof
and can lead to corrupt archives and subsequent build failures. On the other hand, the archive generation is
not expensive and produces a working archive without problems even on incremental builds.


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