[TASK] Context Menus in Tables should behave consistently globally
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Context menus (more menus) in tables across the product stay visible even when focus is lost, this is true in several places, I am showing it in the locales portlet for this example. They should disappear once a selection is made, another menu is open, or in general, when context is lost.
Jalinson also already fixed the context menu that was staying visible even when scrolling, for content drive, he mentions that this issue is happening because of how PRIMENG handles the context menu, that is we use the content drive table across the board the scrolling issue would be addressed as he fixed it there by exposing the OnScroll() menthod.
In general, context menus should behave consistently across the board and should be treated as a global element. We should check to make sure that is the case.
Acceptance Criteria
In general, context menus should behave consistently across the board and should be treated as a global element. We should check to make sure that is the case.
Priority
Medium
Additional Context
No response
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 with the locales portlet example and compare its context-menu behavior with the content drive table, where the scrolling issue was already addressed. Review how PrimeNG context menus are used across the tables and the existing OnScroll() change. Done means menus consistently disappear when focus or context is lost, another menu opens, a selection is made, or the table scrolls.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100