I've been thinking about this off and on for a few weeks now. In my case, I have one image carousel that loads up 18 images. I hid it on narrow screens as it's no where near essential (I'm vying to have it removed completely) but, like you've already stated, that doesn't fix the issue of the user having to download it. In the future, for anything that isn't essential, I'm going to load it via JavaScript after the page has loaded. If it is essential, in the case of a carousel, I'm only going to load what is shown immediately. Once the page content is available, I'll load the other items in the background and add the controls to the carousel.
Just my thought process so far. On Fri, Feb 14, 2014 at 12:42 PM, John Johnson <j...@coffeeonmars.com>wrote: > Let's say for sizes above mobile (ie 600px) you have 2 or 3 jQuery sliders > on a page, but for mobile, you just want 1 slider to be shown. > > my thought is to use CSS to hide the unwanted, but will there still be > just as many HTTP requests, and therefore, should I look to a superior way > to do it so that the load on the mobile device reflects only what the user > sees? > > And what would that better way be? > > Thank you, > > John > ______________________________________________________________________ > css-discuss [css-d@lists.css-discuss.org] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > List policies -- http://css-discuss.org/policies.html > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > -- Chris Rockwell ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
