Is your feature request related to a problem? Please describe. Support tags like acronym

Describe the solution you'd like Use abbr, acronym instead of abbr.

FYI, using the following, from my own list, and integrated the one in the repository.

pre,
code,
kbd,
samp {
  font-family: "Fira Code", 
    "Cascadia Code", 
    Consolas, 
    "Inconsolata",
    Monaco,
    Menlo,
    "Noto Mono",
    "Roboto Mono",
    "Droid Sans Mono", 
    "Ubuntu Mono",
    "Ubuntu Monospace",
    "Source Code Pro", 
    "Oxygen Mono",
    "Liberation Mono", 
    "DejaVu Sans Mono", 
    "Bitstream Vera Sans Mono", 
    monospace,
    "Apple Color Emoji",
    "Segoe UI Emoji",
    "Segoe UI Symbol",
    "Noto Color Emoji";
  font-size: 1.04rem;
}

The developer fonts above represent some of the more common fonts, all of which will render/display better than the default which is often a Courier derivative. The above fonts list are all sans-serif developer fonts with an aesthetic which will at least be closer to the default font family.

Reason on the ordering...

• Fira Code - the most complete font in terms of fixed width with width-proper emojii support.
• Cascadia Code - Windows (newer)
• Consolas - Windows (common)
• Inconsolata - Consolas look-alike, open-source.
• Droid Sans Mono - Android
• Monaco - MacOS
• Menlo - iOS
• others - more common alternative fonts installed on different platforms
• monospace - Default fallback
• *Emoji - emoji character supprt as fallback

Thank you for contributing! Please confirm this pull request meets the following requirements:

• [x] I followed the contributing guidelines: https://github.com/krishdevdb/reseter.css/blob/master/contributing.md

Which change are you proposing?

• [ ] Adding A New Element's Reset
• [x] Editing A Old Element's Reset
• [ ] Removing A Elements's Reset

Write Something About It Here works on the opacity of placeholder in input. (pseudoelement)

My PR Meets The Following Criterias:

• [x] It Redifines Usefull Defaults (If you are doing it for h1 you redifine the font size to be big enough)
• [x] My Content Is Responsive If Applicable (If you are defining any px values please convert them to rem for responsiveness)
• [x] My Content Is Tested. That It Doesn't Breaks The Element
• [x] My Content Is Not My Personal Opinion
• [ ] I have used the command yarn *:build

I've added the following sources:

• [ ] less
• [ ] scss
• [ ] sass
• [ ] stylus

Fixes #16 Check #16

Describe the bug Under the Tweet and GitHub star buttons display bug

To Reproduce Steps to reproduce the behavior:

1. Go to https://krishdevdb.github.io/reseter.css/
2. See bug

Expected behavior Not display bug

Screenshots

Desktop (please complete the following information):

• OS: macOS Catalina ver 10.15.7
• Browser: Chrome
• Version: Version 89.0.4389.114 (Official Build) (x86_64)

Additional context Is it a bug specific to GitHub Pages?

Detailed Description

Don't have time for a PR at the moment, appended to my local copy, but probably a good idea to add..

p + p {
  margin-top: 1rem;
}

Contributing

• [X] I have read the project's contribution guidelines.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Anything else?

No response

Is your feature request related to a problem? Please describe. Chrome doesn't wrap its links at all while Firefox does. Chrome uses a different default value for word-break then Firefox as after adding word-break: break-word; on its links it behaved the same way as Firefox did. I also saw that similar questions have come up before and they were put aside because of "unexpected behaviors", but this seems like a special case as it to only happens with the tag so it could be an exception.

a {
  cursor: pointer;
  color: #3333e1;
  background-color: transparent;
  text-decoration: none;
  word-break: normal;
}

This was requested by krishdevdb in this comment

Describe the bug Going through the 'Why do I use a CSS Reset' part, I noticed that there is a Firefox browser referenced in the table, but instead of the firefox heading, the heading says 'with Resetter.css'.

Also, on the first line of this section, instead of using 'Down is the result', which could be misleading as the status of the website, 'Below is the result' can be used.

To Reproduce Steps to reproduce the behaviour:

1. Go to the ReadMe.md page.
2. Go to section 'Why do I use a CSS Reset'
3. See the error

Expected behaviour The table heading should say Firefox, instead of 'with Resetter.css'

Screenshots

Desktop (please complete the following information):

• NA

Smartphone (please complete the following information):

• NA

Additional context Add any other context about the problem here.

Is your feature request related to a problem? Please describe. FireFox (latest version as of posting) has a slightly lower opacity for input placeholders. See my screenshot below. You fix this with:

I suggest adding it to reseter.css.

Describe the solution you'd like Fix The Issue By Adding input::placeholder { opacity: 1; } to reseter.css

Additional context

Originally Publish By @starkana in sindresorhus/modern-normalize#46

Is your feature request related to a problem? Please describe. We are using the LTS version of Node which is not supported by this package.

Describe the solution you'd like Downgrade the required Node version to the latest LTS.

Describe alternatives you've considered Upgrading to a non-LTS version is not possible on the project I'm currently working, so not much that can be done here.

Additional context

@krishdevdb

showcase image needs to be fixed 

• There seems to be some issue with Image
• and there is no space after the mark sign I think It will look better if it's fixed

Bumps postcss-cli from 9.0.2 to 10.1.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Original issue in Normalize: https://github.com/necolas/normalize.css/issues/864

Particularly the bit about Turkish characters is interesting.

The guideline in question: https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html

Currently using 1.15 in this repo (https://github.com/resetercss/reseter.css/blob/main/css/reseter.css#L10)

I liked the documentation a lot. Could you add some colourful shades so that the docs become a bit easy to read? I tried changing the color temporarily, which looked better.

Noticed an issue where the pointer style is being applied to buttons even though they are disabled. Here is the current code that provides this styling.

[type='button']:not(disabled),
[type='reset']:not(disabled),
[type='submit']:not(disabled),
button:not(disabled) {
  cursor: pointer;
}

I believe that to proper select disabled buttons we have to do it this way:

[type='button']:not([disabled]),
[type='reset']:not([disabled]),
[type='submit']:not([disabled]),
button:not([disabled]) {
  cursor: pointer;
}

However, can we not just utilize the :enabled selector?