And when I run the script below (the only difference being that the process is now chrome.exe), I get the same neat result in Chrome. Three tabs in the same window.
… the URLs open up in three separate windows in Internet Explorer.
I know it’s almost a moot point, since Internet Explorer is about to retire, but please indulge me. Is there a way to fix this script so that I can get the same results in Internet Explorer as I do in Edge or Chrome? Or do we just chalk it up to Explorer not being controllable that way?
Before today I had no idea what a ComObject was, I had no idea what the navigate2 method was, and I had no idea what a flag was.
The thing that I still find irritating is that I can’t find any documentation on what the flag values actually mean, or the logic from which they are derived. I just had to take for granted that 0x0800 is the value that will make the URL open in a new tab. But, I mean, why? Like, why is the x sitting right there between those two 0s, for example?
Anyway, thank you for steering me in the right direction (even if in a couple of weeks this solution will be purely academic).
Hey hey … cool. And thanks for sharing your solution.
Since creating a good, complete and comprehensive documentation is a lot of work on the one side and no glory in it on the other it’s very often neglegted.
Of course I do not know the meaning of the flag but an “x” at this position of a number means that it is a hex number. So in decimal format it would be 2048.
Oh my goodness, thank you! I kept seeing those two numbers in reference to the same method parameter and spent much too long wondering if one was for an older version of Internet Explorer or… or something. Good to know!