ZeroFrame API doesn't work with hyperlinks in web app

Open the site App 0
http://127.0.0.1:43110/1E7wdLyfWBZAJoPtk7t7dxBAdVFDkWpKrX/

Follow its instructions

While browsing ZeroNet in the web app (Chrome should be in a standalone app presentation), go to ThunderWave from there.
http://127.0.0.1:43110/thunderwave.bit/

All hyperlinks shared there, relative and absolute paths, return a null address no matter which browser is selected to open them.
>http://127.0.0.1:43110/thunderwave.bit/null
>Not Found
>null

Glightstar AKA AnthyG thinks it has to do with ZeroFrame API and needs to be reported here.

Whenever SSL arrives so that PWAs can be made, I believe this bug would have to be resolved too.

Reproduce the failure in the ZeroNet web app by following the linked App 0 instructions, opening ThunderWave in Chrome's standalone presentation, and selecting different browsers for relative and absolute hyperlinks. Start at the ZeroFrame API path used for hyperlink handling; done means both link types open their intended addresses instead of resolving to null.

Written by the indexing model from the issue text.