[windows] cannot support protocol handlers using awe custom schemes (awv:// etc)

[happybeing]

Tauri v2 does not provide a way for its custom protocol handlers to work with custom schemes (such as awv://) because older versions of Windows only allow http. If Tauri were to drop support for Windows 7/8 that might change, but there are no plans for that in v2 which is at release candidate stage.

There are similar problems with Android due to recent changes to the Chrome webview. Both issues are detailed here tauri-apps/tauri#10667

On Windows, the proposed way to work around this is to translate from the standard scheme to that used by Windows (e.g. using the Tauri convertFileSrc() API) but this is not possible for URLs loaded directly by the iframe used in awe.

Possible remedies to allow support on Windows would be to:

• replace the iframe with something else, such as a Webview, but that may not work if the Chrome changes get in the way of that
• re-implement awe using something other than Tauri, such as Servo assuming that would solve this issue
• change awe to use a Windows compatible custom protocol (such as https://awv.something)

Next

It is probably worth researching how other projects (e.g. ipfs) handle this issue and reviewing options and priorities for a demo and a practical browser.

Pending that, no action is proposed on this issue, which means awe cannot yet be used to view websites on Windows though it should still be capable of publishing websites and other features relying solely on the CLI rather than the GUI.

There is though currently an problem using the awe CLI on Windows in release builds: #1