Upload Kmake

This commit is contained in:
Gorochu
2026-05-26 23:36:42 -07:00
parent ba051b2f74
commit 555ec72358
41615 changed files with 13344630 additions and 1 deletions

View File

@ -0,0 +1,5 @@
A couple notes about the files scattered in this `resources/` directory:
* The nested directory structure is necessary here so that relative URL resolution can be tested; we need different sub-paths for each document.
* The semi-duplicate `window-to-open.html`s scattered throughout are present because Firefox, at least, does not fire `Window` `load` events for 404s, so we want to ensure that no matter which global is used, `window`'s `load` event is hit and our tests can proceed.

View File

@ -0,0 +1,4 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>Current page used as a test helper</title>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>If the current settings object is used this page will be opened</title>

View File

@ -0,0 +1,15 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>Incumbent page used as a test helper</title>
<iframe src="relevant/relevant.html" id="r"></iframe>
<iframe src="current/current.html" id="c"></iframe>
<script>
const relevant = document.querySelector("#r");
const current = document.querySelector("#c");
window.runWindowOpenVeryIndirectly = (...args) => {
return current.contentWindow.open.call(relevant.contentWindow, ...args);
};
</script>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>Realm for a host function used as a test helper</title>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>If the function's settings object is used this page will be opened</title>

View File

@ -0,0 +1,24 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>Incumbent page used as a test helper</title>
<script src="/wasm/jsapi/wasm-module-builder.js"></script>
<script src="/wasm/jsapi/functions/helper.js"></script>
<iframe src="relevant/relevant.html" id="r"></iframe>
<iframe src="current/current.html" id="c"></iframe>
<script>
const relevant = document.querySelector("#r");
const current = document.querySelector("#c");
window.runWindowPostMessageVeryIndirectly = (...args) => {
return current.contentWindow.postMessage.call(relevant.contentWindow, ...args);
};
// This tests the backup incumbent settings object stack scenario, by avoiding putting user code on the stack.
window.runWindowPostMessageVeryIndirectlyWithNoUserCode = (...args) => {
const runWindowPostMessage = current.contentWindow.postMessage.bind(relevant.contentWindow, ...args);
call_later(runWindowPostMessage);
};
</script>

View File

@ -0,0 +1,14 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>Relevant page used as a test helper</title>
<script>
// incumbent.html will end up posting a message to here. We need to signal back the "source".
window.onmessage = e => {
const testId = e.data;
const sourceURL = e.source.document.URL;
window.dispatchEvent(new CustomEvent("messagereceived", { detail: [testId, sourceURL] }));
};
</script>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>If the relevant settings object is used this page will be opened</title>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>If the incumbent settings object is used this page will be opened</title>

View File

@ -0,0 +1,3 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>If the entry settings object is used this page will be opened</title>