Web Bundles that don't have an origin? about webpackage HOT 3 CLOSED

I think the question is for "navigate-to-bundle" case. Although a web bundle format itself supports "a relative URL", I don't think that works for "navigate-to-bundle" case, where an absolute URL is required to make the navigation work.

@irori Do you have any insights? I think the answer would be "Unfortunately, a dummy absolute URL is required"...

from webpackage.

Thanks for your reply! Yes, this is in reference to the "navigate-to-bundle" case. If a special value/protocol/tld is unlikely to be created, then perhaps best practice could be to use .example as the TLD? It is apparently reserved:

By publication of RFC 2606 in 1999, the Internet Engineering Task Force reserved the DNS labels example, invalid, localhost, and test so that they may not be installed into the root zone of the Domain Name System.

The reason for reservation of these top-level domain names is to reduce the likelihood of conflict and confusion.[1] This allows the use of these names for either documentation purposes or in local testing scenarios.

https://en.wikipedia.org/wiki/.example

Although on second thought .example might be a bit confusing because it implies that it should be replaced with a "real" value. Something like http://webbundle/foo.html (similar to localhost usage) might be ideal? Not sure if that's a valid URL though.

from webpackage.

[Issue Triage]

It seems we can close this issue, in favor of #763.

from webpackage.