In the "for what it's worth" category while reading this thread, I thought I'd pass on a possible solution....and for those of you who have strong programming backgrounds, you'll recognize this as a major HACK, but from my perspective, having done this for other clients, it was the best I could do given that PowerPoint doesn't support window control at all.
I'm about to dive into some technical territory here, so I'm going to ask you to take this w/ a grain of salt....mostly b/c I don't think I'll be able to explain this entirely (or correctly at this time of night) and I'm sure someone out there will find some level of fault with the following.....so here goes.
This is a 2 part solution and I'm going to provide all the code I use in this process. Part one is defining the script that will execute when called and part 2 will include the function call on the HTML page that will load the external content.
Open Notepad and add the following:
Save this doc as launchModule.js
Part 2: Calling the script from your HTML page
On the HTML page that you're looking to connect to from your Presenter content, place this line of code before the closing </head> tag:
Save the HTML file and shut it down.
Okay so what did we just do?
Simple: the javascipt document contains a simple function that tells an open window to resize based on some variables that are defined within it. In this case, I set mine to 452 x 440. You can't control chrome elements this way (meaning the address bar, toolbars scrollbars and all that jazz), but you can absolutely define the scope of the open window, which in my case, was enough to do the job. From there, a reference to the script is needed at the HTML ducument level, so that the opening HTML page knows what to do and thus respond to the script accordingly.
I'd be happy to provide working examples if you'd like; just drop me a line at firstname.lastname@example.org.
That said, let's talk about some OBVIOUS caveats with this approach.
ONE: if you're trying to target an html page that you don't have any control over...like the index page of ABC company for example....then you're screwed. No control = no control over the experience you're looking to create.
TWO: this approach still doesn't address denito's earlier post about launching a SINGLE web page stemming from different links in a deck. But there's nothing stopping you from creating a single "landing" page which then can lead to additional content. It ain't the cleanest approach, but then again I did stipulate that this was a hack!
Having said all this, my personal belief is that we need to keep the learning experience as painless and seamless as possible for learners. Additional distractions, multiple navigation threads, and the like, all add up to a boat-load of problems for folks and the last thing we want is disgruntled, frustrated learners. So....don't know if this helps at all, but just thought I'd weigh in on it.