LibWeb: Catch up with the spec on document destroy, abort and unload

These changes do not solve hanging `location.reload()` and `location.go()` but only align implementation with the latest edits in the specification. `WindowProxy-Get-after-detaching-from-browsing-context` test output is affected because `iframe.remove();` no longer synchronously does destruction of a document, but queues a task on event loop. Co-Authored-By: Andrew Kaster <akaster@serenityos.org>
Author: https://github.com/kalenikaliaksandr Commit: 9098fa23a2 Pull-request: https://github.com/SerenityOS/serenity/pull/23786
2025-07-30 04:39:06 +00:00 · 2024-03-31 23:42:51 +02:00 · 2024-03-31 23:42:51 +02:00 · 9098fa23a2 · 2024-07-17 00:16:31 +09:00
commit 9098fa23a2
parent 43752a1ff8
6 changed files with 207 additions and 81 deletions
--- a/Tests/LibWeb/Text/expected/HTML/WindowProxy-Get-after-detaching-from-browsing-context.txt
+++ b/Tests/LibWeb/Text/expected/HTML/WindowProxy-Get-after-detaching-from-browsing-context.txt
@ -1,3 +1,3 @@
 
-null
+
 PASS (didn't crash)