No update in 2y: how can it support last 2-3 browser versions then?

Open
#32 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
css
Domain
documentation

Research direction

Start by reviewing the README's statement about support for the last 2–3 browser versions and compare it with the project's release history. Done means the README's support claim is clarified or corrected to match the available release information.

Written by the indexing model from the issue text.

Description

The readme says that the last 2-3 browser versions are supported. Is this possible given that there haven't been any releases in the past 2 years?

Dominant language
HTML
Stars
656
Forks
66
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from csstools/normalize.css

All issues in csstools/normalize.css

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.