Well, I thought about it for a while, really, it wasn't a random decision on a whim.I HIGHLY suggest returning support for this DETECT-string and filling it with real extensions that the plugin can correctly open.
INI file is an integral part of the plugin, so "ini isn't there" is not an option, it's the same as "wlx isn't there". Ini file comes with a predefined set of supported extensions, and you can easily add or modify it. If you don't want to do it, just don't.
The main (or the only?) point of a detect string is to speed up TC a bit: TC checks whether a file is supported using the string, then loads the plugin. If the detect string is empty, it will simply try using the plugin in any case (and the plugin will check whether this extension is supported).
There are two downsides here, though. First, if you want to add a new file type, you'll have to do it twice -- in the main ini file and in the detect string. Second, AFAIK a detect string can't accept directories as an input file type (and this was requested).
There are two error messages. One ("Cannot create WebView2. Error code: blabla") is mine, I can fix that. Another one (don't remember what it says exactly) is shown by Edge itself, and I can't change it AFAIK.BUT!!! Showing a window stating that it is not possible to create a window with "WebView2" class is left.
Well, again, please understand that in this situation we can only rely on MS-supplied functionality. I will add more information into Readme, and I might make a fully standalone version of the plugin. Note, however, that the standalone Edge for each processor architecture is ~200MB zipped (~400MB unzipped, almost 1GB in total if you want to have both 32 and 64 versions).try to deal with the situation when people use only portable versions of the EDGE browser,