Update focused component info back to server on each UIDL-request
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by @jouni
Window.getFocusedComponent() returns only the last component set with focus()-method. I think the state should represent the actual situation on the client side during the the time of UIDL-request.
Should at least make easier to implement keybindings.
Imported from https://dev.vaadin.com/ issue #1364
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
Start by tracing Window.getFocusedComponent() and the UIDL-request handling mentioned in the issue, checking how client focus state is represented and sent to the server. Done means each UIDL request reports the component actually focused on the client, supporting the stated keybinding use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100