2014-07-16  Adrian Perez de Castro  <aperez@igalia.com>

        [GTK] Support script message handlers WebKitUserContentManager

        https://bugs.webkit.org/show_bug.cgi?id=133730

        Reviewed by NOBODY (OOPS!).

        Support user script message handlers in WebKitUserContentManager.

        This needs building with ENABLE_USER_MESSAGE_HANDLERS, for which

        an option is added to the CMake build files. The option is disabled

        globally by default, and the WebKitGTK port enables it. On the API

        level, two new methods to register and unregister names are provided

        in the "window.webkit" namespace, and on message reception the

        "WebKitUserContentManager::script-message-received" signal is

        emitted, using the registered names as signal detail.

        * CMakeLists.txt: Conditionally add the needed files to the build

        when the ENABLE_USER_MESSAGE_HANDLERS feature is enabled.

2014-07-16  Adrian Perez de Castro  <aperez@igalia.com>

        [GTK] Support script message handlers WebKitUserContentManager

        https://bugs.webkit.org/show_bug.cgi?id=133730

        Reviewed by NOBODY (OOPS!).

        Support user script message handlers in WebKitUserContentManager.

        This needs building with ENABLE_USER_MESSAGE_HANDLERS, for which

        an option is added to the CMake build files. The option is disabled

        globally by default, and the WebKitGTK port enables it. On the API

        level, two new methods to register and unregister names are provided

        in the "window.webkit" namespace, and on message reception the

        "WebKitUserContentManager::script-message-received" signal is

        emitted, using the registered names as signal detail.

        * UIProcess/API/gtk/WebKitJavascriptResult.cpp: Add a new private

        function to construct a WebKitJavascriptResult directly from a

        WebCore::SerializedScriptValue.

        (_WebKitJavascriptResult::_WebKitJavascriptResult): Ditto.

        (webkitJavascriptResultCreate): Ditto.

        * UIProcess/API/gtk/WebKitJavascriptResultPrivate.h: Ditto.

        * UIProcess/API/gtk/WebKitUserContentManager.cpp:

        (webkit_user_content_manager_class_init): Install the

        "script-message-received" signal.

        (webkit_user_content_manager_register_script_message_handler):

        Added.

        (webkit_user_content_manager_unregister_script_message_handler):

        Added.

        * UIProcess/API/gtk/WebKitUserContentManager.h: Added the new

        public API methods.

        * UIProcess/API/gtk/docs/webkit2gtk-sections.txt: Ditto.

        * UIProcess/API/gtk/docs/webkit2gtk.types: Add

        webkit_user_content_manager_get_type() to the list in order to make

        gtk-doc to generate documentation for signals.

if (ENABLE_USER_MESSAGE_HANDLERS)

    list(APPEND WebCore_IDL_FILES

        page/UserMessageHandler.idl

        page/UserMessageHandlersNamespace.idl

        page/WebKitNamespace.idl

    )

    list(APPEND WebCore_SOURCES

        bindings/js/JSUserMessageHandlersNamespaceCustom.cpp

        page/UserMessageHandler.cpp

        page/UserMessageHandlerDescriptor.cpp

        page/UserMessageHandlersNamespace.cpp

        page/WebKitNamespace.cpp

    )

endif ()

    _WebKitJavascriptResult(WebKitWebView* view, WebCore::SerializedScriptValue& serializedScriptValue)

        : webView(view)

        , referenceCount(1)

    {

        value = serializedScriptValue.deserialize(webkit_web_view_get_javascript_global_context(view), nullptr);

    }

WebKitJavascriptResult* webkitJavascriptResultCreate(WebKitWebView* webView, WebCore::SerializedScriptValue& serializedScriptValue)

{

    WebKitJavascriptResult* result = g_slice_new(WebKitJavascriptResult);

    new (result) WebKitJavascriptResult(webView, serializedScriptValue);

    return result;

}

#include <WebCore/SerializedScriptValue.h>

WebKitJavascriptResult* webkitJavascriptResultCreate(WebKitWebView*, WebCore::SerializedScriptValue&);

#include "WebKitJavascriptResult.h"

#include "WebKitJavascriptResultPrivate.h"

#include "WebKitWebContextPrivate.h"

#include "WebScriptMessageHandler.h"

#include "WebSerializedScriptValue.h"

    GObjectClass* gObjectClass = G_OBJECT_CLASS(klass);

    /**

     * WebKitUserContentManager::script-message-received:

     * @manager: the #WebKitUserContentManager

     * @js_result: the #WebKitJavascriptResult holding the value received

     *     from the JavaScript world.

     *

     * This signal is emitted when JavaScript in a web view calls

     * <code>window.webkit.&lt;name&gt;.postMessage()</code>, after registering

     * <code>&lt;name&gt;</code> using

     * webkit_user_content_manager_register_script_message_handler()

     *

     * Since: 2.6

     */

    signals[SCRIPT_MESSAGE_RECEIVED] =

        g_signal_new(

            "script-message-received",

            G_TYPE_FROM_CLASS(gObjectClass),

            static_cast<GSignalFlags>(G_SIGNAL_RUN_LAST | G_SIGNAL_DETAILED),

            0, nullptr, nullptr,

            g_cclosure_marshal_VOID__BOXED,

            G_TYPE_NONE, 1,

            WEBKIT_TYPE_JAVASCRIPT_RESULT);

class ScriptMessageClientGtk final : public WebScriptMessageHandler::Client {

public:

    ScriptMessageClientGtk(WebKitUserContentManager* manager, const gchar* handlerName)

        : m_handlerName(g_quark_from_string(handlerName))

        , m_manager(manager)

    {

    }

    virtual void didPostMessage(WebPageProxy& page, WebFrameProxy&, WebCore::SerializedScriptValue& serializedScriptValue)

    {

        auto jsResult = adoptGRef(webkitJavascriptResultCreate(WEBKIT_WEB_VIEW(page.viewWidget()), serializedScriptValue));

        g_signal_emit(m_manager.get(), signals[SCRIPT_MESSAGE_RECEIVED], m_handlerName, jsResult.get());

    }

    virtual ~ScriptMessageClientGtk() { }

private:

    GQuark m_handlerName;

    GRefPtr<WebKitUserContentManager> m_manager;

};

/**

 * webkit_user_content_manager_register_script_message_handler:

 * @manager: A #WebKitUserContentManager

 * @name: Name of the script message channel

 *

 * Registers a new user script message handler name. After it is

 * registered, scripts can use `window.webkit.<name>.postMessage(value)`

 * to send messages. Those messages are received by connecting handlers

 * to the WebKitUserContentManager::script-message-received signal. The

 * handler name is used as the detail of the signal. To avoid race

 * conditions between registering the handler name, and starting to

 * receive the signals, it is recommended to connect to the signal

 * *before* registering the handler name:

 *

 * <informalexample><programlisting>

 * WebKitWebView *view = webkit_web_view_new ();

 * WebKitUserContentManager *manager = webkit_web_view_get_user_content_manager ();

 * g_signal_connect (manager, "script-message-received::foobar",

 *                   G_CALLBACK (handle_script_message), NULL);

 * webkit_user_content_manager_register_script_message_handler (manager, "foobar");

 * </programlisting></informalexample>

 *

 * Registering a script message handler will fail if the requested

 * name has been already registered before.

 *

 * Returns: Whether the message channel was registered successfully.

 *

 * Since: 2.6

 */

gboolean webkit_user_content_manager_register_script_message_handler(WebKitUserContentManager* manager, const gchar* name)

{

    g_return_val_if_fail(WEBKIT_IS_USER_CONTENT_MANAGER(manager), FALSE);

    g_return_val_if_fail(name, FALSE);

    const auto handler_name = String::fromUTF8(name);

    auto handler = WebScriptMessageHandler::create(std::make_unique<ScriptMessageClientGtk>(manager, name), handler_name);

    return manager->priv->userContentController->addUserScriptMessageHandler(handler.get());

}

/**

 * webkit_user_content_manager_unregister_script_message_handler:

 * @manager: A #WebKitUserContentManager

 * @name: Name of the script message channel

 *

 * Unregisters a previously registered message handler name.

 *

 * Note that this does *not* disconnect handlers for the

 * WebKitUserContentManager::script-message-received signal:

 * the signal handlers will be kept connected, but the signal

 * will not be emitted unless the handler name is registered

 * again.

 *

 * See: webkit_user_content_manager_register_script_message_handler()

 *

 * Since: 2.6

 */

void webkit_user_content_manager_unregister_script_message_handler(WebKitUserContentManager* manager, const gchar* name)

{

    g_return_if_fail(WEBKIT_IS_USER_CONTENT_MANAGER(manager));

    manager->priv->userContentController->removeUserMessageHandlerForName(String::fromUTF8(name));

}

webkit_user_content_manager_register_script_message_handler

webkit_user_content_manager_unregister_script_message_handler

webkit_user_content_manager_get_type

WEBKIT_OPTION_DEFAULT_PORT_VALUE(ENABLE_USER_MESSAGE_HANDLERS ON)

    WEBKIT_OPTION_DEFINE(ENABLE_USER_MESSAGE_HANDLERS "Toggle user script message handler support" OFF)

2014-07-16  Adrian Perez de Castro  <aperez@igalia.com>

        [GTK] Support script message handlers WebKitUserContentManager

        https://bugs.webkit.org/show_bug.cgi?id=133730

        Reviewed by NOBODY (OOPS!).

        Support user script message handlers in WebKitUserContentManager.

        This needs building with ENABLE_USER_MESSAGE_HANDLERS, for which

        an option is added to the CMake build files. The option is disabled

        globally by default, and the WebKitGTK port enables it. On the API

        level, two new methods to register and unregister names are provided

        in the "window.webkit" namespace, and on message reception the

        "WebKitUserContentManager::script-message-received" signal is

        emitted, using the registered names as signal detail.

        * TestWebKitAPI/Tests/WebKit2Gtk/TestWebKitUserContentManager.cpp:

        Add test case for user script message handlers.

        (scriptMessageReceived):

        (testUserContentManagerScriptMessageReceived):

        (beforeAll):

#if ENABLE_USER_MESSAGE_HANDLERS

static void scriptMessageReceived(WebKitUserContentManager*, WebKitJavascriptResult* jsResult, gpointer refPtr)

{

    auto resultRefPtr = reinterpret_cast<GRefPtr<WebKitJavascriptResult>*>(refPtr);

    *resultRefPtr = jsResult;

}

static void testUserContentManagerScriptMessageReceived(UserContentManagerTest* test, gconstpointer)

{

    GRefPtr<WebKitJavascriptResult> message;

    g_signal_connect(test->m_userContentManager.get(), "script-message-received::msg", G_CALLBACK(scriptMessageReceived), &message);

    webkit_user_content_manager_register_message_handler(test->m_userContentManager.get(), "msg");

    test->loadHtml("<html></html>", nullptr);

    test->waitUntilLoadFinished();

    // Check that the "document.webkit" namespace exists

    GUniqueOutPtr<GError> error;

    WebKitJavascriptResult* javascriptResult = test->runJavaScriptAndWaitUntilFinished("window.webkit ? 'y' : 'n';", &error.outPtr());

    g_assert(javascriptResult);

    g_assert(!error.get());

    GUniquePtr<char> valueString(WebViewTest::javascriptResultToCString(javascriptResult));

    g_assert_cmpstr(valueString.get(), ==, "y");

    // Check that the "document.webkit.msg" namespace exists

    javascriptResult = test->runJavaScriptAndWaitUntilFinished("window.webkit.msg ? 'y' : 'n';", &error.outPtr());

    g_assert(javascriptResult);

    g_assert(!error.get());

    valueString.reset(WebViewTest::javascriptResultToCString(javascriptResult));

    g_assert_cmpstr(valueString.get(), ==, "y");

    // Call "document.webkit.msg.postMessage()" and check that the flag was flipped

    javascriptResult = test->runJavaScriptAndWaitUntilFinished("window.webkit.msg.postMessage('user message');", &error.outPtr());

    g_assert(javascriptResult);

    g_assert(!error.get());

    g_assert(message.get());

    valueString.reset(WebViewTest::javascriptResultToCString(message));

    g_assert_cmpstr(valueString.get(), ==, "user message");

}

#endif

#if ENABLE_USER_MESSAGE_HANDLERS

    UserContentManagerTest::add("WebKitUserContentManager", "script-message-received", testUserContentManagerScriptMessageReceived);

#endif

2014-07-16  Adrian Perez de Castro  <aperez@igalia.com>

        [GTK] Support script message handlers WebKitUserContentManager

        https://bugs.webkit.org/show_bug.cgi?id=133730

        Reviewed by NOBODY (OOPS!).

        Support user script message handlers in WebKitUserContentManager.

        This needs building with ENABLE_USER_MESSAGE_HANDLERS, for which

        an option is added to the CMake build files. The option is disabled

        globally by default, and the WebKitGTK port enables it. On the API

        level, two new methods to register and unregister names are provided

        in the "window.webkit" namespace, and on message reception the

        "WebKitUserContentManager::script-message-received" signal is

        emitted, using the registered names as signal detail.

        * Source/cmake/OptionsGTK.cmake: For the GTK port, enable the

        ENABLE_USER_MESSAGE_HANDLERS feature by default.

        * Source/cmake/WebKitFeatures.cmake: Add feature description for

        ENABLE_USER_MESSAGE_HANDLERS, disabled by default.