feat: Redesigned the Input Number for Input Range

[drvcodenta]

Added the selector .input-range-inputs[type="number"]

My PR closes #509

👨‍💻 Changes proposed(What did you do ?)

Updated styles.css by redesigning the Input Number for Input Range

✔️ Check List (Check all the applicable boxes)

• [x] My code follows the code style of this project.
• [x] This PR does not contain plagiarized content.
• [x] The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
code-magic	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2023 9:17pm

[Dun-sin]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass. Most often, our PR titles are something like one of these:

* docs: correct typo in README

* feat: implement dark mode"

* fix: correct remove button behavior

Linting Errors

* Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"

* No subject found

@drvcodenta Please fix this error, if you don't know how, try this:

• Read the error carefully or read the contributing file
• Checkout past merged Pull requests to see how they were done for it to be merged

Note: you can edit your PR message, this PR won't be merged if the error isn't gone and you have a week max to fix it before the PR gets closed without being merged

[Dun-sin]

:tada: This PR is included in version 2.75.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: