Close idle UIs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
The session timeout is UI independent and it's possible to close IDLE sessions, but it's not supported to close IDLE UIs.
If one user opens the same UI in two tabs in the same browser, the server has one VaadinSession and two UI instances. It would be great to support closing idle UIs because both UIs are stored in the same VaadinSession and closing IDLE sessions doesn't close an idle UI.
If user doesn't use UI 1, it should expire. The idle UI feature should be like a session timeout for UIs.
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 the existing idle session timeout behavior from VaadinSession to its UI instances, then compare how two tabs are represented within one session. Determine where per-UI inactivity could be tracked and what existing timeout behavior should be reused. Done means an unused UI expires without closing active sibling UIs in the same VaadinSession, with coverage for the two-tab scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100