Is it possible to only allow downward HTML / flash scaling of a project?

Question

Hi, When I've exported from captivate 7 (latest update) with the "Scalable HTML" option enabled, it creates the output and makes it scale up or down to fit the needs of the device.  The flash version also does the same.  This is working as expected and works well.
However when viewing on a large computer screen, the project looks fuzzy / un-sharp / over-zoomed in because it has increased in size to fill the screen..  Does anyone know of a way in which you can set the project only to scale down, and not to scale up.  For example, we are using 1024 x 672 for Ipad, but if it was on a 7 inch tablet, it would still scale down, but on a larger screen it would retain 1024 x 672.
Essentially, the same functionality as "max-width" and "max height" in CSS.
I imagine it will involve editing some code in HTML / CSS / JS in the output files, I've had a brief look, but haven't gone into depth on it yet.
Any help would be greatly appreciated.
Oen

Answer 1

I understand your dilema.
My point was that if you only served the HTML5 version for mobile, you would never be able to scale over a max width anyway, since the largest screen would be a tablet.
Desktops would be served the SWF version, which is possible to control the max-width since there are only 2 divs you need to worry about and it could still scale down.
It's conceivably possible to do it with the HTML5 version but you would have to write a script to change the css for all divs, the container div and all of it's children and their children and you'd have to run it for every slide. As some of the divs have no id you would also have to create a new id for those divs, or apply a class before you could change their css. You'd probaby have to evaluate which divs have classes, which have inline css, to sum it up it would be a nightmare to write the code. CSS specificity can be confusing enough, let alone trying to figure it out dynamically. If you ever got it to work it would probably take longer than the time it took to build the course, let alone the latency it would introduce.
I'm sure you've noticed that when you apply css rules the the main container div has absolutely no effect in the HTML5 version since the child divs have their own set of rules.