NativeScript / NativeScript/plugins
[@nativescript/keyboard-toolbar] Weird behavior on Toolbar
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 206
- Forks
- 123
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
I have successfully implemented the KeyboardToolbar on an Android device using Angular. I have experienced a couple of issues:
- I am experiencing problems with autoscroll when the KeyboardToolbar is covering the text input. In my case, initially, the toolbar is already covering part of the text input and, once it gets longer than one line, the UI starts getting messed up. This behavior can be seen in the attached video, but is currently making it unusable for our use case. I believe these could be related to the Future Work section in Eddy's old plugin.
https://github.com/NativeScript/plugins/assets/15091668/06b68aaa-127b-469a-b1f9-dc07ec201324
- I am also unable to use this plugin with Angular when the TextView is in a child component. The KeyboardToolbar on the parent component is not able to detect the id of the TextView. I believe this should work, any ideas on how to would be nice, since I guess this design pattern is pretty common
I have tried checking the plugin's code but I'm not sure exactly how it works. so I don't think I can PR myself 😅
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are mentioned. Start by reproducing both behaviors on Android with Angular: a multiline TextView covered by the toolbar and a TextView in a child component; done means autoscroll remains correct and the parent toolbar detects the child TextView.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, angular, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100