normalize-scss 2.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 6dcd0d6dd7892ffe004c010df93a5459d6c92b48
4
+ data.tar.gz: 14dee99f3b13a462733a3f1636b7ad66596962d4
5
+ SHA512:
6
+ metadata.gz: f2bbe7803dd20275d3b8ef92cc195614f4a1af5816bb9d6776a39df8454497e6f1063222c4644a63ae9fd1824fef5d39f5c286b71594cd076624fd7cc0ecd3a8
7
+ data.tar.gz: 99721a8fb6691fcf0a0c0794adbb0e5f256658b45afdcb0ca0938a86626b0055b22da667eeb5f293896103b5cd609aaff9b54d8febe5940c47a31404113d75da
data/CHANGELOG.md ADDED
@@ -0,0 +1,69 @@
1
+ == HEAD
2
+
3
+ == 2.1.2 (May 11, 2013)
4
+
5
+ * Revert root `color` and `background` normalizations.
6
+
7
+ == 2.1.1 (April 8, 2013)
8
+
9
+ * Normalize root `color` and `background` to counter the effects of system
10
+ color schemes.
11
+
12
+ == 2.1.0 (January 21, 2013)
13
+
14
+ * Normalize `text-transform` for `button` and `select`.
15
+ * Normalize `h1` margin when within HTML5 sectioning elements.
16
+ * Normalize `hr` element.
17
+ * Remove unnecessary `pre` styles.
18
+ * Add `main` element to HTML5 display definitions.
19
+ * Fix cursor style for disabled button `input`.
20
+
21
+ == 2.0.1 (August 20, 2012)
22
+
23
+ * Remove stray IE 6/7 `inline-block` hack from HTML5 display settings.
24
+
25
+ == 2.0.0 (August 19, 2012)
26
+
27
+ * Remove legacy browser form normalizations.
28
+ * Remove all list normalizations.
29
+ * Add `quotes` normalizations.
30
+ * Remove all heading normalizations except `h1` font size.
31
+ * Form elements automatically inherit `font-family` from ancestor.
32
+ * Drop support for IE 6/7, Firefox < 4, and Safari < 5.
33
+
34
+ == 1.1.2 (May 11, 2013)
35
+
36
+ * Revert root `color` and `background` normalizations.
37
+
38
+ == 1.1.1 (April 8, 2013)
39
+
40
+ * Normalize root `color` and `background` to counter the effects of system
41
+ color schemes.
42
+
43
+ == 1.1.0 (January 21, 2013)
44
+
45
+ * Normalize `text-transform` for `button` and `select`.
46
+ * Normalize `hr` element (excluding IE 6/7).
47
+ * Add `main` element to HTML5 display definitions.
48
+ * Fix cursor style for disabled button `input`.
49
+
50
+ == 1.0.2 (November 17, 2012)
51
+
52
+ * Correct `h6` font size normalization.
53
+
54
+ == 1.0.1 (August 19, 2012)
55
+
56
+ * Adjust `small` font size normalization.
57
+
58
+ == 1.0.0 (August 14, 2012)
59
+
60
+ (Only the notable changes since public release)
61
+
62
+ * Add MIT License.
63
+ * Hide `audio` elements without controls in iOS 5 (#69).
64
+ * Normalize heading margins and font size.
65
+ * Move font-family normalization from `body` to `html` (#62).
66
+ * Remove scrollbar normalization (#64 #65).
67
+ * Remove excess padding from checkbox and radio inputs in IE 7 (#42).
68
+ * Add IE9 correction for SVG overflow (#16).
69
+ * Add fix for legend not inheriting color in IE 6/7/8/9.
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,177 @@
1
+ # Contributing to normalize.css
2
+
3
+ Please take a moment to review this document in order to make the contribution
4
+ process easy and effective for everyone involved.
5
+
6
+ Following these guidelines helps to communicate that you respect the time of
7
+ the developers managing and developing this open source project. In return,
8
+ they should reciprocate that respect in addressing your issue or assessing
9
+ patches and features.
10
+
11
+
12
+ ## Using the issue tracker
13
+
14
+ The issue tracker is the preferred channel for [bug reports](#bugs),
15
+ [features requests](#features) and [submitting pull
16
+ requests](#pull-requests), but please respect the following restrictions:
17
+
18
+ * Please **do not** use the issue tracker for personal support requests.
19
+
20
+ * Please **do not** derail or troll issues. Keep the discussion on topic and
21
+ respect the opinions of others.
22
+
23
+
24
+ <a name="bugs"></a>
25
+ ## Bug reports
26
+
27
+ A bug is a _demonstrable problem_ that is caused by the code in the repository.
28
+ Good bug reports are extremely helpful - thank you!
29
+
30
+ Guidelines for bug reports:
31
+
32
+ 1. **Use the GitHub issue search** – check if the issue has already been
33
+ reported.
34
+
35
+ 2. **Check if the issue has been fixed** – try to reproduce it using the
36
+ latest `master` branch in the repository.
37
+
38
+ 3. **Isolate the problem** – create a live example (e.g., on
39
+ [Codepen](http://codepen.io)) of a [reduced test
40
+ case](http://css-tricks.com/6263-reduced-test-cases/).
41
+
42
+ A good bug report shouldn't leave others needing to chase you up for more
43
+ information. Please try to be as detailed as possible in your report. What is
44
+ your environment? What steps will reproduce the issue? What browser(s) and OS
45
+ experience the problem? What would you expect to be the outcome? All these
46
+ details will help people to fix any potential bugs.
47
+
48
+ Example:
49
+
50
+ > Short and descriptive example bug report title
51
+ >
52
+ > A summary of the issue and the browser/OS environment in which it occurs. If
53
+ > suitable, include the steps required to reproduce the bug.
54
+ >
55
+ > 1. This is the first step
56
+ > 2. This is the second step
57
+ > 3. Further steps, etc.
58
+ >
59
+ > `<url>` - a link to the reduced test case
60
+ >
61
+ > Any other information you want to share that is relevant to the issue being
62
+ > reported. This might include the lines of code that you have identified as
63
+ > causing the bug, and potential solutions (and your opinions on their
64
+ > merits).
65
+
66
+
67
+ <a name="features"></a>
68
+ ## Feature requests
69
+
70
+ Feature requests are welcome. But take a moment to find out whether your idea
71
+ fits with the scope and aims of the project. It's up to *you* to make a strong
72
+ case to convince the project's developers of the merits of this feature. Please
73
+ provide as much detail and context as possible.
74
+
75
+
76
+ <a name="pull-requests"></a>
77
+ ## Pull requests
78
+
79
+ Good pull requests - patches, improvements, new features - are a fantastic
80
+ help. They should remain focused in scope and avoid containing unrelated
81
+ commits.
82
+
83
+ **Please ask first** before embarking on any significant work, otherwise you
84
+ risk spending a lot of time working on something that the project's developers
85
+ might not want to merge into the project.
86
+
87
+ Please adhere to the coding conventions used throughout a project (whitespace,
88
+ accurate comments, etc.) and any other requirements (such as test coverage).
89
+
90
+ Follow this process if you'd like your work considered for inclusion in the
91
+ project:
92
+
93
+ 1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
94
+ and configure the remotes:
95
+
96
+ ```bash
97
+ # Clone your fork of the repo into the current directory
98
+ git clone https://github.com/<your-username>/normalize.css
99
+ # Navigate to the newly cloned directory
100
+ cd normalize.css
101
+ # Assign the original repo to a remote called "upstream"
102
+ git remote add upstream https://github.com/necolas/normalize.css
103
+ ```
104
+
105
+ 2. If you cloned a while ago, get the latest changes from upstream:
106
+
107
+ ```bash
108
+ git checkout master
109
+ git pull upstream master
110
+ ```
111
+
112
+ 3. Never work directly on `master`. Create a new topic branch (off the latest
113
+ version of `master`) to contain your feature, change, or fix:
114
+
115
+ ```bash
116
+ git checkout -b <topic-branch-name>
117
+ ```
118
+
119
+ 4. Commit your changes in logical chunks. Please adhere to these [git commit
120
+ message conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
121
+ or your code is unlikely be merged into the main project. Use Git's
122
+ [interactive rebase](https://help.github.com/articles/interactive-rebase)
123
+ feature to tidy up your commits before making them public.
124
+
125
+ Make sure to add a test to the `test.html` file if appropriate, and test
126
+ your change in all supported browsers.
127
+
128
+ 5. Locally rebase the upstream development branch into your topic branch:
129
+
130
+ ```bash
131
+ git pull --rebase upstream master
132
+ ```
133
+
134
+ 6. Push your topic branch up to your fork:
135
+
136
+ ```bash
137
+ git push origin <topic-branch-name>
138
+ ```
139
+
140
+ 10. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
141
+ with a clear title and description.
142
+
143
+ Please submit a separate pull request for any appropriate changes required
144
+ in the `v1` branch for legacy browsers.
145
+
146
+ **IMPORTANT**: By submitting a patch, you agree to allow the project owner to
147
+ license your work under the same license as that used by the project.
148
+
149
+
150
+ <a name="maintainers"></a>
151
+ ## Maintainers
152
+
153
+ If you have commit access, please follow this process for merging patches and
154
+ cutting new releases.
155
+
156
+ ### Accepting patches
157
+
158
+ 1. Check that a patch is within the scope and philosophy of the project.
159
+ 2. Check that a patch has any necessary tests and a proper, descriptive commit
160
+ message.
161
+ 3. Test the patch locally.
162
+ 4. Do not use GitHub's merge button. Apply the patch to `master` locally
163
+ (either via `git am` or by checking the whole branch out). Amend minor
164
+ problems with the author's original commit if necessary. Then push to GitHub.
165
+ 5. If a patch should be included in `v1`, cherry-pick the commits or manually
166
+ apply if all else fails.
167
+
168
+ ### Releasing a new version
169
+
170
+ 1. Include all new functional changes in the CHANGELOG.
171
+ 2. Use a dedicated commit to increment the version. The version needs to be
172
+ added to the CHANGELOG (inc. date), and the `bower.json`, `component.json`,
173
+ and `normalize.css` files.
174
+ 3. The commit message must be of `v0.0.0` format.
175
+ 4. Create an annotated tag for the version: `git tag -m "v0.0.0" v0.0.0`.
176
+ 5. Push the changes and tags to GitHub: `git push --tags origin master`
177
+ 6. Checkout the `gh-pages` branch and follow the instructions in the README.
data/LICENSE.md ADDED
@@ -0,0 +1,19 @@
1
+ Copyright (c) Nicolas Gallagher and Jonathan Neal and John Albin Wilkins
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining a copy of
4
+ this software and associated documentation files (the "Software"), to deal in
5
+ the Software without restriction, including without limitation the rights to
6
+ use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
7
+ of the Software, and to permit persons to whom the Software is furnished to do
8
+ so, subject to the following conditions:
9
+
10
+ The above copyright notice and this permission notice shall be included in all
11
+ copies or substantial portions of the Software.
12
+
13
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19
+ SOFTWARE.
data/README.md ADDED
@@ -0,0 +1,109 @@
1
+ ## Latest downloadable version
2
+
3
+ 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).
4
+ It combines normalize.css v2.1.2 and normalize v1.1.2.
5
+
6
+ ## The Compass port of normalize.css
7
+
8
+ __This project is the Sass/Compass port of normalize.css.__ It aims to use the best
9
+ partials from Compass to make normalize even easier to integrate with your
10
+ website. To learn about why Normalize.css is so amazing, skip to the
11
+ "normalize.css" section below.
12
+
13
+ This Sass/Compass port currently utilizes:
14
+
15
+ * Legacy IE support variables
16
+ * CSS3 Box Sizing mixin
17
+ * Vertical Rhythm mixins
18
+
19
+ In addition, Normalize.css has 2 major versions: version 2 (without legacy
20
+ browser support) and version 1 (with support for IE 6/7, etc.) This Compass port
21
+ combines the two versions into one file so that you can easily toggle between
22
+ the two versions using Compass' `$legacy-support-for-ie7` variable.
23
+
24
+ Did a client wait until the last minute to mention their CEO uses IE 7? Simply
25
+ set `$legacy-support-for-ie7` to `true` and recompile your Sass files.
26
+
27
+ # normalize.css v2
28
+
29
+ Normalize.css is a customisable CSS file that makes browsers render all
30
+ elements more consistently and in line with modern standards. We researched the
31
+ differences between default browser styles in order to precisely target only
32
+ the styles that need normalizing.
33
+
34
+ [Check out the demo](http://necolas.github.io/normalize.css/latest/test.html)
35
+
36
+ [Legacy browser support is available in v1](https://github.com/necolas/normalize.css/tree/v1)
37
+
38
+ ## Install
39
+
40
+ Download from the [project page](http://necolas.github.io/normalize.css/).
41
+
42
+ Install with [Bower](http://bower.io/): `bower install --save normalize-css`
43
+
44
+ ## What does it do?
45
+
46
+ * Preserves useful defaults, unlike many CSS resets.
47
+ * Normalizes styles for a wide range of elements.
48
+ * Corrects bugs and common browser inconsistencies.
49
+ * Improves usability with subtle improvements.
50
+ * Explains what code does using detailed comments.
51
+
52
+ ## How to use it
53
+
54
+ Normalize.css is intended to be used as an alternative to CSS resets.
55
+
56
+ It's suggested that you read the `normalize.css` file and consider customising
57
+ it to meet your needs. Alternatively, include the file in your project and
58
+ override the defaults later in your CSS.
59
+
60
+ For more information about how to use it, see the [About normalize.css article](http://nicolasgallagher.com/about-normalize-css/).
61
+
62
+ To use the Compass port of Normalize, simply copy the _normalize.scss file to
63
+ your sass directory and follow the article's suggestions:
64
+
65
+ * __Approach 1:__ use _normalize.scss as a starting point for your own project's
66
+ base Sass, customising the values to match the design's requirements. (The best
67
+ approach, _IMO_.)
68
+ * __Approach 2:__ include _normalize.scss untouched and build upon it, overriding
69
+ the defaults later in your Sass if necessary.
70
+
71
+ ## Browser support
72
+
73
+ * Google Chrome
74
+ * Mozilla Firefox 4+
75
+ * Apple Safari 5+
76
+ * Opera 12+
77
+ * Internet Explorer 8+
78
+ * Internet Explorer 6-7 (when `$legacy-support-for-ie7` or
79
+ `$legacy-support-for-ie6` is set to `true`)
80
+
81
+ ## Contribute
82
+
83
+ Please read Necolas' [contributing
84
+ guidelines](CONTRIBUTING.md).
85
+
86
+ Updates to most CSS rules should be reported to Necolas' upstream [Normalize.css
87
+ project](http://necolas.github.com/normalize.css/). Updates to the Sass should
88
+ be reported in the [Normalize.css with Sass and Compass project](https://github.com/JohnAlbin/normalize.css-with-sass-or-compass/).
89
+
90
+ ## Acknowledgements
91
+
92
+ Normalize.css is a project by [Nicolas Gallagher](https://github.com/necolas),
93
+ co-created with [Jonathan Neal](https://github.com/jonathantneal).
94
+
95
+ This Sass/Compass port is a project by [John Albin Wilkins](http://john.albin.net).
96
+
97
+ ## Other ports of Normalize.css
98
+
99
+ For the record, there are several other Sass or Compass ports as well.
100
+ Including:
101
+
102
+ * https://github.com/waynegraham/compass-normalize-plugin
103
+ * https://github.com/ksmandersen/compass-normalize
104
+ * https://github.com/hail2u/normalize.scss
105
+ * https://github.com/kristerkari/normalize.scss
106
+
107
+ Some of the above projects convert normalize into Sass mixins. That makes it
108
+ impossible to add Normalize using __Approach 1__ (by copying the file into your website
109
+ and customizing/overriding for your needs.)