Conversation
…lt-value-state-emitting
exploIF
approved these changes
Nov 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #237
Turns out
eventEmitterisn't available from the very beginning, but the iOS code was remembering recently active styles even if no state change event was emitted. This way, when the event emitter was finally available, no state change event was emitted because recently active styles were exactly same (even though no event went out).Except that, I added all lifecycle callbacks (
anyTextMayHaveBeenModifiedthat e.g. runs the state change event) to thedidMoveToWindowbecause it seems like the event emitter is defined then.The issue was;
defaultValuewas set but its state changes emitted only when some change was done to an input (and not on focus or when eventEmitter is available). The PR fixes both scenarios.