Symbols

Bugs/Feature Requests

Known Issues

More about UNC path support

Turning off the UNC paths transformation might be seen as a
​security measure
and if someone can demonstrate that this feature presents
a security risk, I'll disable it by default in future releases.
But here, the "file:" links are user-oriented and can't possibly be embedded
in a <img> tag or Javascript code, so I don't really see what could be the risk,
and I think it's OK to enable this feature by default.

Firefox doesn't do anything with the file: links, but
users can use the ​LocalLink plugin
(​install).

Alternatively, I use the "Open Link in Ext.App." contextual menu entry provided
by the ​IETab plugin
(​install),
and this works great.

Chrome has also its own ​LocalLinks plugin, which was modeled after the Firefox extension.

Local Paths

Using IETab within Firefox even allows you to use links local paths
(say, S:\Public\File.txt) by using the equivalent UNC path \\?\S:\Public\File.txt,
which is recognized as a link by the plugin and will be opened correctly by IETab
"Open Link in Ext.App.".
Note that S:\Public\File.txt itself isn't recognized as a link (and probably
will never be, as that will conflict with one letter InterTrac prefixes) and
that the file:///?/ file link produced by the plugin are not
understood by IE7 or IETab plugin "Open Link in IE Tab" (I haven't tested the LocalLink plugin).