Closed (fixed)
Project:
Responsive Tables Filter
Version:
2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2024 at 08:53 UTC
Updated:
19 Aug 2024 at 17:04 UTC
Jump to comment: Most recent
Comments
Comment #2
mark_fullmerConfirming that this problem can be reproduced on any form where (a) a table is rendered when (b) this module's global setting for adding this to administrative Views is enabled. An immediate workaround for someone having this problem is to disable that setting.
Now to the root cause...
Comment #5
mark_fullmerOur team determined that the problem here stems from the switch from the jQuery version of Tablesaw to Shoestring, which happened as part of the transition in the 2.x branch to move away from jQuery. The Shoestring library, which functions as a kind of replacement for Tablesaw, appears to have some problems with global scoping that interfere with other JS. See https://github.com/filamentgroup/shoestring/pull/146
Reverting to using jQuery resolves the issue.
The merge request above:
1. Reverts to using the jQuery version of the Tablesaw library.
2. Replaces deprecated calls to
push()andsort()with supported syntax per https://blog.jquery.com/2024/02/06/jquery-4-0-0-beta/3. Moves a couple accessibility customizations out of the library into their own JS file so that it's clear what has been modified about the original library.
Comment #7
mark_fullmer