Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use 'tabIndex' instead of 'tabindex' #169

Closed
6 tasks done
CesGalaxy opened this issue Sep 7, 2023 · 1 comment · Fixed by #170
Closed
6 tasks done

Use 'tabIndex' instead of 'tabindex' #169

CesGalaxy opened this issue Sep 7, 2023 · 1 comment · Fixed by #170
Labels
React Issue with Tailwind Mobile React

Comments

@CesGalaxy
Copy link

CesGalaxy commented Sep 7, 2023

Check that this is really a bug

  • I confirm

Reproduction link

Bug description

The Link component uses tabindex instead of tabIndex property

Expected Behavior

Use tabIndex="0"

Actual Behavior

Uses tabindex="0"

Konsta UI version

3.0.1

Platform/Target and Browser Versions

Windows 11 & Chrome 116

Validations

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a Konsta UI issue and not a framework-specific issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR
@CesGalaxy CesGalaxy added the React Issue with Tailwind Mobile React label Sep 7, 2023
jkhaui added a commit to jkhaui/konsta that referenced this issue Sep 7, 2023
@jkhaui
Copy link
Contributor

jkhaui commented Sep 7, 2023

Ha what timing, this has been bugging me for a few days too now and I literally just visited this repo to open a PR fixing it: #170

@nolimits4web, thanks for this awesome lib, when you get a chance is it possible to also merge in #167? If you need, I can make a new issue for it.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
React Issue with Tailwind Mobile React
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants