Closed (fixed)
Project:
Workbench Access
Version:
8.x-1.0-beta4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2021 at 14:09 UTC
Updated:
20 May 2022 at 14:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
prudloff commentedComment #4
agentrickardWhat version of Drupal?
Comment #5
prudloff commentedWe are using Drupal 9.1.4.
Comment #6
agentrickardThanks!
Comment #7
agentrickardSo, I have a philosophical problem with this issue.
- Claro is experimental
- Claro is what changed the form / class structure.
- This works fine with Seven, as intended.
So what, exactly, are we supposed to do here?
Seven:
I am not fixing one to break the other.
Comment #8
agentrickardComment #9
larowlanCan we have our own attribute, eg a data attribute, and target that, rather than rely on classes added by the theme?
Comment #10
agentrickardOr a class that we add directly from the $form that is only used as a target, but doing so ignored the bounding DIV.
Using the `.js-form-item-editors-add` class(es) seems to fix the issue.
Comment #11
agentrickardNew version with
e.preventDefault();added.Comment #12
larowlanLooks good to me
Comment #14
agentrickardCommitted.