The double click inside a table happens when the first click selects the row and only the second reaches the control - the row-selection handler of the table (Dojo table of the Coaches toolkit, and the UI Toolkit table in single-select mode with "select on click") consumes the first click; sometimes the first click also blurs a previously focused input, triggering a re-render of the row.
Fixes by toolkit:
- UI Toolkit table: set the table's Selection option to None when the rows do not need selecting; when selection is needed, newer toolkits let you exclude cell controls from triggering it; and keep cell controls light (Text / Checkbox), not composite views.
- Avoid re-render on the first click: a formula or an on change handler that calls setData on the table's list re-renders every row and swallows the click; update the record in place (record.qty = ...) and refresh only that row.
- Heritage Dojo table: the first click focuses the cell (edit mode), the second edits; there is no clean fix - either enable "single-click edit" where the version offers it or move to the UI Toolkit table.
- Buttons in cells: in the cell control's on click handler call event.stopPropagation() so the row selection does not run; or put the action buttons outside the table acting on the selected row (one click to select, a visible button to act - often the better UX).
// Button inside a table cell > On click (UI Toolkit): act on this row without triggering row selection logic
if (typeof event !== "undefined" && event && event.stopPropagation) event.stopPropagation();
var rec = me.ui.getIndex ? ${Orders}.getRecord(me.ui.getIndex()) : ${Orders}.getSelectedRecord();
${Details}.setData(rec);References