CSS is handled by the client. If you want to have the client to not have to download something, the CSS is too late.
AFAIK, there are but two choices: 1) A mobile version of the page/site, users get redirected there based on client and you only load as needed for each client. This has a number of issues: different user experiences, non-portable links, multiple sites to test, etc. but is the easiest way to handle this issue. 2) Have the client determine what is needed and download as necessary. That's "lazy loading", that's Javascript, and while a worthwhile topic and a useful method used more and more lately, it's off-topic here. Solves several of the issues with separate sites, but adds another language, testing, and layer of complexity. Chris On 2/14/14 9:42 AM, "John Johnson" <[email protected]> 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? ______________________________________________________________________ css-discuss [[email protected]] 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/
