This is a slight problem, which probably affects no one but me. I am in the midst of a large project where it's all about the web object as my "interface within a runtime" project, and I've run across an incorrect behavior of the web object.
Many of the graphics I have loading into the web object are so large that IE and/or Firefox need to scale these down upon loading so that the entire viewable area is in the window. Each of these browsers gives you zoom tool when you hover over the image.
AMS doesn't do this via the web object. I think it should.
The images load fine, but they are so large due to not being scaled automatically, that the user can simply miss it altogether as they are just seeing a corner of the actual viewable area.
Since the web standard is to provide a simple solution via the auto scale/magnifying glass cursor trick, I think it should be part and parcel of the web object's behavior in AMS. Who's with me?
Many of the graphics I have loading into the web object are so large that IE and/or Firefox need to scale these down upon loading so that the entire viewable area is in the window. Each of these browsers gives you zoom tool when you hover over the image.
AMS doesn't do this via the web object. I think it should.
The images load fine, but they are so large due to not being scaled automatically, that the user can simply miss it altogether as they are just seeing a corner of the actual viewable area.
Since the web standard is to provide a simple solution via the auto scale/magnifying glass cursor trick, I think it should be part and parcel of the web object's behavior in AMS. Who's with me?
Comment