Only this group's mentor and creator can set the rules. Because this group IS a forum for discussing CSS it seems right to limit fine-grained how-to-do-it discussion to CSS only. But the use of CSS in the real world invariably happens in a context that almost always includes a mixture of technologies including databases, server side scripting and javascript. So at higher big picture level some discussion about how CSS fits into the overall scheme of things still seems appropriate.
Using Javascript cookies and (initially) a double GET to determine the state of the current user agent makes the most sense to me--so custom CSS, custom image sizes and even custom HTML can be sent back down the pipe. CSS only "mobile first" approaches violate basic theory of programming rules because mobile first inescapably couples itself to both small mobile displays plus the vastly different requirements of bigger desktop displays. Writing codes with semi-secret two role agendas is seldom a good idea. On Mon, Feb 17, 2014 at 9:48 AM, Chris Williams <ch...@clwill.com> wrote: > Which is precisely what I suggested as one of the two alternatives: use > JS to serve up content based on screen size. > > On 2/17/14 12:27 AM, "MiB" <digital.disc...@gmail.com> wrote: > > > > >Javascript analysis of screen type ... > > ______________________________________________________________________ > 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/ > -- /* Colin (Sandy) Pittendrigh >--oO0> */ ______________________________________________________________________ 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/
