Disappearing Frame Origin

We constructed an example which clarified strange behavior in wiki frames. Frames are now consistently placed in a null origin for every page load. Dear Reader, you will likely find the prose in the page confusing as the fixed behavior of the examples no longer match the original behavior.

Here we construct another example. It works when the page first loads. window.origin is defined in this case.

Clicking the reload button triggers a reload of the frame. window.origin is null in this case. We don't understand why origin would be null after reload. But the null origin causes a CORS error to prevent the graphviz-viewer.js from loading.

We double-check our assumptions.

When the page loads, a simple graphviz graph is drawn within the frame. But when we instruct the browser to reload only the frame, the graph is not drawn and we find CORS errors in the browser console.

We've copied the original frame item here. To test the behavior, try right-clicking (or two-finger clicking, or ctrl-clicking, as appropriate for your device) to summon a context menu & choose therein the "Reload Frame" command.