Paul,

It involves skullduggery with MSHTML rendering engine and COM interfaces,
rather than iexplore.exe running.

I already expected an answer like that. :-(

Yes, I'm quite aware that much of what the user sees is not actually
performed by the program he started. But does that matter in regard to the
question I asked ? I don't think so.

The only thing you've shown me is that:

a) You have not actually read the question -- It's not about who does it,
but about where its initiated and that I do not want it to happen.

b) you're (trying to be) a pedantic asshole. Not actually contributing to
anything (much less to an answer), but just tring to pick a fight (worth
nothing, no matter whomever "wins" it).

Goodbye. I can use my time and energy *way* better. By picking my nose for
example. Or watching paint dry.

Regards,
Rudy Wieser


-- Origional message:
"Paul" wrote in message
news
R.Wieser wrote:
Paul,

Searching in the address bar, was a function specific to Internet
Explorer
(which is not the same thing as File Explorer).

I'm rather amazed by that above statement, as your own experiments you
posted a bit lower down prove the opposite.

Quote:

As an experiment, on WinXP SP3 with IE6, I typed "http:www.sun.com" into the File Explorer bar at the top, and it opened IE6 *in the same window*

You can't have it both ways.

Regards,
Rudy Wieser

A theory, for your consideration.

https://s26.postimg.org/ny1bn5yk9/explorer_info.gif

It involves skullduggery with MSHTML rendering engine and COM
interfaces, rather than iexplore.exe running. Explorer.exe
is using COM to get to MSHTML and render something. If the
European Union insists that iexplore.exe be removed,
Microsoft leaves the MSHTML part (the "engine"), because it
supports such functions as HTML help.

Paul