Removed <tags> so they wouldn't conflict with procssor.com#14
Merged
necolas merged 1 commit intonecolas:masterfrom Jun 10, 2011
Merged
Removed <tags> so they wouldn't conflict with procssor.com#14necolas merged 1 commit intonecolas:masterfrom
necolas merged 1 commit intonecolas:masterfrom
Conversation
necolas
added a commit
that referenced
this pull request
Jun 10, 2011
Remove <tags> from CSS comments to avoid any problems with CSS formatting tools.
Owner
|
Thanks for this! |
sigridfuhrenkamp-cyber
pushed a commit
to sigridfuhrenkamp-cyber/normalize.css
that referenced
this pull request
Mar 9, 2026
Remove <tags> from CSS comments to avoid any problems with CSS formatting tools.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you copy and paste the normalize.css into the recommended processor, http://procssor.com/, you get
<textarea>,<input>, and<a>tags throughout the page. Although this is really a bug with procssor, I would advise switching this for user convenience.I simply changed the syntax from
<tags>to'tags'. Alternative syntax is welcome, but escaping the tags seemed wrong.You can see the exact issue here http://img832.imageshack.us/img832/7329/tagnormalissues.png