- Issue created by @Grevil
- @grevil opened merge request.
- 🇩🇪Germany Grevil
Done, this fixes the issue. Unsure on how to continue here. As said in the issue summary, field_group is very special and there is already code for it in core, might be time to reactivate ✨ Add field grouping to core Needs work , and get the whole thing in core finally.
- 🇺🇸United States smustgrave
Possible to get a test case showing this as an issue? Is it possible without field_groups/should field groups be the one to fix it?
- First commit to issue fork.
- 🇩🇪Germany Grevil
@smustgrave unfortunately this isn't possible to reproduce without field_group.
Not quite sure how to fix it in field_group itself, though. I doubt, we should overwrite field_ui.js in field_group.
- 🇩🇪Germany Anybody Porta Westfalica
Yeah really important to get this fixed, so we can get the nasty Field Group issues fixed also...
- 🇩🇪Germany Grevil
As said before, testing this would require to install the field_group issue.
- 🇺🇸United States smustgrave
Will leave it here but seems like large enough change it should have some kind of coverage in core.
- 🇬🇧United Kingdom AndyF
Possible to get a test case showing this as an issue? Is it possible without field_groups/should field groups be the one to fix it?
I just recreated the issue on 11.x and it seems to be fixed by the PR from 🐛 TableDrag JS :first-of-type issues Needs work (which includes tests).
Also updating the repro instructions: as far as I can tell you need to drag the item up for it to fail.
Should this be marked duplicate?
- 🇩🇪Germany Grevil
@andyf you are correct, I am using gin and tried to apply the core changes in their override file before, but it didn't fix the issue for me.
Somehow it does now... I guess I forgot to clear my cache, which is QUITE annoying. Thanks for the heads-up.
Here is the issue on gin's side to fix it in their tabledrag.js override: #3542075: TableDrag JS :first-of-type issues →