normalize-scss 2.1.2

checksums.yaml

@@ -0,0 +1,7 @@
+--- 
+SHA1: 
+  metadata.gz: 6dcd0d6dd7892ffe004c010df93a5459d6c92b48
+  data.tar.gz: 14dee99f3b13a462733a3f1636b7ad66596962d4
+SHA512: 
+  metadata.gz: f2bbe7803dd20275d3b8ef92cc195614f4a1af5816bb9d6776a39df8454497e6f1063222c4644a63ae9fd1824fef5d39f5c286b71594cd076624fd7cc0ecd3a8
+  data.tar.gz: 99721a8fb6691fcf0a0c0794adbb0e5f256658b45afdcb0ca0938a86626b0055b22da667eeb5f293896103b5cd609aaff9b54d8febe5940c47a31404113d75da

data/CHANGELOG.md

@@ -0,0 +1,69 @@
+== HEAD
+
+== 2.1.2 (May 11, 2013)
+
+* Revert root `color` and `background` normalizations.
+
+== 2.1.1 (April 8, 2013)
+
+* Normalize root `color` and `background` to counter the effects of system
+  color schemes.
+
+== 2.1.0 (January 21, 2013)
+
+* Normalize `text-transform` for `button` and `select`.
+* Normalize `h1` margin when within HTML5 sectioning elements.
+* Normalize `hr` element.
+* Remove unnecessary `pre` styles.
+* Add `main` element to HTML5 display definitions.
+* Fix cursor style for disabled button `input`.
+
+== 2.0.1 (August 20, 2012)
+
+* Remove stray IE 6/7 `inline-block` hack from HTML5 display settings.
+
+== 2.0.0 (August 19, 2012)
+
+* Remove legacy browser form normalizations.
+* Remove all list normalizations.
+* Add `quotes` normalizations.
+* Remove all heading normalizations except `h1` font size.
+* Form elements automatically inherit `font-family` from ancestor.
+* Drop support for IE 6/7, Firefox < 4, and Safari < 5.
+
+== 1.1.2 (May 11, 2013)
+
+* Revert root `color` and `background` normalizations.
+
+== 1.1.1 (April 8, 2013)
+
+* Normalize root `color` and `background` to counter the effects of system
+  color schemes.
+
+== 1.1.0 (January 21, 2013)
+
+* Normalize `text-transform` for `button` and `select`.
+* Normalize `hr` element (excluding IE 6/7).
+* Add `main` element to HTML5 display definitions.
+* Fix cursor style for disabled button `input`.
+
+== 1.0.2 (November 17, 2012)
+
+* Correct `h6` font size normalization.
+
+== 1.0.1 (August 19, 2012)
+
+* Adjust `small` font size normalization.
+
+== 1.0.0 (August 14, 2012)
+
+(Only the notable changes since public release)
+
+* Add MIT License.
+* Hide `audio` elements without controls in iOS 5 (#69).
+* Normalize heading margins and font size.
+* Move font-family normalization from `body` to `html` (#62).
+* Remove scrollbar normalization (#64 #65).
+* Remove excess padding from checkbox and radio inputs in IE 7 (#42).
+* Add IE9 correction for SVG overflow (#16).
+* Add fix for legend not inheriting color in IE 6/7/8/9.

data/CONTRIBUTING.md

@@ -0,0 +1,177 @@
+# Contributing to normalize.css
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of
+the developers managing and developing this open source project. In return,
+they should reciprocate that respect in addressing your issue or assessing
+patches and features.
+
+
+## Using the issue tracker
+
+The issue tracker is the preferred channel for [bug reports](#bugs),
+[features requests](#features) and [submitting pull
+requests](#pull-requests), but please respect the following restrictions:
+
+* Please **do not** use the issue tracker for personal support requests.
+
+* Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others.
+
+
+<a name="bugs"></a>
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** – check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** – try to reproduce it using the
+   latest `master` branch in the repository.
+
+3. **Isolate the problem** – create a live example (e.g., on
+   [Codepen](http://codepen.io)) of a [reduced test
+   case](http://css-tricks.com/6263-reduced-test-cases/).
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? What would you expect to be the outcome? All these
+details will help people to fix any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the browser/OS environment in which it occurs. If
+> suitable, include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the reduced test case
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+
+
+<a name="features"></a>
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to *you* to make a strong
+case to convince the project's developers of the merits of this feature. Please
+provide as much detail and context as possible.
+
+
+<a name="pull-requests"></a>
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant work, otherwise you
+risk spending a lot of time working on something that the project's developers
+might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (whitespace,
+accurate comments, etc.) and any other requirements (such as test coverage).
+
+Follow this process if you'd like your work considered for inclusion in the
+project:
+
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
+   and configure the remotes:
+
+   ```bash
+   # Clone your fork of the repo into the current directory
+   git clone https://github.com/<your-username>/normalize.css
+   # Navigate to the newly cloned directory
+   cd normalize.css
+   # Assign the original repo to a remote called "upstream"
+   git remote add upstream https://github.com/necolas/normalize.css
+   ```
+
+2. If you cloned a while ago, get the latest changes from upstream:
+
+   ```bash
+   git checkout master
+   git pull upstream master
+   ```
+
+3. Never work directly on `master`. Create a new topic branch (off the latest
+   version of `master`) to contain your feature, change, or fix:
+
+   ```bash
+   git checkout -b <topic-branch-name>
+   ```
+
+4. Commit your changes in logical chunks. Please adhere to these [git commit
+   message conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+   or your code is unlikely be merged into the main project. Use Git's
+   [interactive rebase](https://help.github.com/articles/interactive-rebase)
+   feature to tidy up your commits before making them public.
+
+   Make sure to add a test to the `test.html` file if appropriate, and test
+   your change in all supported browsers.
+
+5. Locally rebase the upstream development branch into your topic branch:
+
+   ```bash
+   git pull --rebase upstream master
+   ```
+
+6. Push your topic branch up to your fork:
+
+   ```bash
+   git push origin <topic-branch-name>
+   ```
+
+10. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+    with a clear title and description.
+
+    Please submit a separate pull request for any appropriate changes required
+    in the `v1` branch for legacy browsers.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
+license your work under the same license as that used by the project.
+
+
+<a name="maintainers"></a>
+## Maintainers
+
+If you have commit access, please follow this process for merging patches and
+cutting new releases.
+
+### Accepting patches
+
+1. Check that a patch is within the scope and philosophy of the project.
+2. Check that a patch has any necessary tests and a proper, descriptive commit
+   message.
+3. Test the patch locally.
+4. Do not use GitHub's merge button. Apply the patch to `master` locally
+   (either via `git am` or by checking the whole branch out). Amend minor
+   problems with the author's original commit if necessary. Then push to GitHub.
+5. If a patch should be included in `v1`, cherry-pick the commits or manually
+   apply if all else fails.
+
+### Releasing a new version
+
+1. Include all new functional changes in the CHANGELOG.
+2. Use a dedicated commit to increment the version. The version needs to be
+   added to the CHANGELOG (inc. date), and the `bower.json`, `component.json`,
+   and `normalize.css` files.
+3. The commit message must be of `v0.0.0` format.
+4. Create an annotated tag for the version: `git tag -m "v0.0.0" v0.0.0`.
+5. Push the changes and tags to GitHub: `git push --tags origin master`
+6. Checkout the `gh-pages` branch and follow the instructions in the README.

data/LICENSE.md

@@ -0,0 +1,19 @@
+Copyright (c) Nicolas Gallagher and Jonathan Neal and John Albin Wilkins
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,109 @@
+## Latest downloadable version
+
+The latest release of _normalize.scss is: [2.1.2](https://github.com/JohnAlbin/normalize.css-with-sass-or-compass/archive/2.1.2.zip).
+It combines normalize.css v2.1.2 and normalize v1.1.2.
+
+## The Compass port of normalize.css
+
+__This project is the Sass/Compass port of normalize.css.__ It aims to use the best
+partials from Compass to make normalize even easier to integrate with your
+website. To learn about why Normalize.css is so amazing, skip to the
+"normalize.css" section below.
+
+This Sass/Compass port currently utilizes:
+
+* Legacy IE support variables
+* CSS3 Box Sizing mixin
+* Vertical Rhythm mixins
+
+In addition, Normalize.css has 2 major versions: version 2 (without legacy
+browser support) and version 1 (with support for IE 6/7, etc.) This Compass port
+combines the two versions into one file so that you can easily toggle between
+the two versions using Compass' `$legacy-support-for-ie7` variable.
+
+Did a client wait until the last minute to mention their CEO uses IE 7? Simply
+set `$legacy-support-for-ie7` to `true` and recompile your Sass files.
+
+# normalize.css v2
+
+Normalize.css is a customisable CSS file that makes browsers render all
+elements more consistently and in line with modern standards. We researched the
+differences between default browser styles in order to precisely target only
+the styles that need normalizing.
+
+[Check out the demo](http://necolas.github.io/normalize.css/latest/test.html)
+
+[Legacy browser support is available in v1](https://github.com/necolas/normalize.css/tree/v1)
+
+## Install
+
+Download from the [project page](http://necolas.github.io/normalize.css/).
+
+Install with [Bower](http://bower.io/): `bower install --save normalize-css`
+
+## What does it do?
+
+* Preserves useful defaults, unlike many CSS resets.
+* Normalizes styles for a wide range of elements.
+* Corrects bugs and common browser inconsistencies.
+* Improves usability with subtle improvements.
+* Explains what code does using detailed comments.
+
+## How to use it
+
+Normalize.css is intended to be used as an alternative to CSS resets.
+
+It's suggested that you read the `normalize.css` file and consider customising
+it to meet your needs. Alternatively, include the file in your project and
+override the defaults later in your CSS.
+
+For more information about how to use it, see the [About normalize.css article](http://nicolasgallagher.com/about-normalize-css/).
+
+To use the Compass port of Normalize, simply copy the _normalize.scss file to
+your sass directory and follow the article's suggestions:
+
+* __Approach 1:__ use _normalize.scss as a starting point for your own project's
+base Sass, customising the values to match the design's requirements. (The best
+approach, _IMO_.)
+* __Approach 2:__ include _normalize.scss untouched and build upon it, overriding
+the defaults later in your Sass if necessary.
+
+## Browser support
+
+* Google Chrome
+* Mozilla Firefox 4+
+* Apple Safari 5+
+* Opera 12+
+* Internet Explorer 8+
+* Internet Explorer 6-7 (when `$legacy-support-for-ie7` or
+`$legacy-support-for-ie6` is set to `true`)
+
+## Contribute
+
+Please read Necolas' [contributing
+guidelines](CONTRIBUTING.md).
+
+Updates to most CSS rules should be reported to Necolas' upstream [Normalize.css
+project](http://necolas.github.com/normalize.css/). Updates to the Sass should
+be reported in the [Normalize.css with Sass and Compass project](https://github.com/JohnAlbin/normalize.css-with-sass-or-compass/).
+
+## Acknowledgements
+
+Normalize.css is a project by [Nicolas Gallagher](https://github.com/necolas),
+co-created with [Jonathan Neal](https://github.com/jonathantneal).
+
+This Sass/Compass port is a project by [John Albin Wilkins](http://john.albin.net).
+
+## Other ports of Normalize.css
+
+For the record, there are several other Sass or Compass ports as well.
+Including:
+
+* https://github.com/waynegraham/compass-normalize-plugin
+* https://github.com/ksmandersen/compass-normalize
+* https://github.com/hail2u/normalize.scss
+* https://github.com/kristerkari/normalize.scss
+
+Some of the above projects convert normalize into Sass mixins. That makes it
+impossible to add Normalize using __Approach 1__ (by copying the file into your website
+and customizing/overriding for your needs.)