ladybird/Tests/LibWeb/Text/input/navigation/remove-iframe-from-timeout-callback.html

<script src="../include.js"></script><div id="foo"><iframe></iframe><script>
    setTimeout(function () {
        foo.remove();
        window.done = true;
    }, 0);
</script></div><iframe></iframe><script>
    asyncTest(function (done) {
        let internalId;
        internalId = setInterval(function () {
            if (window.done) {
                clearInterval(internalId);
                done();
            }
        }, 0);
    });
</script>PASS: did not crash
LibWeb: Fix endless spinning in apply_the_history_step() While waiting for a task that populates a session history entry, we can't limit the processing of the event loop to the `NavigationAndTraversal` task source. This is because fetching uses the `Networking` task source, which also needs to be processed. Since making a fetch request might take some time, we want to process everything on the event loop while waiting, to avoid blocking user interactions. It is still possible to use `spin_processing_tasks_with_source_until()` on subsequent steps of `apply_the_history_step()`. Also modifies test that was flaky. 2024-03-25 19:08:27 +01:00			`<script src="../include.js"></script><div id="foo"><iframe></iframe><script>`
			`setTimeout(function () {`
			`foo.remove();`
			`window.done = true;`
			`}, 0);`
			`</script></div><iframe></iframe><script>`
			`asyncTest(function (done) {`
			`let internalId;`
			`internalId = setInterval(function () {`
			`if (window.done) {`
			`clearInterval(internalId);`
			`done();`
			`}`
LibWeb: Run only tasks with navigation source in "apply history step" In our implementation of the "apply the history step" algorithm, we have to spin-wait for the completion of tasks queued on the event loop. Before this change, we allowed tasks from any source to be executed while we were waiting. It should not be possible because it allows to interrupt history step application by anything, including another history step application. Fixes https://github.com/SerenityOS/serenity/issues/23598 2024-03-20 15:41:45 +01:00			`}, 0);`
LibWeb: Fix endless spinning in apply_the_history_step() While waiting for a task that populates a session history entry, we can't limit the processing of the event loop to the `NavigationAndTraversal` task source. This is because fetching uses the `Networking` task source, which also needs to be processed. Since making a fetch request might take some time, we want to process everything on the event loop while waiting, to avoid blocking user interactions. It is still possible to use `spin_processing_tasks_with_source_until()` on subsequent steps of `apply_the_history_step()`. Also modifies test that was flaky. 2024-03-25 19:08:27 +01:00			`});`
			`</script>PASS: did not crash`