4 ms·
Can someone suggest good resources for debugging CSS? I found that most of the time either you know why something works or you do not. I have not seen a resourc
by 3into10power5 8y ago
Can someone suggest good resources for debugging CSS? I found that most of the time either you know why something works or you do not. I have not seen a resource which says, "This box is placed here because this other box is 50px and there is no more place on this row." or "This box is next to this box because there is a float:right on it" etc. Basically, I am looking for a "log" showing the browser's decisions.
Some people seem to get this instinctively, but for some backend engineers like me, CSS has been a nightmare.
- godot 8y agoI'm actually legitimately curious too. I'm a backend dev now, but I started working with CSS and frontend since early 00s and that's the only reason I know many of those things. For newer devs coming into web now, I have no idea how one would learn CSS quirks easily.
- hackermailman 8y agoI've mostly cheated by using CSS preprocessors like Sylus (http://stylus-lang.com http://stylus-lang.com ) or Sass to avoid page rendering surprises, and a postprocessor like PostCSS to optimize and not worry if certain latest modules have multi browser support. A survey of these things here if interested: https://www.mdpi.com/2078-2489/9/1/17/htm https://www.mdpi.com/2078-2489/9/1/17/htm I also once read through this thesis, to understand how the rule overrides work and other problems in CSS, but gave up keeping with the new standards and switched to preprocessors https://www.wiumlie.no/2006/phd/#ch-problems https://www.wiumlie.no/2006/phd/#ch-problems