dmaax/ladybird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

LibWebView+WebContent: Move test-mode special handling to the UI process

Browse source 
We will need to propagate test mode behavior to both the WebContent and
WebWorker processes. By moving this handling to the UI process, we will
only need to update one location.
This commit is contained in:
Timothy Flynn 2026-02-17 13:55:51 -05:00 committed by Shannon Booth
parent ce3742724a
commit b357d3c3c8
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
Libraries/LibWebView/Application.cpp
View file

@ -299,6 +299,13 @@ ErrorOr<void> Application::initialize(Main::Arguments const& arguments)
};
create_platform_options(m_browser_options, m_request_server_options, m_web_content_options);
// Test mode implies internals object is exposed and the Skia CPU backend is used
if (m_web_content_options.is_test_mode == IsTestMode::Yes) {
m_web_content_options.expose_internals_object = ExposeInternalsObject::Yes;
m_web_content_options.force_cpu_painting = ForceCPUPainting::Yes;
}
initialize_actions();
m_event_loop = create_platform_event_loop();

6
Services/WebContent/main.cpp
View file

@ -144,12 +144,6 @@ ErrorOr<int> ladybird_main(Main::Arguments arguments)
}
font_provider.load_all_fonts_from_uri("resource://fonts"sv);
// Test mode implies internals object is exposed and the Skia CPU backend is used
if (enable_test_mode) {
expose_internals_object = true;
force_cpu_painting = true;
}
Web::set_browser_process_command_line(command_line);
Web::set_browser_process_executable_path(executable_path);