Meta tags:
description= A cross-browser CSS foundation. Contribute to csstools/normalize.css development by creating an account on GitHub.;
Headings (most frequently used words):
contributing, navigation, md, css, file, breadcrumbs, requests, footer, to, normalize, menu, repository, filesexpand, tree, latest, commit, history, metadata, and, controls, using, the, issue, tracker, bug, reports, feature, pull, maintainers, conventions, accepting, patches, releasing, new, version, semver, strategy,
Text of the page (most frequently used words):
the (74), and (43), your (21), for (20), github (17), css (15), you (14), project (12), git (12), this (11), new (11), #normalize (11), test (10), all (10), feature (10), code (10), that (9), are (9), branch (9), please (9), issue (9), with (8), file (8), requests (8), any (7), patch (7), version (7), push (7), bug (7), versions (6), browser (6), developers (6), not (5), security (5), changes (5), add (5), will (5), latest (5), into (5), directory (5), comments (5), pull (5), features (5), what (5), support (5), actions (5), considered (4), selector (4), change (4), might (4), update (4), copy (4), changelog (4), patches (4), applies (4), work (4), fix (4), more (4), repository (4), respect (4), contributing (4), raw (4), copilot (4), time (3), information (3), navigation (3), rules (3), backwards (3), others (3), html (3), master (3), origin (3), create (3), include (3), use (3), check (3), has (3), commit (3), scope (3), process (3), including (3), then (3), order (3), make (3), possible (3), following (3), these (3), something (3), clone (3), upstream (3), csstools (3), fork (3), case (3), lines (3), steps (3), reproduce (3), example (3), report (3), problem (3), issues (3), tracker (3), blame (3), main (3), history (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), reload (3), sign (3), customer (3), enterprise (3), grade (3), build (3), can (2), share (2), personal (2), community (2), status (2), footer (2), compatible (2), normalization (2), cause (2), minor (2), result (2), release (2), major (2), semver (2), supported (2), browsers (2), after (2), tags (2), tag (2), merge (2), locally (2), commits (2), necessary (2), descriptive (2), message (2), have (2), follow (2), sorted (2), specificity (2), alphabetic (2), begin (2), when (2), they (2), obvious (2), short (2), keep (2), guidelines (2), conventions (2), title (2), license (2), used (2), thing (2), npm (2), current (2), our (2), checkout (2), move (2), com (2), remote (2), install (2), repo (2), coding (2), etc (2), other (2), want (2), first (2), good (2), improvements (2), help (2), out (2), merits (2), reported (2), potential (2), opinions (2), reduced (2), step (2), environment (2), using (2), been (2), see (2), search (2), reports (2), review (2), 188 (2), 145 (2), loc (2), path (2), breadcrumbs (2), insights (2), signed (2), universe (2), training (2), integrations (2), stories (2), center (2), documentation (2), learn (2), business (2), fixes (2), products (2), secret (2), perform, action, manage, cookies, contact, docs, privacy, terms, 2026, inc, functionality, manner, therefore, instance, element, may, override, user, style, universal, backgrounds, shrink, background, color, inputs, disappear, opacity, whatsoever, breaking, impact, rendering, widely, accepted, method, deciding, how, numbers, incremented, written, strategy, index, from, root, named, pages, annotated, functional, releasing, button, caution, apply, squashing, tests, proper, within, philosophy, accepting, access, merging, cutting, releases, maintainers, between, selectors, low, high, section, cascade, correct, deal, less, side, effects, describe, does, without, number, reference, entire, rule, point, readable, now, clear, description, remember, submitting, agree, allow, owner, under, same, open, request, sure, appropriate, follows, practices, your_user, tools, testing, assign, original, called, navigate, newly, cloned, like, inclusion, adhere, throughout, whitespace, accurate, requirements, such, coverage, before, embarking, significant, otherwise, risk, spending, lot, working, ask, fantastic, should, remain, focused, avoid, containing, unrelated, welcome, take, moment, find, whether, idea, fits, aims, strong, convince, provide, much, detail, context, relevant, being, identified, causing, solutions, their, link, url, further, second, summary, which, occurs, suitable, required, shouldn, leave, needing, chase, detailed, experience, would, expect, outcome, details, people, bugs, live, isolate, trying, fixed, already, caused, demonstrable, derail, troll, discussion, topic, preferred, channel, but, restrictions, helps, communicate, managing, developing, return, reciprocate, addressing, document, contribution, easy, effective, everyone, involved, edit, outline, download, preview, metadata, controls, top, expand, tree, files, items, dismiss, alert, switched, accounts, appearance, settings, pricing, event, talks, workshops, next, partners, about, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, source, across, one, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, development, environments, codespaces, analysis, enforcement, automation, ship, agent, tasks, projects, automated, hosting, collaboration, platform, menu, skip, content,
Text of the page (random words):
normalize css contributing md at main csstools normalize css github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message csstools normalize css repository navigation code issues 5 5 pull requests 1 1 actions security and quality insights more items files expand file tree main breadcrumbs normalize css contributing md copy path blame more file actions blame more file actions latest commit history history history 188 lines 145 loc 7 19 kb main breadcrumbs normalize css contributing md copy path top file metadata and controls preview code blame 188 lines 145 loc 7 19 kb raw copy raw file download raw file outline edit and raw actions contributing to normalize css please 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 project in return we will reciprocate that respect in addressing your issues patches and features using the issue tracker the issue tracker is the preferred channel for bug reports feature requests and 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 bug reports a bug is a demonstrable problem caused by the code in this repository use the github issue search to see if the issue has already been reported check if the issue has been fixed by trying to reproduce it using the latest master branch in the repository isolate the problem to create a live example of a reduced test case a good bug report shouldn t leave others needing to chase you up for more information please 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 this is the first step this is the second step 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 feature requests feature requests are welcome 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 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 to begin fork this project clone your fork and add our upstream clone your fork of the repo into the current directory git clone git github com your_user normalize css git navigate to the newly cloned directory cd normalize css assign the original repo to a remote called upstream git remote add upstream git github com csstools normalize css git install the tools necessary for testing npm install create a branch for your feature or fix move into a new branch for your feature git checkout b feature thing move into a new branch for your fix git checkout b fix something if your code follows our practices then push your feature branch test current code npm test push the branch for your new feature git push origin feature thing or push the branch for your update git push origin update something be sure to add a test to the test html file if appropriate and test your change in all supported browsers now open a pull request with a clear title and description remember 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 css conventions keep the css file as readable as possible by following these guidelines comments are short and to the point comments without a number reference the entire rule comments describe the selector when the selector does not make the normalization obvious comments begin with correct the when they deal with less obvious side effects rules are sorted by section cascade specificity and then alphabetic order selectors are sorted by low to high specificity and then alphabetic order in browser applies to all versions in browser v applies to all versions after and including the version in browser v applies to all versions up to and including the version in browser v v applies to all versions including and between the versions maintainers if you have commit access please follow this process for merging patches and cutting new releases accepting patches check that a patch is within the scope and philosophy of the project check that a patch has any necessary tests and a proper descriptive commit message test the patch locally use github s merge button with caution or apply the patch locally squashing any commits releasing a new version include all new functional changes in changelog md create an annotated tag for the version git tag m 0 0 0 0 0 0 push the changes and tags to github git push tags origin master update the gh pages branch copy the latest normalize css and test html from the master branch into the root directory the latest directory and a new directory named after the new version 0 0 0 update the normalize css version and supported browsers in index html semver strategy semver is a widely accepted method for deciding how version numbers are incremented in a project versions are written as major minor patch any change to css rules whatsoever is considered backwards breaking and will result in a new major release others changes with no impact on rendering are considered backwards compatible and will result in a new patch release no changes to css rules can add functionality in a backwards compatible manner therefore no changes are considered minor for instance a normalization on an element selector may override a user style on a universal selector or a change to opacity might cause inputs to disappear or a change to background color might cause backgrounds to shrink footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|