v0.5.2

A statement sent as the next package loads is no longer lost

When a page loads one package after another, the previous package can still send an xapi or
finished statement while it is being replaced — a learner's last answer, or the completion
itself. In Chromium, removing the frame's src navigates it to about:blank, and a message from
the document that has just gone arrives with event.source set to null. The element's source
check dropped it, so the statement never reached the page, and no error said so.

The element now accepts such a statement when it names the package that was just replaced, and
stamps it with that package's revision as before. Nothing else from a document that is gone is
accepted. A page that plays one package and stays on it was never affected.

@missing-elements/h5p-embed 0.2.1

The self-hosted embed page, new since 0.5.1: npx @missing-elements/h5p-embed <folder> writes
the /embed page as a static site for a player domain of your own, with the player, the runtime
and the library bundle in it and the policy written as _headers, vercel.json and a <meta>.
See its README.

0.2.1 changes no code; it requires player ^0.5.2, so a site written with it carries the fix
above. A site is built from the player installed when it is written, so an existing player
domain gets the fix only when you write it again and redeploy:

npx @missing-elements/h5p-embed@0.2.1 <folder> --force

Full Changelog: v0.5.1...v0.5.2