- Issue created by @taote
- πΊπΈUnited States mark_fullmer Tucson
Confirming 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...
- First commit to issue fork.
- Merge request !18Replace jQuery 4 deprecated array manipulation elements per... β (Merged) created by mark_fullmer
- πΊπΈUnited States mark_fullmer Tucson
Our 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 topush()
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. - Status changed to Fixed
3 months ago 5:00pm 5 August 2024 -
mark_fullmer β
committed bbd1f639 on 2.x
Issue #3460761: Module causes javascript problems in edit form
-
mark_fullmer β
committed bbd1f639 on 2.x
Automatically closed - issue fixed for 2 weeks with no activity.