When javascript is disabled the fallback does not kick in. It appears this is attempted to be loaded into <app-root> by angular, which wouldn't work if javascript weren't available.
If this were loaded in with the <app-root> html, it would create a form. However this form still uses variables parsed by angular, and so it would need to be customized when installed.
But even if that were the case, this form relies on javascript to construct the URL for Primo.
I think there isn't a way around this without relying on server-side code, which would be outside the scope of this project.
When javascript is disabled the fallback does not kick in. It appears this is attempted to be loaded into
<app-root>by angular, which wouldn't work if javascript weren't available.If this were loaded in with the
<app-root>html, it would create a form. However this form still uses variables parsed by angular, and so it would need to be customized when installed.But even if that were the case, this form relies on javascript to construct the URL for Primo.
I think there isn't a way around this without relying on server-side code, which would be outside the scope of this project.