Re: [css-d] dealing with media breaks
On 3/27/14 7:58 AM, Davies, Elizabeth wrote: When one of the testers come in with a it looks like shit on the Galaxy S3 (or whatever) it's usually a design shortsightedness that we'll address and work at laying out that bit in a better way. This mostly happens because we forgot to be mobile first. We're still learning. Elizabeth; Thank you, I'm very grateful for that mind-bendingly substantial response..I appreciate your going out of your way to spend that kind of time answering my question. I absolutely will do mobile first, next time out..no doubt about it! 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/
Re: [css-d] dealing with media breaks
Lately I've ceased worrying about device media break points and instead I've focused on our grid. Where we determine what the min/max width of a column is. How wide can one base column stretch, how narrow. When does it evolve to 2 columns, 3 columns, etc.. This has simplified the media breaks. Currently heavily investigating use of flexbox in this context, both using the CSS3 for it and the spirit of it depending on what browsers have to be supported. Haven't settled on which of several methods will give us the best performance: flex, calc() with floats, scripting or mix. Overall, going mobile first has also simplified things, including typography (modular scale based on the golden ratio) which only changes once at desktop and again at wall. ELIZABETH DAVIES Input | Intellection | Learner | Achiever | Belief -Original Message- From: css-d-boun...@lists.css-discuss.org [mailto:css-d-boun...@lists.css-discuss.org] On Behalf Of John Sent: Tuesday, March 25, 2014 8:16 PM To: CSS-Discuss Subject: [css-d] dealing with media breaks Are there best practices in dealing with setting up and modifying media breaks and the CSS for each? In the few responsive sites I've worked on, I find myself quickly getting clobbered by the several instances of each style that must be adjusted for each media break. I manage to deal with it, but wondering if others use methods to help keep it all straight as they work, or especially, if they have to come back to the code months later. 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/ All information in this message is confidential and may be legally privileged. Only intended recipients are authorized to use it. __ 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/
Re: [css-d] dealing with media breaks
On Tue, Mar 25, 2014 at 9:16 PM, John j...@coffeeonmars.com wrote: Are there best practices in dealing with setting up and modifying media breaks and the CSS for each? In the few responsive sites I've worked on, I find myself quickly getting clobbered by the several instances of each style that must be adjusted for each media break. I manage to deal with it, but wondering if others use methods to help keep it all straight as they work, or especially, if they have to come back to the code months later. Thank you! John Mobile-first tends to keep repeat styles to a minimum. As your width increases, only change or add rules to deal with layout changes. My base (mobile) styles are heaviest, and sheets for increased widths tend to be extremely light, consisting only of tweaks. Also, I second the idea of content dictating break points, although other people where I work have expectations of where breaks occur, but that's another story... HTH -- Tom Livingston | Senior Front-End Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com __ 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/
Re: [css-d] dealing with media breaks
On Tue, Mar 25, 2014 at 9:16 PM, John j...@coffeeonmars.com wrote: Are there best practices in dealing with setting up and modifying media breaks and the CSS for each? John John. There are a number of methods. You will find the one that works best for you and your clients. As with anything else on the Web, there is no such animal as too much testing before you let the horses out of the gate. Best, David Laakso __ 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/
Re: [css-d] dealing with media breaks
David Laakso wrote: There are a number of methods. You will find the one that works best for you and your clients. As with anything else on the Web, there is no such animal as too much testing before you let the horses out of the gate. Testing can reveal only the presence of bugs, not their absence -- Edsger Dijskstra (11 May 1930 – 6 August 2002) __ 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/
Re: [css-d] dealing with media breaks
mar 26 2014 17:54 Philip Taylor p.tay...@rhul.ac.uk: Testing can reveal only the presence of bugs, not their absence -- Edsger Dijskstra (11 May 1930 – 6 August 2002) Edsger was an avid tester was he? An automated test written to get rid of a specific bug, does indeed prove that this specific bug with the known circumstances does not occur any longer. Obviously it doesn’t prevent unknown bugs or unknown factors. What does? I’m not only a mobile first guy I’m a test-first guy. Using test-first does not imply over-interpretation on what they do. On the contrary, test first design gives a sane outlook on your project. I use Thucydides with jbehave for running specifications against HTML5 views (as well as getting data from server-side). There’s no graphical analysis going on of course, only content evaluations. I’m looking to start javascript testing later. I’m sure css will follow at some point. At the moment it’s too much work for little gain. Or? Device detection is something I imagine I will make tests for sooner rather than later. __ 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/
[css-d] dealing with media breaks
Are there best practices in dealing with setting up and modifying media breaks and the CSS for each? In the few responsive sites I've worked on, I find myself quickly getting clobbered by the several instances of each style that must be adjusted for each media break. I manage to deal with it, but wondering if others use methods to help keep it all straight as they work, or especially, if they have to come back to the code months later. 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/
