Allowing the Player to scale to browser window : bad idea?

I've been playing with the Player settings for a story that was built at 720 x 520 pixels. My native resolution is 1920 x 1200 on a Windows 7 machine. My students will be accessing the course on Mac and Windows machines running a variety of browsers. We are not publishing this content as HTML 5, and if we ever do so, the course will need some revisions to make it mobile friendly anyway.

When I set the Player to scale to fit the browser window (standard Web/SWF output), I'm seeing crisp results in Chrome, Firefox, and IE9, no matter how large or small I make the browser window. This allows me to build courses that I would normally consider optimized for a browser running in a 1024 x 768 (or 1366 x 768) resolution  with no concerns that the any potential students on lower resolutions would be cut off and would have to scroll to see all content.

But I'd like to hear about the potential downside of this kind of scaling. So far, I can list:

1) HTML5 blurriness (as mentioned in this support article). As I mentioned, this course is not going to be published as HTML5 any time soon, so I can forget about this problem for now.

2) Students with high resolutions who also run their browsers maximized could be overwhelmed by ONE HUGE SCARY STORY. I'm thinking I could sell the resizing as a feature, not a bug, and in any opening material, reassure students they can set their browser to any size they find comfortable.

3) One thing I haven't tested yet: what if the Player is displayed within a div, iframe or other block level element within a web page? Would the Player respect the boundaries of that element when maximizing, or would it somehow escape and take over the entire space within the web page? I would assume it would stay within its parent element, but there are enough odd browser issues out there that I'm not even sure if the limited testing I can do on this machine would give me a generalizable answer.

Are there any other known or theoretical pitfalls that I'm missing?


Be the first to reply