mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-26 01:35:08 +02:00
LibWeb+WebContent+WebWorker: Move backing store allocation in Navigable
Making navigables responsible for backing store allocation will allow us to have separate backing stores for iframes and run paint updates for them independently, which is a step toward isolating them into separate processes. Another nice side effect is that now Skia backend context is ready by the time backing stores are allocated, so we will be able to get rid of BackingStore class in the upcoming changes and allocate PaintingSurface directly.
This commit is contained in:
committed by
Jelle Raaijmakers
parent
b73525ba0e
commit
082053d781
Notes:
github-actions[bot]
2025-07-04 14:14:12 +00:00
Author: https://github.com/kalenikaliaksandr Commit: https://github.com/LadybirdBrowser/ladybird/commit/082053d7812 Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/5259 Reviewed-by: https://github.com/gmta ✅
@@ -95,7 +95,7 @@ WebIDL::ExceptionOr<void> NavigableContainer::create_new_child_navigable(GC::Ptr
|
||||
document_state->set_about_base_url(document->about_base_url());
|
||||
|
||||
// 7. Let navigable be a new navigable.
|
||||
GC::Ref<Navigable> navigable = *heap().allocate<Navigable>(page);
|
||||
GC::Ref<Navigable> navigable = *heap().allocate<Navigable>(page, false);
|
||||
|
||||
// 8. Initialize the navigable navigable given documentState and parentNavigable.
|
||||
TRY_OR_THROW_OOM(vm(), navigable->initialize_navigable(document_state, parent_navigable));
|
||||
|
||||
Reference in New Issue
Block a user