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

[MIRROR] Fixes input boxes [No gbp] #1235

Merged
merged 1 commit into from
Dec 21, 2023
Merged

[MIRROR] Fixes input boxes [No gbp] #1235

merged 1 commit into from
Dec 21, 2023

Conversation

Steals-The-PRs
Copy link
Collaborator

Mirrored on Skyrat: Skyrat-SS13/Skyrat-tg#25761
Original PR: tgstation/tgstation#80490

About The Pull Request

One of the quirks of react is that we're no longer using onChange the same as Inferno - React's version is a synthetic event. I made the mistake of thinking it would be okay. Many interfaces are using onChange events to send messages to byond (very laggy), others are using it to close the input (closes each keypress).

So this was the alternative- I hope to replicate the behavior via onBlur && onEnter. I went through to undo most of the onInput -> onChange replacements of #80340 where it made sense. Other inputs which should safely use onChange (DEFINITELY to send messages) remain as such.

Example of an input which used onChange now working with this PR:
aUojN0owHO

Why It's Good For The Game

Bug fixes
Fixes #80486

Changelog

🆑 jlsnow301
fix: Name input in character setup should work properly now.
fix: Many inputs should feel more responsive.
/:cl:

* Fixes input boxes [No gbp] (#80490)

## About The Pull Request
One of the quirks of react is that we're no longer using onChange the
same as Inferno - React's version is a synthetic event. I made the
mistake of thinking it would be okay. Many interfaces are using onChange
events to send messages to byond (very laggy), others are using it to
close the input (closes each keypress).

So this was the alternative- I hope to replicate the behavior via onBlur
&& onEnter. I went through to undo most of the onInput -> onChange
replacements of #80340 where it made sense. Other inputs which should
safely use onChange (DEFINITELY to send messages) remain as such.

Example of an input which used onChange now working with this PR:

![aUojN0owHO](https://github.com/tgstation/tgstation/assets/42397676/82aa1d44-360d-4978-bef8-12720d7b4c70)
## Why It's Good For The Game
Bug fixes
Fixes #80486
## Changelog
:cl:
fix: Name input in character setup should work properly now.
fix: Many inputs should feel more responsive.
/:cl:

* Fixes input boxes [No gbp]

---------

Co-authored-by: Jeremiah <[email protected]>
@ReezeBL ReezeBL merged commit 4b5dd96 into master Dec 21, 2023
23 checks passed
@ReezeBL ReezeBL deleted the upstream-mirror-25761 branch December 21, 2023 06:53
AnywayFarus added a commit that referenced this pull request Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants