Hi,

I keep getting this error

Undefined variable: "$supported-browsers"

But I can't find any Compass documentation to tell me what I should set this value to.

Can anyone point me in the right direction?

Normalize can be used in a variety of project settings. Not all of them have Compass. Would it be possible to remove this requirement?

I've just installed normalize.css with bower, using "bower install normalize.scss --save" in a local Yeoman project on Mac 10.7.5.

Installation works fine, but when I attempt the command "bower list" I receive the output:

bower error Unable to fetch package normalize-scss (if the cache was deleted, run install again)

If I uninstall the package, "bower list" returns the installed components as expected.

I could very well be doing something wrong. Anybody else having a similar issue?

pulling down "normalize.scss": "3.0.0-alpha.1+normalize.2.1.3" and i'm getting this compiling errror:

"Syntax error: Invalid CSS after " 'chrome'": expected ")", was ": null,"\A on line 30 of /bower_components/normalize.scss/_normalize.scss from line 4 of main.scss"

any ideas?

We're currently using a single ruleset for h1, h2, h3, h4, h5, h6 to apply a leading and trailing vertical rhythm unit. And if the compiled CSS was in px that would work. But the compiled CSS is in em which means the margins are relative to the font size of the heading, i.e. all the margins are wrong.

We need to pass the font-size to the leader() and trailer() mixins for each heading.

Hi,

I was using Compass-normalize in an old project. When I was looking for a normalize component, I inadvertently skipped this one and went with the first. For a new project though, I wanted to make sure I'm using this repo, as it's maintained and updated frequently (Compass-normalize is a few years old without any recent updates). So I switched the require statement in config.rb from 'compass-normalize' to 'normalize-scss' and figured I'm good to go. Then, a closer look at my css output, reveals a horrible bug (or feature?). The css output remains that of "compass-normalize". I enabled source comments to find out where the css emits from, and it's most definitely coming from gems/compass-normalize. I have no idea why it does that when I altered my require statement. It seems like uninstalling 'compass-normalize' fixes it, but I cannot uninstall it, as it's a dependency in some of my older projects.

Anyone moving from that old normalize repo to this repo, read the usage instructions carefully. While the old one requires a simple import statement 'import "normalize"', this one requires another line "include normalize()" which of course, calls a mixin. I also didn't notice 'support-for' is required, since I simply switched the require statement and my code compiled just fine. It's up until I noticed the css output is that of "compass-normalize".

Any solution or just a compass bug?

Thanks.

It would make it easier to "drop and customize" this if there was a @import "base" statement at the top.

I'm not 100% certain if this should be:

// @import "base"; // Add your project's base partial.

or:
@import "base"; // Add your project's base partial.

If it is left uncommented, then when you add it to a project and they don't follow best practices by having a _base.scss partial, then they'll get an error. Maybe this instead:

@import "base"; // Remove this line if you don't follow Compass best practices. @see http://compass-style.org/help/tutorials/best_practices/

Taking a look at @Snugug's Navigator test framework for Sass with Compass.

Going to try implementing this here first.

Hi,

Thanks for this nice port of formalize. I have one question though, why do you import "base" in normalize? I think it would be better to leave it to the themer since "base" can be in other directory or even have a different name.

For instance, in my main.sass file I usually have something like:

@import global/base
@import vendor/normalize
@import partials/...

You convert line-height to ems which result in some unexpected behavior. The recommendation is to use unitless values. Is there any reason you chose to convert to ems?

Hi,

maybe I'm completely lost, but when I look at your bower.json the normalize/_import-now.scss file is marked as main file.

There are some instructions on how to use your lib, but there is no real scenario on how to use it with bower, except of the note that you have to override some things to use it with wiredep.

We want to use css libs from our project by just running bower install and adding an @import line in our main css.

In your case, the main file is in the ./normalize Folder. Normally other css libraries use the main file in the root namespace but you don't, so we can't use your Project in the same generic way with Sass include paths.

If there is nothing against from your side using the normalize-scss/sass/_normalize.scss instead of normalize-scss/sass/normalize/_import-now.scss you'd help us and properly all wiredeps user as well.

If you agree to that, I can open a PR.

Greets
`Alwin Mark

Cannot import using compass because the folder contains "."

The license comment (for MIT license) is not protected:

/* normalize-scss 3.0.3+normalize.3.0.3 | MIT/GPLv2 License | bit.ly/normalize-scss */

The exclamation mark is missing.

Here the license comment of the original normalize CSS
(https://github.com/necolas/normalize.css/blob/3.0.3/normalize.css#L1)

/*! normalize.css v3.0.3 | MIT License | github.com/necolas/normalize.css */

This is important, because CSS minifiers (e.g. csswring) will strip a normal comment away,
and this license notice won't appear in the CSS file being published.

Hi, I'm doing research about what is the best reset css nowadays, and I noticed that a lot of coworkers has been using your normalize_scss while other are using normalize.css from Nicolas. I would like to know what is the difference between your and Nicolas, and if there are some advantage to use the normalize in sass, like performance, or other reasons ?

Thanks Regards

Hello,

Im using your plugin with import now option, which is including from bower components. When i try to have initial compile of scss i get this error:

bower_components\normalize-scss\sass\normalize\_vertical-rhythm.scss Error: normalize-font-size() only supports px inputs. The typey library is better. on line 25 of bower_components/normalize-scss/sass/normalize/_vertical-rhythm.scss
And i cant proceed any work. Thanks in advance

Wait for a PR based on this comment: 76b5921#diff-df19fcac63f4bf0081a32c7021d79c8f

https://css-tricks.com/inheriting-box-sizing-probably-slightly-better-best-practice/

Since the people cry for a world without dependencies, we should drop compass. Or, at least, we should stick together a version without compass.

For sure, there are a lot of great forks out there, but you are the leader at NPM, RubyGem etc.

After a bit of research I found this gist, which could help us: https://gist.github.com/ry5n/2026666

I try to @import normalize or normalize/import-now,
but eyeglass alone doesn't seem to be able to pick it up.

I prepared a test repo so one can debug it directly:
https://github.com/strarsis/normalize-scss_test/tree/master

http://cssdeck.com/labs/full/cnoifmlu/noframe
http://necolas.github.io/normalize.css/2.1.0/test.html

https://github.com/necolas/normalize.css/releases/tag/4.0.0

There is no main value specified in the bower.json file which stops build tools from injecting the correct file into the build process

At least it looks that way: http://beta.compass-style.org/CHANGELOG/

When running alpha versions of Compass 1.0.0 a warning will be issued due to the fact that _normalize.scss sets $legacy-support-for-ie6 and $legacy-support-for-ie7. I solved this problem by simply moving the variables below the compass imports around line 42 since they are still expected later on in _normalize.scss. Of course, for people wanting legacy IE support this probably isn't the best solution as Compass itself isn't being configured.

The warning issued when compiling:

WARNING: Compass has changed how browser support is configured. See the CHANGELOG for more details. The following configuration variables are no longer supported: $legacy-support-for-ie6, $legacy-support-for-ie7.

{} interpolation near operators will be simplified in a future version of Sass. To preserve the current behavior, use quotes:

unquote("#{$h1-font-size / $base-font-size}#{$rhythm-unit}")

line 211 should be changed from this:

font-size: if($rhythm-unit == "px", $h1-font-size, ($h1-font-size / $base-font-size)#{$rhythm-unit});

to:

font-size: if($rhythm-unit == "px", $h1-font-size, unquote("{$h1-font-size / $base-font-size}#{$rhythm-unit}")  );

Hi,

I have installed the partial _normalize.scss but the compilation failed :

error sass/styles.sass (Line 192 of sass/vendors/_normalize.scss: 0.15em/px isn't a valid CSS value.)

It's looking like a problem with the rhythm mixin but I don't understand why...

Any idea ?

I am using Grunt (with grunt-sass) to build my site’s CSS. I’ve used NPM to install normalize-scss, but when I require('normalize-scss') in my GruntFile.js, I get a SyntaxError:

Loading "GruntFile.js" tasks...ERROR
>> SyntaxError: Unexpected token ILLEGAL
>>     at exports.runInThisContext (vm.js:53:16)
>>     at Module._compile (module.js:404:25)
>>     at Object.Module._extensions..js (module.js:432:10)
>>     at Module.load (module.js:356:32)
>>     at Function.Module._load (module.js:311:12)
>>     at Module.require (module.js:366:17)
>>     at require (module.js:385:17)
>>     at Object.module.exports (/Users/kyank/code/impromelbourne.com.au/GruntFile.js:26:11)
>>     at loadTask (/Users/kyank/code/impromelbourne.com.au/node_modules/grunt/lib/grunt/task.js:325:10)
>>     at Task.task.init (/Users/kyank/code/impromelbourne.com.au/node_modules/grunt/lib/grunt/task.js:437:5)

NodeJS v5.0.0 on OS X 10.11.2.

Any idea what I might be doing wrong?

Hey, Martin! @apparentlymart

Thanks for publishing normalize-scss to npm for me, but I can't publish the latest release to npmjs.org.

$ npm publish normalize-scss
npm ERR! publish Failed PUT 403

npm ERR! You do not have permission to publish 'normalize-scss'. Are you logged in as the correct user? : normalize-scss

Can you add me as having permissions to publish to that namespace so I can publish 3.0.3?

npm owner add johnalbin normalize-scss

From a fresh Bower install, and import of the normalize.scss files the following error is returned

Error: Undefined variable: "$px-fallback".
    on line 42 of bower_components/normalize-scss/fork-versions/default/_vertical-rhythm.scss, in `normalize-rhythm'
    from line 58 of bower_components/normalize-scss/fork-versions/default/_vertical-rhythm.scss, in `normalize-margin'
    from line 185 of bower_components/normalize-scss/fork-versions/default/_normalize.scss
    from line 2 of sass/style.scss

Only 2 little changes:
necolas@5962c89#diff-bb3dde41d97f19be8ab7b4780a915d5e
necolas@3a62048#diff-bb3dde41d97f19be8ab7b4780a915d5e

It's almost always used liked this:

@if not $strict-normalize or support-legacy-browser(ie, "7") {
  // Vertical rhythm code...
}

Since support-legacy-browser returns true, the vertical rhythm code gets included. I'm not sure what the expected behavior is, but the result is $strict-normalize is essentially ignored.

IE8 needs px fallback when using rem units.

Currently, when doing @include normalize-rhythm(margin, 1 0); the px fallback outputs a unitless 1 instead of the actual px value needed.

I was hoping to use this version of normalize as my default install for a static site generator I am working on, but then today as I was about to publish the first stable version and I could no longer compile the sass.

I was wondering if there was a new name in the bower registry? I guess I can specify the repo directly, but my yeoman generator will look pretty silly when the prompt stretches off the screen saying:

[?] Bower packages to install, comma separated: angular,[email protected]:JohnAlbin/normalize-scss.git

Any suggestions? Or can you re-publish on bower?

SassyTest 3 is out.

IE 6/7 and Firefox 29 have a few special properties in various rulesets in normalize-scss.

However, all 3 of those browsers are no longer supported by their vendors. IE 9 is the earliest browser version supported by Microsoft. And Firefox 45 is the earliest supported browser by Mozilla.

Those were the only browsers requiring special properties and were the reason that _support-for.scss was included in this project.

If we drop support for those unsupported browsers, we can simplify the codebase by removing support-for.

https://github.com/necolas/normalize.css/

Given the discussion in #43 and #48, we should update the README to talk about import paths.

When I use this module together with Susy I automatically get horizontal lines to guide / debug a vertical rhythm (revealed together with Susy's grid). Could you point me to how that happens and where the code for it is?

If I include normalize.css instead, the lines disappear. So it must be coming from here... Unfortunately GitHub doesn't search forked repos yet.

Normalize 2.0 is out. Woo-hoo!

It removes support for crufty browsers, IE7 and lower. See necolas@7e01498 and necolas@dcc17fd

I occasionally get clients asking for IE7 support late in a project. Switching from a project-modified normalize v2 to a fresh normalize v1 and re-adding the project-specific modifications would be a PITA.

Fortunately Compass gives us a way around this. It's "support" module provides $legacy-support-for-ie7 and $legacy-support-for-ie6 variables.

We can use those variables to wrap the crufty bits from normalize v1 in a conditional @if and place them in normalize v2. That way, we'd get normalize v2 by default and if you turned on IE7 or IE6 support, you'd get the v1 support injected into the stylesheet immediately.

Normalize.css 5.0.0 is out. https://github.com/necolas/normalize.css/releases/tag/5.0.0

We should upgrade.

I explicitly defined all the variables used in normalize.scss. I did this in the normalize-with-sass branch since it works without Compass, but I forgot to look at this again after adding actual Compass imports.

There's no need to re-define the variable defaults since they are already defined in the imports.

Let's just leave them as code comments.

I remember that Chris Epstein pointed out that /* */ comments get stripped out when using output_style = :compressed on production sites, but not when output_style = :expanded or :nested or :compact on development sites.

To make it even easier to keep the Sass/Compass port of normalize in sync with the normailze.css, let's convert all the // comments back into /* */ comments.

Due to the package.json file containing an older version of eyeglass, this module is out of date with eyeglass.
#50

Normalize 7.0.0 is out. https://github.com/necolas/normalize.css/releases

Sass 3.4 was recently released but this gem is declared to be incompatible. Unless there are known incompatibilities, could you change the dependency?

Caveat: I don’t know much about best practices here

cannot require at node, add it to fix.

_normalize.scss imports files from the normalize folder which is missing
in the package for beta release 4.0.0-beta.1.

Error at first import in file:

[...]
File to import not found
or unreadable: normalize/variables.
[...]

...or with libsass:

[...]
Error: Could not import `normalize/variables` from any of the following locations
[...]

When following the instructions to install/use the latest branch with support for normalize.css v3, Sass 3.3 and Compass 1.0 via bower there is an error resolving the target version. Presumably because the tag is missing?

$ bower install --save normalize.scss#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3       not-cached git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3          resolve git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0       not-cached git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0          resolve git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.2+normalize.3.0.0
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3         download https://github.com/JohnAlbin/normalize-scss/archive/3.0.0-alpha.1+normalize.2.1.3.tar.gz
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3          extract archive.tar.gz
bower normalize.scss#3.0.0-alpha.1+normalize.2.1.3         resolved git://github.com/JohnAlbin/normalize-scss.git#3.0.0-alpha.1+normalize.2.1.3
bower normalize.scss#3.0.0-alpha.2+normalize.3.0.0     ENORESTARGET No tag found that was able to satisfy 3.0.0-alpha.2+normalize.3.0.0

Additional error details:
Available versions: 3.0.0-alpha.1+normalize.2.1.3, 2.2.0+normalize.2.1.3, 2.1.3, 2.1.2, 2.1.0, 2.0.1, 2.0.1+build.2

I was able to get the version I wanted using the following command:

$ bower install --save git://github.com/JohnAlbin/normalize-scss#master

in case it helps:

$ npm -v && bower -v && uname -v
1.3.24
1.2.8
Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64

The first import that normalize does is for a file that does not exist. Any ideas?

It seems that in this commit f32a7fd , it was removed from the normalized folder.

Hi John not sure where else to turn. I usually use a base line height of 6px and adjust leading to (4) on html to give me better control over white space. Just updated to the latest version of normalize scss and its setting the line-height to 6em rather than calculating 1.5em.

Tested with the old version in case it was my version of compass and worked fine. I notice you added the strict normalize boolean in but I can't see how that should affect the outcome.

Any thoughts would be much appreciated.

In fact just tested with default of leading(1) and no matter what I change the base-line-height variable to it always outputs 1.5em???