-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8187307: ListView, TableView, TreeView: receives editCancel event when edit is committed #684
Conversation
when edit is committed
👋 Welcome back fastegal! A progress list of the required criteria for merging this PR into |
/reviewers 2 |
@aghaisas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
I also did some manual tests and everything looks fine here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix and tests look good.
@kleopatra This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 43 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 4c79c54.
Your commit was automatically rebased without conflicts. |
@kleopatra Pushed as commit 4c79c54. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The misbehaviour was that an edit handler received both a commit and cancel event when cell commitEdit is called. That happened whenever a collaborator reset the controls editing state (either directly or indirectly) while processing the editCommit event. The reason was that the cell had not yet updated its own editing state when receiving the change of editing from the control.
Fix is to update cell's editing state before firing the event, that is change the sequence or method calls from fire/super.commit to super.commit/fire.
Added tests that fail/pass before/after the fix.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/684/head:pull/684
$ git checkout pull/684
Update a local copy of the PR:
$ git checkout pull/684
$ git pull https://git.openjdk.java.net/jfx pull/684/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 684
View PR using the GUI difftool:
$ git pr show -t 684
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/684.diff