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
We've been using tables inside "form" elements and have recently observed a strange side effect. Some tables, after sorting them, were submitting the whole form and reloading the page. So, for some reason, it breaks the sorting process, shows an error in the console, and then makes a default submission. It turns out that there are two conditions for this error: the table needs to be initialized with the number of entries per page larger than the table itself, and there have to be a few cells with no content inside. Then, if you try to sort the columns, sometimes it works fine for the first one or two clicks, but ultimately it breaks. Since, in our case, the tables are mostly generated dynamically and we cannot predict the content or number of rows, it is an issue.
We've been using tables inside "form" elements and have recently observed a strange side effect. Some tables, after sorting them, were submitting the whole form and reloading the page. So, for some reason, it breaks the sorting process, shows an error in the console, and then makes a default submission. It turns out that there are two conditions for this error: the table needs to be initialized with the number of entries per page larger than the table itself, and there have to be a few cells with no content inside. Then, if you try to sort the columns, sometimes it works fine for the first one or two clicks, but ultimately it breaks. Since, in our case, the tables are mostly generated dynamically and we cannot predict the content or number of rows, it is an issue.
Here are examples of static tables where you can see this issue..
The text was updated successfully, but these errors were encountered: