"Evertjan." <***@inter.nl.net> wrote
| > Note that the posted link is not compatible with IE 11 or Edge. Use
| > another browser or an earlier version of IE.
| Indeed, Edge has no VBScript or HTA, that's why it is called Edge.
I think he meant my webpage, not the download. But
one can use IE11 with IE compatibility set. Or people can
disable style and fish through the resulting layout, if they
want to. The "dysfunction" is meant to be just courtesy
information because IE11-Edge-mode and Edge can't handle
my IE-targetted menus, so they can't navigate the site.
It's beyond me why anyone would choose to use an
incompatible, spyware browser from Microsoft that's been
designed to break compatibility *with itself*, but it's really
none of my business as long as I don't have to spend time
writing new webpages to accommodate it.
The other glaring problem with Edge is that it's Win10-only
and thus updates with Win10. So how does one test pages
on Edge? Buy a Win10 box to run each Win10 update over
at least the past 18 months, which would mean 3 of them.
Fat chance of that.
But the news is that Edge is going to change to a
Chrome clone. Microsoft want to be able to support
going to start by making a conforming browser. (Then,
no doubt, they'll add their own incompatible tools.
ActiveX redux.) Good riddance to them. But if they
remake Edge as Chrome and fully spoof the userAgent
then they can access my non-IE version of my website.
That would be fine. If it doesn't work it will be their
Currently they take a curious approach: IE11 in Edge
mode and Edge both use a spoof to pretend they're Chrome
or Firefox. MS took out the "MSIE" that everyone depended
on to identify IE. But MS still left info identifying both IE11
and Edge uniquely. And if IE11-compat-with-IE mode is set,
the userAgnt says it's IE7.