Previously, the Explorer would allow you to press a letter in order to traverse to the next sibling you had selected.
For example, if I were to press G while having this element selected, it would traverse to “Goblin Blacksmith” and select that, as the first letter is G.
With the new explorer, this behavior is seemingly gone.
Expected behavior
Pressing keycodes should traverse to the next sibling.
Hey! Currently we don’t have plans to add this to Next Gen Explorer, so will close this ticket as a feature request.
You don’t intend to add type‑ahead navigation to a Explorer window? Why in the name of RNJ not, its like the most useful way to navigate the explorer?
I am not happy with this decision. Replacements to existing systems should be able to replicate their functionality, otherwise why replace it? That’s a waste of development time if the outcome is a downgrade in functionality.
Agreed. I’ve been using key traversing for years and I don’t know why it is not being moved over to the Next Gen explorer.
next gen explorer is such a downgrade in so many respects… Roblox are making it clear they do not want people to develop on this platform if they can’t do the bare minimum of not removing functionality!
I cannot think of any other program, service, or entity that is considered successful that regresses or has regressed functionality.
Yeah, I didn’t really agree with this being a feature request as it was existing functionality that was stripped away. To me, that seems like unintended behavior. It’s unfortunate but I don’t know if much can be done.
100% this, its a replacement not a new system. @pensive_penguin please can you kindly re-evaluate your decision?
Next Gen Disappointment, thanks!
