On Aug 5, 2010, at 4:23 PM, David Storey wrote: > > Not strictly true. First of all Opera Mini compresses the content and images > (which is one of the reasons for the image quality setting - it will compress > it less on high setting) to optimise it for low bandwidth devices. Opera (in > general) also doesn't load resources that are set to display: none; until > they are set to show on the page.
Hi David, This is interesting but I am not sure I fully understand it. Compression this I understand, but not loading the display none part. Are you saying that Opera Mini able to exclude inline elements in the markup that are declared display none in the style sheet. If so, I would like to learn more the technical aspect how Opera Mini does it. If David L display none his 170kb inline image, Opera Mini will not load that 170kb or whatever reduced size that is after the compression? When I did my final assignment for the Mobile Web Best Practices course I mentioned, I needed to make a page (a WordPress blog) stay within 10k file size, it was more than a challenge having to watch over every byte in a dynamic page. I first used the media queries, "display:none" side column items (e.g., tags, archives, recent comment and inline image etc...) that I wanted to exclude in mobile version. Visually I get the result I wanted, but as far as markup and file sizes are concerned, they were still there in the source code. I tested the page over MobileOK Checker, the validator picked them up too, and that is how I concluded without some sort of content negotiation (along with other more aggressive methods), media queries is just a very nice idea for mobile version of site without much practical use, unless, we don't care at all optimization. tee ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
