Grid/TreeGrid Editor events are 66% not what it says on the tin.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Applies to 8.1.1.
In the Grid/TreeGrid we have the possibility attach listeners to the editor to be notified of:
- Open
- Save
- Cancel
However, these events seem to behave oddly.
In the Grid, in unbuffered mode, mind you, the events behave as follows:
- Open, called when the editor opens.
- Save, never called.
- Cancel, called when the editor loses the focus or is closed by pressing Return.
- No event is fired when Escape is pressed.
In the TreeGrid, unbuffered mode, the events behave as follows:
- Open, called when the editor opens.
- Save, never called.
- Cancel, called when Escape is pressed.
- When Return is pressed, the "next" open event fires.
This seems rather unintuitive, or did I miss something there?
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
Reproduce the reported behavior in Grid and TreeGrid with unbuffered editors, exercising Open, Save, Cancel, Return, Escape, focus loss, and closing. Compare the event sequences between both components and determine the intended editor lifecycle semantics. Done means the events consistently reflect the documented actions in both Grid and TreeGrid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100