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.

Describe the solution you'd like

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

Additional context
Originally Opened By @Gaboris at necolas/normalize.css#851 Plus, Original Solution By @VixieTSQ in necolas/normalize.css#852

Links broke due to the transfer to the org

GitHub issue templates and pr templates are broken since they no longer connect to krishdevdb/.github

Detail Comments In The Source Explaining The Code

Checklist:

• Add Comments
• No Notice Like /*! reseter.css v1.1.1 | MIT License | github.com/krishdevdb/reseter.css */`
• Comments Available In All Sources.
  • SASS
  • LESS
  • SCSS
  • Stylus
• Changes Are Made In The Comments Branch and merged in a single pull request.
• Reference Of All The Code In A Separate Web Page/Blog. Maybe At https://krishdevdb.github.io/reseter.css

Resource

• Normalize.css
• CSS Tools' Normalize.css
• Sanitize.css
• MDN Docs

Original issue in Normalize: necolas/normalize.css#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)

Just to be helpful - in the "Why use...(must read)" section of the page at https://krishdevdb.github.io/, the 3 images are missing.

@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

Description

Some badges in the README.md are displaying "File not found".

Anything else?

Code of Conduct

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

Detailed Description

Roll Out v2.0.0 as the changes promised are already made, we can continue the docs simultaneously as docs won't be shipped to the package

Contributing

• I have read the project's contribution guidelines.

Code of Conduct

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

Anything else?

No response

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.

Add @coliss for blog contributions

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @semantic-release/github to v10.1.7

Vulnerabilities

Renovate has not found any CVEs on osv.dev.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Describe the bug
There is an image in the Readme file, that has broken due to some reason.

Screenshots

Read me file links to various libraries and frameworks are broken int more section .

If a demo video is added to the ReadMe.md file, it would help the community to understand and use this project more effectively subsequently expanding the user-base.

Description

The table markup in the README.md is displaying the markup as text instead of the actual table

Anything else?

Code of Conduct

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

Is your feature request related to a problem? Please describe.
I like the idea to reseter to have a consistent UI throughout all the browsers. I tried the mentioned demo in the readme.md and it loads the UI better but still it varies in the different browsers. I have tried with

1. Chrome
2. Microsoft edge
3. Firefox

You can refer the attached screenshot for details.

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

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?

Add @lsprr As A Contributor For #32

https://github.com/krishdevdb/reseter.css/blob/fe8d92687a8cc34207cddc27c924dd4d6f6c7919/css/reseter.css#L70-L78

These rules seem to be not understood by at least two major browsers (Firefox 88 and Vivaldi 3.7).

For the margin, replacing initial by another value like auto or 0 removes the error.

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.

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

We can make it using: https://github.com/EddieHubCommunity/gh-action-open-source-labels

Original Idea by @schmelto in EddieHubCommunity/support#1448

Project does't have a convention of .md files.
In order to make it more readable can I work on this

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

• I have read the project's contribution guidelines.

Code of Conduct

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

Anything else?

No response

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

The first image in readme.md and the github pages isn't sourced properly.

Hey @krishdevdb 👋🏽 This docs link is broken in the about section of this repository, please do fix it.

Also, I was looking at this project and you all have maintained it well. Pretty good!! Keep it up folks 🔥

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.

A humble request to everyone reading this. I request you to kindly, check out other CSS resets and normalizers. Find some issues or bugs in them using the bug tracker. Then repost it to this repository. Make sure to link to the actual issue, of the repo where you found it.

For example, #19 and #16 are taken from @starkana in sindresorhus/modern-normalize#46 and @Gaboris at necolas/normalize.css#851 respectively.

Thanks! Please Mention This Issue In Your Issue So That Everyone Reading This Page Will Get To Know What All Issues Have Been Made!

Describe the bug
Please see screenshots

To Reproduce
Steps to reproduce the behavior:

1. Go to https://krishdevdb.github.io/reseter.css/
2. Read the entire page, and you will see several separate words we combine into one — but shouldn’t.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [Windows 10 Pro build 19042.928]
• Browser [Firefox Developer Edition]
• Version [89.0b3]

Additional context
Is it a bug specific to GitHub Pages?

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?