Jeremy Fields

Hi @FezVrasta, thanks for bringing this up. I've had `:focus-visible` on my radar for a while to look into. What Input has been around longer than `:focus-visible` so it's not...

@phun-ky it's very possible! If `:focus-visible` gets you what you need then I'd agree that jumping on the browser-native solution is the way to go. I don't make any money...

Hi @swey, thanks for the feedback! You should be able to still get the same response as v3 by using the `data-whatintent` attribute or querying `whatInput.ask('loose')`. That was my way...

Hi @swey, I just released version 5 with some breaking changes to v4 and some updated logic to how input/intent behaves. It may still not be exactly what you're looking...

Hi @lorenzos, thanks for reporting this. I'll give it a look.

Hi @DmitryLen, thanks for bringing this issue up. Your first message sounds like the intended behavior when interacting with forms. I have that documented under [interacting with forms](https://github.com/ten1seven/what-input#interacting-with-forms). Can you...

You should just need to do `"track-focus": "1.0.0"` since it's published as a package. You could also try installing it via npm with `npm install track-focus`. Let me know if...

Okay, give it a try now. I tried publishing again and tested.

@smiller171 You should be able to import or require it per the options I outlined in the [usage](https://github.com/ten1seven/what-input#usage) section of the README. Is it failing when you try this?

Oops, you're right! Have you tried What Input for this functionality? It's the replacement for Track Focus and I actively maintain it.