You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware that the current implementation of the (TAO Advance) test-runner requires the PCI to provide a single, bundled JS file as an entrypoint.
A PCI we created earlier depends on content, which is provided by a third-party runtime which is rendered via <iframe> while communicating with the host pci via PostMessage. In the previous test runner engine, this was possible due to the fact that a PCI could bring it's own resources and reference them by using the TAO AssetManager.
Unfortunately, the third-party runtime depends on certain internal files & directories to be present and therefore cannot be bundled into the PCI directly. As a workaround for the current system, we were considering to prepare a ServiceWorker (SW) which includes these external resources to make them available to the PCI via relative URLs.
This SW would run in it's own scope and would be disposed of with the "onCompleted" event.
Problem is:
the nature of how SWs are created requires an URL to a js-file containing the SW-code.
Providing a "blob:" or "data:" URL to the navigator.serviceWorker.register() function is restricted by W3C due to security concerns.
To cut a long story short:
Is there a workaround or configuration in the imsPciCreator.json, to include and reference a single additional sourcefile?
Thanks & kind regards,
Felix
The text was updated successfully, but these errors were encountered:
Dear team,
I'm aware that the current implementation of the (TAO Advance) test-runner requires the PCI to provide a single, bundled JS file as an entrypoint.
A PCI we created earlier depends on content, which is provided by a third-party runtime which is rendered via <iframe> while communicating with the host pci via PostMessage. In the previous test runner engine, this was possible due to the fact that a PCI could bring it's own resources and reference them by using the TAO AssetManager.
Unfortunately, the third-party runtime depends on certain internal files & directories to be present and therefore cannot be bundled into the PCI directly. As a workaround for the current system, we were considering to prepare a ServiceWorker (SW) which includes these external resources to make them available to the PCI via relative URLs.
This SW would run in it's own scope and would be disposed of with the "onCompleted" event.
Problem is:
the nature of how SWs are created requires an URL to a js-file containing the SW-code.
Providing a "blob:" or "data:" URL to the navigator.serviceWorker.register() function is restricted by W3C due to security concerns.
To cut a long story short:
Is there a workaround or configuration in the imsPciCreator.json, to include and reference a single additional sourcefile?
Thanks & kind regards,
Felix
The text was updated successfully, but these errors were encountered: