1. 4
  1.  

  2. 2

    Every Browser has it’s own CSS Reset

    But that’s exactly why you should use a reset. I could be wrong, but I don’t believe there’s a standard on the default CSS that browsers ought to ship with, and so you can’t assume they’re all using the same base. Using a full CSS reset places every browser on the same playing field to ensure that your app/site looks the same in every browser. It does make your CSS structure a tiny bit more complicated, but instead of throwing the baby out with the bath water and removing the full reset, you should focus on simplifying your project’s CSS.

    And now that I’m on this subject, my experience from working on lots of projects is that it hardly makes sense to start a new project by defining styles for global elements in this fashion, anyway. Any assumptions you make up front about what you’ll need for your entire app/site will most likely be wrong. Projects grow and what you need for one page may be completely different than what you need for another. Instead, you should start by styling h1’s, h2’s, p’s, etc. for certain areas of your app, and then only later identify and extract the common pieces to mixins or utility classes or however you want to do that.

    1. 1

      Also why reseting some elements if you are not using them in your project. Example: If you don’t have forms in your project don’t reset them.

      This makes me think there should be a pre-processor tool for including resets only for the HTML you include in your website.

      1. 1

        I was thinking that, but the problem isn’t important enough for the amount of work that would be.