LibWeb: Use VM helpers for execution context access

Inline JS-to-JS frames no longer live in the raw execution context
vector, so LibWeb callers that need to inspect or pop contexts now go
through VM helpers instead of peeking into that storage directly.

This keeps the execution context bookkeeping encapsulated while
preserving existing microtask and realm-entry checks.
This commit is contained in:
Andreas Kling
2026-04-13 12:49:53 +02:00
committed by Andreas Kling
parent 9af5508aef
commit 88d4d1b1a6
Notes: github-actions[bot] 2026-04-13 16:31:11 +00:00
6 changed files with 13 additions and 14 deletions

View File

@@ -604,6 +604,7 @@ void EventLoop::perform_a_microtask_checkpoint()
// NOTE: This assertion is per requirement 9.5 of the ECMA-262 spec, see: https://tc39.es/ecma262/#sec-jobs
// > At some future point in time, when there is no running context in the agent for which the job is scheduled and that agent's execution context stack is empty...
VERIFY(vm().execution_context_stack().is_empty());
VERIFY(!vm().has_running_execution_context());
// 2. Set the event loop's performing a microtask checkpoint to true.
m_performing_a_microtask_checkpoint = true;