It is currently difficult to test the book paging system with the documented dev setup process, since it leads to an origin mismatch. Example error:
BookReaderJSmod.js?sha384-tRcU/HIUEfyWhneEe/mZH2jWZmTAklvq822EcwBK6dXZtynxqfdVFbXt1vlz4HxB:186 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost') does not match the recipient window's origin ('http://localhost:8080').
This has the consequence that the URL bar does not get updated to show the current page, breaking permalinkability.
Should the book paging system preserve nonstandard ports to form the target origin? Or should the dev setup include a proxy to hide the 8080?
Originally posted by @cokernel in #55
It is currently difficult to test the book paging system with the documented dev setup process, since it leads to an origin mismatch. Example error:
BookReaderJSmod.js?sha384-tRcU/HIUEfyWhneEe/mZH2jWZmTAklvq822EcwBK6dXZtynxqfdVFbXt1vlz4HxB:186 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost') does not match the recipient window's origin ('http://localhost:8080').
This has the consequence that the URL bar does not get updated to show the current page, breaking permalinkability.
Should the book paging system preserve nonstandard ports to form the target origin? Or should the dev setup include a proxy to hide the 8080?
Originally posted by @cokernel in #55