ladybird/Ladybird/AppKit
Timothy Flynn 5f8d852dae LibWebView+UI: Migrate Ladybird's command line flags to LibWebView
Currently, if we want to add a new e.g. WebContent command line option,
we have to add it to all of Qt, AppKit, and headless-browser. (Or worse,
we only add it to one of these, and we have feature disparity).

To prevent this, this moves command line flags to WebView::Application.
The flags are assigned to ChromeOptions and WebContentOptions structs.
Each chrome can still add its platform-specific options; for example,
the Qt chrome has a flag to enable Qt networking.

There should be no behavior change here, other than that AppKit will now
support command line flags that were previously only supported by Qt.
2024-08-01 11:38:42 +02:00
..
Application LibWebView+UI: Migrate Ladybird's command line flags to LibWebView 2024-08-01 11:38:42 +02:00
UI LibWebView+UI: Migrate Ladybird's command line flags to LibWebView 2024-08-01 11:38:42 +02:00
Utilities Ladybird/AppKit: Remove system header workarounds for global names 2024-07-18 09:43:38 +01:00
CMakeLists.txt Meta: Create a common Swift settings flow 2024-07-30 18:38:02 -06:00
main.mm LibWebView+UI: Migrate Ladybird's command line flags to LibWebView 2024-08-01 11:38:42 +02:00
module.modulemap Ladybird/AppKit: Port TaskManager window to Swift 2024-07-21 15:55:47 -06:00