| Age | Commit message (Collapse) | Author |
|---|
|
Always call platform_init after there's a QApplication, because in the
installed configuration that's how we find the resources.
Try QCoreApplication::applicationDirPath() after looking in ./WebContent
for the WebContent process. In an installed configuration, ladybird and
WebContent will both be in $PREFIX/bin.
Add install rules for WebContent and its linked libraries, for if they
ever differ from ladybird's.
|
|
|
|
This makes the JS console usable in new tabs, without having to load
something first.
|
|
This causes CMake to output a WebContent build, without this it would
not build WebContent and Ladybird would be unusable since it couldn't
find the WebContent executable.
|
|
|
|
|
|
While this adds a fair bit of widget code, we're also increasing code
sharing by using the same bits in WebContentClient for interacting with
the JS console.
That said, we should look for more ways to share code here.
|
|
This patch brings over the WebContent process over from SerenityOS
to Ladybird, along with a new WebContentView widget that renders
web content in a separate process.
There's a lot of jank and FIXME material here, notably I had to re-add
manually pumped Core::EventLoop instances on both sides, in order to get
the IPC protocol running. This introduces a lot of latency and we should
work towards replacing those loops with improved abstractions.
The WebContent process is built separately here (not part of Lagom) and
we provide our own main.cpp for it. Like everything, this can be better
architected, it's just a starting point. :^)
|
|
|
|
This matches the changes made to Serenity in:
https://github.com/SerenityOS/serenity/commit/7a2da4cabf5627941cf1fc6eb7c5fd068fcc75f9
|
|
This should help IDEs have an easier time indexing serenity files.
|
|
This allows installed ladybird and Andriod ladybird to find the content
filters without copying all of Base/home/anon into the install tree.
|
|
size() may include the dimensions of the scrollbars, so we now use
viewport() instead.
|
|
|
|
|
|
|
|
|
|
View Source was a subwindow which made it cover part of the browser with
no way for closing it.
|
|
...not part of the WebView. Its lifetime is managed by a QPointer.
|
|
|
|
This prevents memory leaks detected by both Valgrind and ASAN/LSAN.
Valgrind is still suspicious of the leaked JS::VM from
Web::Bindings::main_thread_vm() but there's other issues with leak
checking all the GC'd objects.
Co-Authored-By: Diego Iastrubni <diegoiast@gmail.com>
|
|
|
|
For the first cut, the file path is not configurable and the content
filter cannot be toggled on or off. If we fail to apply the content
filters for any reason (e.g. the filter file doesn't exist), we simply
just stop loading the content filters to allow using Ladybird without
content filters.
|
|
See https://github.com/SerenityOS/serenity/commit/4230dbbb21ec68cbb9844130d5e90276c96d16c2
|
|
|
|
'group' is not very specific.
|
|
We use a ModelTranslator to expose a DOMTreeModel from LibWebView :^)
It allows you to select the currently inspected node, which causes
the engine to render a little box model overlay above the web content.
|
|
This will be used to expose the DOMTreeModel from LibWebView :^)
|
|
This will allow us to share code with LibWebView from SerenityOS.
(This would otherwise not work, since its "WebView" namespace collides
with our "WebView" class.)
Also, we should eventually move towards a more sophisticated
multi-process WebView like OOPWV.
|
|
Qt has this feature built-in, so there's no need to create a custom
implementation
|
|
|
|
This blocks us from removing it upstream in LibWeb.
|
|
|
|
This makes sure that any console.log (and friends) called before ever
opening the JS Console are not lost.
|
|
|
|
Remove release build info, as per request of @bgianfo
|
|
library path for easier reference and finding.
|
|
closes #49
|
|
There are a lot of unsupported mouse click events that the engine
cannot handle. It such event (0) reaches the web engine - it will
assert.
Don't even propagate them - this is the safe way. As of today!
I also added back/forward buttons to the translation.
Should fix #27
|
|
|
|
|
|
|
|
And rename it to PageClientLadybird while we're at it, it's not
"headless" by any means.
|
|
|
|
|
|
This commit changes how we set the back and forward button key bindings
to use platform-specific standard key sequences.
For example, in Mac OS X, the back action will be now triggered via
Cmd+← and Cmd+[, whereas previously the action was mapped to Alt+←,
which is not standard in Mac OS X.
|
|
|
|
|
|
|
|
This makes #foo links actually scroll the #foo element into view.
|
