ag-grid: `onCellValueChanged` event not triggered by paste in v21.2.0
I’m submitting a …
[x] bug report
[] feature request
[] support request
Note: I am an Enterprise customer, but I have not yet received credentials for filing this bug in Zendesk.
Current behavior
When pasting (cmd+V) into the grid, the onCellValueChanged
callback is not called.
You can see this bug in the ag-Grid documentation. In the Clipboard Example (https://www.ag-grid.com/javascript-grid-clipboard/#clipboard-example), if you paste into the grid, "cellValueChanged"
is never logged in the console, contrary to what the documentation states.
Expected behavior
onCellValueChanged
callback should be called for every pasted cell. This behavior works correctly in v21.1.1
, so it looks like a regression introduced in v21.2.0
.
-
ag-Grid version: 21.2.0
-
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36
-
Language: ES6
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 23 (1 by maintainers)
For those looking for an update on this issue (at least for the
ag-grid-enterprise
module), I do have an open ticket with Enterprise support which looks like it will address this.I first created a simple repo that demonstrates the issue so their support team could review: https://github.com/lroot/ag-grid-copy-paste-bug-demo
The support team then responded:
An example workaround was provided: https://stackblitz.com/edit/ag-grid-vue-hello-world-qi4hhv?file=app.js
This involves extracting the clipboard module explicitly from the ag-grid-enterprise module and registering it with the ag-grid-community module:
Yes, Its in there release pipeline already for next version.
On Thu, Oct 17, 2019 at 7:31 PM Anna Borja notifications@github.com wrote:
It works in v21.2.2. I have MAJOR issues with 22.0.0. I cannot copy and paste anything! All Copy and Paste has broken. I rolled back to 21.2.2. and everything works fine, including this ticket.
It’s such a huge bug, I didn’t log it because I just figured everyone will be complaining about it.