Hi Philippe! Thank you so much for your CSS guru help, I greatly
appreciate it. :)
On Thu, Mar 14, 2013 at 7:00 PM, Philippe Wittenbergh <e...@l-c-n.com> wrote:
> I never use these 'screen', 'all', … media types ( OK, I'm lying… I only use
> them when strictly necessary, e.g only when I want the MQ to be really
> limited to a particular media type). I also rarely see the benefit of
> separating screen and print types. But that has more to do with the type of
> documents I deal with most of the time.
Interesting! Thanks for sharing your thoughts on the topic.
Reasoning for my choice (on my this particular project) to have a
separate print style sheet (please correct me if my thinking is
flawed):
1. IIRC, I think I read somewhere that using a separate style sheet
will allow support in older IEs (would the alternative be @media print
{ ... }? Is that the technique you use to keep your print/screen
styles together?).
2. Having built a "mobile-first" theme, I have a lot of media queries
that use "screen and ... ", whereas the mobile styles (outside MQs)
are not set for any media type (they are out in the open). I wanted to
have a "clean slate" for when it came to my print styles and it seemed
like separating screen and print media would help me to do that (I
could be totally wrong though, I'm definitely no print stylesheet
guru).
> So yes, given that your stylesheets are already limited to a particular media
> type, you don't need to repeat that in your MQ's _inside_ those stylesheets.
Awesome! Thanks for the clarification.
So, you're saying I can convert:
@media only screen and (min-width:665px){ ... }
... to:
@media (min-width:665px) { ... }
... that's pretty cool.
Thanks again for the help!!!! I really appreciate it!
Have an awesome night.
Cheers,
Micky
______________________________________________________________________
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/
