You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a page with Jspreadsheet (for example, the following documentation pages for v4 or v5), open a browser console, then click any cell in the spreadsheet so that the jspreadsheet.current command works properly.
In the console, enter the command jspreadsheet.current.setMerge('B2',1,2).
Right click the column merged ('B" in the example given) and click "Delete selected columns."
This can also impact multi-column cell merges, but the process is more complex: it only breaks on the rightmost column of a merge, and right-clicking it will usually also select any other columns involved in the merge, resulting in a "This will destroy any existing merged cells" screen making the issue irrelevant. To get around this, the first row (i.e. row 1) must not be part of the merge; that way, one can click the cell directly below the column, then right-click the column itself and delete the column from there.
This shifts several columns left from the first row to the point where the merge had ended; however, the other ones below it don't seem to move, leaving the table broken. The console gives the error, Uncaught TypeError: can't access property "removeChild", followed in v4 by obj.records[d][l].parentNode is null and in v5 by l.records[t][n].element.parentNode is null.
The text was updated successfully, but these errors were encountered:
Steps to reproduce:
jspreadsheet.current
command works properly.jspreadsheet.current.setMerge('B2',1,2)
.This shifts several columns left from the first row to the point where the merge had ended; however, the other ones below it don't seem to move, leaving the table broken. The console gives the error,
Uncaught TypeError: can't access property "removeChild"
, followed in v4 byobj.records[d][l].parentNode is null
and in v5 byl.records[t][n].element.parentNode is null
.The text was updated successfully, but these errors were encountered: