Actions
Bug #46903
closedmgr/dashboard: Datatable catches select events from other datatables
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Double-clicking in the limit or search action field of an embeded datatable will be processed by the wrapping datatable.
Files
Updated by Volker Theile over 3 years ago
- File screenshot2.gif screenshot2.gif added
- Description updated (diff)
Updated by Volker Theile over 3 years ago
- Subject changed from mgr/dashboard: Datatable catches select events from other datatables to mgr/dashboard: Datatable catches click events from other datatables
Updated by Volker Theile over 3 years ago
- File screenshot3.gif screenshot3.gif added
- Description updated (diff)
Updated by Volker Theile over 3 years ago
Seems to be a known problem if the Swimlane datatable, see https://github.com/swimlane/ngx-datatable/issues/899.
Updated by Volker Theile over 3 years ago
- Subject changed from mgr/dashboard: Datatable catches click events from other datatables to mgr/dashboard: Datatable catches select events from other datatables
Updated by Volker Theile over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 36590
Updated by Lenz Grimmer over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Tiago Melo over 3 years ago
This introduced a regression in master.
All backports should include https://tracker.ceph.com/issues/47175
Updated by Volker Theile over 3 years ago
- Precedes Bug #47175: mgr/dashboard: Fix stale table actions added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47198: nautilus: mgr/dashboard: Datatable catches select events from other datatables added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47199: octopus: mgr/dashboard: Datatable catches select events from other datatables added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 165 to UI
Actions