-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add latest reset/normalize stylesheet to front end? #82
Comments
Decided to go with normalize.css as a base and make a few modifications:
Note: This does mean that if/when |
Were you seeing specific issues in the front-end that a reset stylesheet has solved...? |
@nelsonic Not specifically on time yet as I haven't started putting anything down yet. But in past projects I've found that I end up adding a bunch of reset styles to my stylesheets anyway to help with cross-browser differences, so a reset-type stylesheet has proven to be a useful starting point. |
Done. See: #79, can still be pulled out of the PR. |
What does adding the reset solve...? |
@nelsonic It solves the problem of inconsistencies in base stylesheets across browsers and minimises the amount of CSS we have to write, keeping our code more readable. |
The perceived problem... |
I'm not married to the idea of using a reset stylesheet, but I have found in the past that putting one in solves those 'last remaining bugs' across browsers. |
You're still adding way more than you need to the reset.css. we probably only need 10% of it...
|
I've removed a few more styles we won't need in the latest commit but the leanest way to do it is start with just the obvious ones and then check back into normalize.css when we add new elements to see if any resetting is recommended and make a decision to add it in then. |
So I'd be doubling the codebase in one fell swoop. Not a great idea! |
Investigate alternatives to Eric Meyer's CSS reset and determine whether normalize.css is the way to go.
The text was updated successfully, but these errors were encountered: