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
Description of the problem
I described the issue here: 2753192
Anyone using the Grid or MiniGrid services might be affected by this. It seems to work fine if the html for the Grid is already on the page, but if a Grid is added dynamically, the sorting is not properly bound to that Grid instance. The selector used in that change tries to find any tbody on the page and make it sortable.
I'm not sure what was wrong with the old code that prompted that change, but it's adversely affecting Simple Grids & Tables.
How To Reproduce
Steps to reproduce the behavior:
Use JS to dynamically add a Grid field to the page, note that sorting does not work.
Possible Solutions
Replace $('tbody') selector with whatever the variable is for the instance of the Grid field.
Revert that commit
Move that sortable() call into it's own function so it can be easily called and bound to a Grid field dynamically added to the page.
The text was updated successfully, but these errors were encountered:
Description of the problem
I described the issue here: 2753192
Anyone using the Grid or MiniGrid services might be affected by this. It seems to work fine if the html for the Grid is already on the page, but if a Grid is added dynamically, the sorting is not properly bound to that Grid instance. The selector used in that change tries to find any
tbody
on the page and make it sortable.I'm not sure what was wrong with the old code that prompted that change, but it's adversely affecting Simple Grids & Tables.
How To Reproduce
Steps to reproduce the behavior:
Use JS to dynamically add a Grid field to the page, note that sorting does not work.
Possible Solutions
$('tbody')
selector with whatever the variable is for the instance of the Grid field.The text was updated successfully, but these errors were encountered: