The mobile browsers aren't handling table well, when a table has too many columns (sometimes three can still be too many depending on the content in the td cell) the columns got cut off. My tests show that with no width being declared, at Landscape view, a table which has one or two columns have little content (such as an input box or number), usually can show some 3 to 5 columns and the last column which is visible in the view port, some part of it still get cut off, so Landscape view isn't reliable to making sure a tabular layout still be completely visible within the view point.
Enable zooming feature does't fixed the problem; if viewport meta tag isn't declared (no declaration for width=device-width), the table shrinks to half despite the 100% width, though this makes the entire table visible and user can zoom in to view all part of table data - one zoom/swipe at a time. But this really isn't a way to go as it defeats the purpose to having a Mobile version of site. I thought maybe setting auto or visible value for overflow in the table could help that maybe allowing user to scroll horizontally to see entire table. NO help! Maybe it's due to the width=device-width declaration or overflow doesn't work for table or simple browser bug in iOS. I don't know how to solve this except making table into a list, but it seems too way off to convert a structurally collect tabular data to ul list because it's a browser issue. Make me think we are facing some old problems in a new dimension that gone completely wrong. tee ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
