Skip to content

Conversation

@seungsoo47
Copy link

  • Current the text input channel handles user input for only existing flutter components.
    Therefore, we added the logic so that the platform view can also handle the composition
    events happened by user input.

* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
Copy link

@bbrto21 bbrto21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bbrto21 bbrto21 merged commit e629333 into flutter-tizen:flutter-2.0.1-tizen Mar 22, 2021
swift-kim pushed a commit that referenced this pull request Jun 7, 2021
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Sep 27, 2021
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Nov 14, 2021
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Dec 9, 2021
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Dec 17, 2021
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Feb 7, 2022
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Feb 11, 2022
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request May 12, 2022
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Aug 5, 2022
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
swift-kim pushed a commit that referenced this pull request Sep 1, 2022
swift-kim pushed a commit that referenced this pull request Sep 1, 2022
* Current the text input channel handles user input for only existing flutter components.
  Therefore, we added the logic so that the platform view can also handle the composition
  events happened by user input.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants