mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-07-23 09:22:30 +00:00
5ed91dc915
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.
35 lines
626 B
C++
35 lines
626 B
C++
/*
|
|
* Copyright (c) 2025, Tim Flynn <trflynn89@ladybird.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
namespace DevTools {
|
|
|
|
class Actor;
|
|
class Connection;
|
|
class CSSPropertiesActor;
|
|
class DeviceActor;
|
|
class DevToolsDelegate;
|
|
class DevToolsServer;
|
|
class FrameActor;
|
|
class HighlighterActor;
|
|
class InspectorActor;
|
|
class PageStyleActor;
|
|
class PreferenceActor;
|
|
class ProcessActor;
|
|
class RootActor;
|
|
class TabActor;
|
|
class TargetConfigurationActor;
|
|
class ThreadActor;
|
|
class ThreadConfigurationActor;
|
|
class WalkerActor;
|
|
class WatcherActor;
|
|
|
|
struct CSSProperty;
|
|
struct ProcessDescription;
|
|
struct TabDescription;
|
|
|
|
}
|