ladybird/Libraries/LibDevTools/Actors/ThreadConfigurationActor.h

/*
 * Copyright (c) 2025, Tim Flynn <trflynn89@ladybird.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#pragma once

#include <AK/NonnullRefPtr.h>
#include <LibDevTools/Actor.h>

namespace DevTools {

class ThreadConfigurationActor final : public Actor {
public:
    static constexpr auto base_name = "thread-configuration"sv;

    static NonnullRefPtr<ThreadConfigurationActor> create(DevToolsServer&, String name);
    virtual ~ThreadConfigurationActor() override;

    JsonObject serialize_configuration() const;

private:
    ThreadConfigurationActor(DevToolsServer&, String name);

    virtual void handle_message(Message const&) override;
};

}
LibDevTools: Implement enough of the protocol to inspect tabs There is a lot needed all at once to actually inspect a tab's DOM tree. It begins with requesting a "watcher" from a TabActor. It seems there can be many types of watchers, but here we implement the "frame" watcher only. The watcher creates an "inspector", which in turn creates a "walker", which is the actor ultimately responsible for serializing and inspecting the DOM tree. In between all that, the DevTools client will send a handful of other informational requests. If we do not reply to these, the client will not move forward with the walker. For example, the CSSPropertiesActor will be asked for a list of all known CSS properties. 2025-02-15 07:57:36 -05:00			`/*`
			`* Copyright (c) 2025, Tim Flynn <trflynn89@ladybird.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#pragma once`

			`#include <AK/NonnullRefPtr.h>`
			`#include <LibDevTools/Actor.h>`

			`namespace DevTools {`

			`class ThreadConfigurationActor final : public Actor {`
			`public:`
			`static constexpr auto base_name = "thread-configuration"sv;`

LibDevTools+LibWebView: Port DevTools to String 2025-02-19 09:28:02 -05:00			`static NonnullRefPtr<ThreadConfigurationActor> create(DevToolsServer&, String name);`
LibDevTools: Implement enough of the protocol to inspect tabs There is a lot needed all at once to actually inspect a tab's DOM tree. It begins with requesting a "watcher" from a TabActor. It seems there can be many types of watchers, but here we implement the "frame" watcher only. The watcher creates an "inspector", which in turn creates a "walker", which is the actor ultimately responsible for serializing and inspecting the DOM tree. In between all that, the DevTools client will send a handful of other informational requests. If we do not reply to these, the client will not move forward with the walker. For example, the CSSPropertiesActor will be asked for a list of all known CSS properties. 2025-02-15 07:57:36 -05:00			`virtual ~ThreadConfigurationActor() override;`

			`JsonObject serialize_configuration() const;`

			`private:`
LibDevTools+LibWebView: Port DevTools to String 2025-02-19 09:28:02 -05:00			`ThreadConfigurationActor(DevToolsServer&, String name);`
LibDevTools: Move message data into a structure This is to prepare for an upcoming change where we will need to track replies to messages by ID. We will be able to add parameters to this structure without having to edit every single actor subclass header file. 2025-03-12 08:01:23 -04:00
			`virtual void handle_message(Message const&) override;`
LibDevTools: Implement enough of the protocol to inspect tabs There is a lot needed all at once to actually inspect a tab's DOM tree. It begins with requesting a "watcher" from a TabActor. It seems there can be many types of watchers, but here we implement the "frame" watcher only. The watcher creates an "inspector", which in turn creates a "walker", which is the actor ultimately responsible for serializing and inspecting the DOM tree. In between all that, the DevTools client will send a handful of other informational requests. If we do not reply to these, the client will not move forward with the walker. For example, the CSSPropertiesActor will be asked for a list of all known CSS properties. 2025-02-15 07:57:36 -05:00			`};`

			`}`