Click here to Skip to main content
15,887,585 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Well, I went to Austin yesterday with my wife's iPad so I could show my dad the progress I've been making on his submarine model, but I found out that being clever 10 years ago has almost completely ruined my ability to navigate the site on a mobile device.

I took steps to make the web page itself not require vertical scrolling with the browser window scroll bars, choosing instead to make the main div scroll instead. This keeps the header area and the footer in view at all times. I found out yesterday that when viewed on the iPad, the div's scroll bar doesn't display at all, so the only content I can see is the content that shows up when the page is initially displayed.

I now have to completely redesign the master page to allow the browser itself to allow scrolling.

And with bandwidth caps and smaller (mobile) screens becoming the norm, I have to rethink the pictures provided on my site. Most are fairly large (800 pixels wide), and with compression, I have them down to about 150K. For tablets, I think I can safely leave them at 800px-wide, but for phones, that's not really practical.

When a web site species a picture to be reduced in size (for example, width="50%"), does it actually re-size the image and send less data to the client, or does it send the image and reduce it for display on the client side?
Posted

1 solution

It sends the full image and the browser resizes it.

"Downsizing a large image with the height and width attributes forces a user to download the large image (even if it looks small on the page). "

http://www.w3schools.com/tags/att_img_width.asp[^]
 
Share this answer
 
v3

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900