Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-19 15:43:20 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Libraries/LibWebView/CMakeLists.txt

114 lines
3.1 KiB
Text
Raw Normal View History

LibWebView+Services+UI: Move the Web plugins to LibWebView
2024-11-10 09:53:15 -05:00
include(fontconfig)
LibWebView+LibPublicSuffix: Merge LibPublicSuffix into LibWebView After d2c7e1ea7db060c1f01a740fab65f3e35a45545b, there is now only one user of LibPublicSuffix - the URL sanitation utility within LibWebView. Rather than having an entire library for the small Public Suffix data accessor, merge it into LibWebView.
2023-10-14 09:07:38 -04:00
LibWebView: Move OutOfProcessWebView to a new LibWebView library Also moves WebContentClient and the references to the generated IPC descriptions, since they are all components of OutOfProcessWebView. This patch has no functional changes.
2022-04-30 10:46:33 +02:00
set(SOURCES
LibWebView+LibCore: Manage process lifecycle using a SIGCHLD handler This large commit also refactors LibWebView's process handling to use a top-level Application class that uses a new WebView::Process class to encapsulate the IPC-centric nature of each helper process.
2024-06-29 22:24:01 -06:00
Application.cpp
LibWebView+WebContent: Add APIs to manipulate DOM nodes This adds APIs to allow Ispector clients to: * Change a DOM text or comment node's text data. * Add, replace, or remove a DOM element's attribute. * Change a DOM element's tag.
2023-11-19 10:42:11 -05:00
Attribute.cpp
LibWebView+UI: Rename ChromeProcess to BrowserProcess
2025-03-15 17:00:58 -04:00
BrowserProcess.cpp
LibWebView+WebContent: Implement basic DevTools console support
2025-03-04 08:48:20 -05:00
ConsoleOutput.cpp
Ladybird+LibWebView: Move CookieJar, Database, and History to LibWebView These classes are used as-is in all chromes. Move them to LibWebView so that non-Serenity chromes don't have to awkwardly reach into its headers and sources.
2023-08-31 07:07:07 -04:00
CookieJar.cpp
Database.cpp
LibDevTools+LibWebView+WebContent: Selectively fetch DOM node properties When we inspect a DOM node, we currently serialize many properties for that node, including its layout, computed style, used fonts, etc. Now that we aren't piggy-backing on the Inspector interface, we can instead only serialize the specific information required by DevTools.
2025-03-19 15:50:56 -04:00
DOMNodeProperties.cpp
LibWebView+Services+UI: Move process helpers to LibWebView
2024-11-10 10:26:07 -05:00
HelperProcess.cpp
LibWeb+LibWebView+WebContent: Inform the UI about DOM mutations This will allow our DevTools server to inform the Firefox DevTools client about DOM mutations.
2025-03-06 17:32:43 -05:00
Mutation.cpp
LibWebView+Services+UI: Move the Web plugins to LibWebView
2024-11-10 09:53:15 -05:00
Plugins/FontPlugin.cpp
Plugins/ImageCodecPlugin.cpp
LibWebView+LibCore: Manage process lifecycle using a SIGCHLD handler This large commit also refactors LibWebView's process handling to use a top-level Application class that uses a new WebView::Process class to encapsulate the IPC-centric nature of each helper process.
2024-06-29 22:24:01 -06:00
Process.cpp
LibWebView+Services+UI: Move the Web plugins to LibWebView
2024-11-10 09:53:15 -05:00
ProcessHandle.cpp
Ladybird+LibWebView: Add ProcessManager to track live processes This model will be used to add a Processes tab to the inspector.
2024-03-25 18:29:14 -06:00
ProcessManager.cpp
LibWebView: Define the list of built-in search engines in LibWebView These engines and their query URLs are duplicated in several places. Before implementing search support in the AppKit chrome, let's move these engines to LibWebView.
2023-10-19 15:50:39 -04:00
SearchEngine.cpp
LibWebView+UI: Introduce a persistent settings object This adds a WebView::Settings class to own persistent browser settings. In this first pass, it now owns the new tab page URL and search engine settings. For simplicitly, we currently use a JSON format for these settings. They are stored alongside the cookie database. As of this commit, the saved JSON will have the form: { "newTabPageURL": "about:blank", "searchEngine": { "name": "Google" } } (The search engine is an object to allow room for a future patch to implement custom search engine URLs.) For Qt, this replaces the management of these particular settings in the Qt settings UI. We will have an internal browser page to control these settings instead. In the future, we will want to port all settings to this new class. We will also want to allow UI-specific settings (such as whether the hamburger menu is displayed in Qt).
2025-03-20 12:59:44 -04:00
Settings.cpp
LibWeb+LibWebView+WebContent: Begin implementing simple site islotation Site isolation is a common technique to reduce the chance that malicious sites can access data from other sites. When the user navigates, we now check if the target site is the same as the current site. If not, we instruct the UI to perform the navigation in a new WebContent process. The phrase "site" here is defined as the public suffix of the URL plus one level. This means that navigating from "www.example.com" to "sub.example.com" remains in the same process. There's plenty of room for optimization around this. For example, we can create a spare WebContent process ahead of time to hot-swap the target site. We can also create a policy to keep the navigated-from process around, in case the user quickly navigates back.
2025-03-09 11:40:34 -04:00
SiteIsolation.cpp
LibWebView: Create a method to syntax-highlight page source with HTML This tokenizes a page's source to produce HTML with syntax highlighting. The first implementation here is rather simple; we do not yet implement code folding, line numbers, etc. The goal is for this to be used as the View Source implementation for all Ladybird chromes.
2023-08-28 14:47:29 -04:00
SourceHighlighter.cpp
LibWebView: Add a helper to sanitize a user-provided URL We currently implement several forms of this method across the Ladybird chromes. As such, we see commits to add special URL handling that only affects a single chrome. Instead, let's consolidate all special handling in a single location for all chromes to make use of. This method can handle resolving file:// URLs, falling back to a search engine query, and validation against the Public Suffix List. These cases were gathered from the various chromes.
2023-10-13 09:43:16 -04:00
URL.cpp
Browser+Ladybird: Let the list of user agent strings be shared
2023-09-11 17:49:57 +04:00
UserAgent.cpp
LibWebView+Services+UI: Move process helpers to LibWebView
2024-11-10 10:26:07 -05:00
Utilities.cpp
LibWebView+Ladybird: Begin de-duplicate WebView implementations This starts moving code equally shared between the OOPWV and Ladybird WebContentView implementations to WebView::ViewImplementation, beginning with the client state.
2023-01-12 19:27:17 +00:00
ViewImplementation.cpp
LibWebView: Move OutOfProcessWebView to a new LibWebView library Also moves WebContentClient and the references to the generated IPC descriptions, since they are all components of OutOfProcessWebView. This patch has no functional changes.
2022-04-30 10:46:33 +02:00
WebContentClient.cpp
LibWeb+LibWebView+WebContent: Introduce a WebUI framework When we build internal pages (e.g. about:settings), there is currently quite a lot of boilerplate needed to communicate between the browser and the page. This includes creating IDL for the page and the IPC for every message sent between the processes. These internal pages are also special in that they have privileged access to and control over the browser process. The framework introduced here serves to ease the setup of new internal pages and to reduce the access that WebContent processes have to the browser process. WebUI pages can send requests to the browser process via a `ladybird.sendMessage` API. Responses from the browser are passed through a WebUIMessage event. So, for example, an internal page may: ladybird.sendMessage("getDataFor", { id: 123 }); document.addEventListener("WebUIMessage", event => { if (event.name === "gotData") { console.assert(event.data.id === 123); } }); To handle these messages, we set up a new IPC connection between the browser and WebContent processes. This connection is torn down when the user navigates away from the internal page.
2025-03-24 09:27:36 -04:00
WebUI.cpp
LibWebView: Move OutOfProcessWebView to a new LibWebView library Also moves WebContentClient and the references to the generated IPC descriptions, since they are all components of OutOfProcessWebView. This patch has no functional changes.
2022-04-30 10:46:33 +02:00
)
LibWebView+Services+UI: Move process helpers to LibWebView
2024-11-10 10:26:07 -05:00
if (APPLE)
list(APPEND SOURCES MachPortServer.cpp)
endif()
LibWebView+Services+UI: Move the EventLoop implementations to LibWebView We currently compile the Qt event loop files multiple times, for every target which wants to use them. This patch moves these to LibWebView as a central location to avoid this.
2024-11-10 09:23:10 -05:00
if (ENABLE_QT)
list(APPEND SOURCES
EventLoop/EventLoopImplementationQt.cpp
EventLoop/EventLoopImplementationQtEventTarget.cpp
)
set(CMAKE_AUTOMOC ON)
find_package(Qt6 REQUIRED COMPONENTS Core)
elseif (APPLE)
list(APPEND SOURCES
EventLoop/EventLoopImplementationMacOS.mm
)
endif()
LibWebView+LibPublicSuffix: Merge LibPublicSuffix into LibWebView After d2c7e1ea7db060c1f01a740fab65f3e35a45545b, there is now only one user of LibPublicSuffix - the URL sanitation utility within LibWebView. Rather than having an entire library for the small Public Suffix data accessor, merge it into LibWebView.
2023-10-14 09:07:38 -04:00
set(GENERATED_SOURCES ${CURRENT_LIB_GENERATED})
Meta: Make embed_as_string_view.py produce Strings instead This is only used for CSS style sheets. One case wants it as a String, and the others don't care, but will in future also want to have the source as a String.
2024-08-22 12:42:12 +01:00
embed_as_string(
LibWebView: Add a standard "look like the OS" style sheet It's quite common to want the web-view to match the native OS widgets, so let's make that easy to do.
2023-08-24 11:01:09 +01:00
"NativeStyleSheetSource.cpp"
"${CMAKE_CURRENT_SOURCE_DIR}/Native.css"
"NativeStyleSheetSource.cpp"
"native_stylesheet_source"
NAMESPACE "WebView"
)
LibWebView: Create plumbing for a single UI process This allows main UI processes created while there is a currently running one to request a new tab or a new window with the initial urls provided on the command line. This matches (almost) the behavior of Chromium and Firefox. Add a new IPC protocol between two UI processes. The main UI process will create an IPC server socket, while secondary UI processes will connect to that socket and send over the URLs and action it wants the main process to take.
2024-04-26 15:20:30 -06:00
compile_ipc(UIProcessServer.ipc UIProcessServerEndpoint.h)
compile_ipc(UIProcessClient.ipc UIProcessClientEndpoint.h)
LibWebView+Services+UI: Move process helpers to LibWebView
2024-11-10 10:26:07 -05:00
if (NOT APPLE AND NOT CMAKE_INSTALL_LIBEXECDIR STREQUAL "libexec")
set_source_files_properties(Utilities.cpp PROPERTIES COMPILE_DEFINITIONS LADYBIRD_LIBEXECDIR="${CMAKE_INSTALL_LIBEXECDIR}")
endif()
LibWebView: Move OutOfProcessWebView to a new LibWebView library Also moves WebContentClient and the references to the generated IPC descriptions, since they are all components of OutOfProcessWebView. This patch has no functional changes.
2022-04-30 10:46:33 +02:00
set(GENERATED_SOURCES
LibWebView: Extend GENERATED_SOURCES list instead of replacing
2024-02-23 11:59:11 -07:00
${GENERATED_SOURCES}
Everywhere: Hoist the Libraries folder to the top-level
2024-11-09 12:25:08 -05:00
../../Services/RequestServer/RequestClientEndpoint.h
../../Services/RequestServer/RequestServerEndpoint.h
../../Services/WebContent/WebContentClientEndpoint.h
../../Services/WebContent/WebContentServerEndpoint.h
../../Services/WebContent/WebDriverClientEndpoint.h
../../Services/WebContent/WebDriverServerEndpoint.h
LibWeb+LibWebView+WebContent: Introduce a WebUI framework When we build internal pages (e.g. about:settings), there is currently quite a lot of boilerplate needed to communicate between the browser and the page. This includes creating IDL for the page and the IPC for every message sent between the processes. These internal pages are also special in that they have privileged access to and control over the browser process. The framework introduced here serves to ease the setup of new internal pages and to reduce the access that WebContent processes have to the browser process. WebUI pages can send requests to the browser process via a `ladybird.sendMessage` API. Responses from the browser are passed through a WebUIMessage event. So, for example, an internal page may: ladybird.sendMessage("getDataFor", { id: 123 }); document.addEventListener("WebUIMessage", event => { if (event.name === "gotData") { console.assert(event.data.id === 123); } }); To handle these messages, we set up a new IPC connection between the browser and WebContent processes. This connection is torn down when the user navigates away from the internal page.
2025-03-24 09:27:36 -04:00
../../Services/WebContent/WebUIClientEndpoint.h
../../Services/WebContent/WebUIServerEndpoint.h
LibWebView: Add a standard "look like the OS" style sheet It's quite common to want the web-view to match the native OS widgets, so let's make that easy to do.
2023-08-24 11:01:09 +01:00
NativeStyleSheetSource.cpp
LibWebView: Create plumbing for a single UI process This allows main UI processes created while there is a currently running one to request a new tab or a new window with the initial urls provided on the command line. This matches (almost) the behavior of Chromium and Firefox. Add a new IPC protocol between two UI processes. The main UI process will create an IPC server socket, while secondary UI processes will connect to that socket and send over the URLs and action it wants the main process to take.
2024-04-26 15:20:30 -06:00
UIProcessClientEndpoint.h
UIProcessServerEndpoint.h
LibWebView: Move OutOfProcessWebView to a new LibWebView library Also moves WebContentClient and the references to the generated IPC descriptions, since they are all components of OutOfProcessWebView. This patch has no functional changes.
2022-04-30 10:46:33 +02:00
)
serenity_lib(LibWebView webview)
LibWebView: Integrate the DevTools server into the WebView application This adds a command line option to enable the DevTools server. Here, we make the application the DevToolsDelegate to reply to requests from the DevTools server about the state of the application.
2025-02-15 08:09:47 -05:00
target_link_libraries(LibWebView PRIVATE LibCore LibDevTools LibFileSystem LibGfx LibImageDecoderClient LibIPC LibRequests LibJS LibWeb LibUnicode LibURL LibSyntax)
Meta: Replace Lagom's LibWebView setup with LibWebView's CMakeLists.txt This lets us add new sources to LibWebView in a single location.
2023-08-30 07:27:45 -04:00
LibWebView+Services+UI: Move process helpers to LibWebView
2024-11-10 10:26:07 -05:00
if (APPLE)
target_link_libraries(LibWebView PRIVATE LibThreading)
endif()
CMake: Consistently use imported targets for third party dependencies
2024-06-24 13:08:41 -06:00
# Third-party
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 16:28:35 -04:00
find_package(SQLite3 REQUIRED)
CMake: Consistently use imported targets for third party dependencies
2024-06-24 13:08:41 -06:00
target_link_libraries(LibWebView PRIVATE SQLite::SQLite3)
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 16:28:35 -04:00
LibWebView+Services+UI: Move the EventLoop implementations to LibWebView We currently compile the Qt event loop files multiple times, for every target which wants to use them. This patch moves these to LibWebView as a central location to avoid this.
2024-11-10 09:23:10 -05:00
if (ENABLE_QT)
target_link_libraries(LibWebView PRIVATE Qt::Core)
elseif (APPLE)
target_link_libraries(LibWebView PRIVATE "-framework Cocoa")
endif()
LibWebView+Services+UI: Move the Web plugins to LibWebView
2024-11-10 09:53:15 -05:00
if (HAS_FONTCONFIG)
target_link_libraries(LibWebView PRIVATE Fontconfig::Fontconfig)
endif()
Meta: Guard everything that installs headers with an option
2024-07-20 19:03:24 +02:00
if (ENABLE_INSTALL_HEADERS)
foreach(header ${GENERATED_SOURCES})
get_filename_component(extension ${header} EXT)
if (NOT "${extension}" STREQUAL ".h")
continue()
endif()
Meta: Replace Lagom's LibWebView setup with LibWebView's CMakeLists.txt This lets us add new sources to LibWebView in a single location.
2023-08-30 07:27:45 -04:00
Meta: Guard everything that installs headers with an option
2024-07-20 19:03:24 +02:00
get_filename_component(subdirectory ${header} DIRECTORY)
string(REGEX REPLACE "^\\.\\./\\.\\./" "" subdirectory "${subdirectory}")
Meta: Replace Lagom's LibWebView setup with LibWebView's CMakeLists.txt This lets us add new sources to LibWebView in a single location.
2023-08-30 07:27:45 -04:00
Meta: Guard everything that installs headers with an option
2024-07-20 19:03:24 +02:00
install(FILES "${CMAKE_CURRENT_BINARY_DIR}/${header}" DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}/${subdirectory}")
endforeach()
endif()
Reference in a new issue Copy permalink