Problem/Motivation
The alignment of radio and checkbox elements within webforms using Civictheme appears to be misaligned. Instead of being displayed inline with their corresponding labels, these elements seem to be misaligned, causing a discrepancy in the layout. This issue undermines the visual consistency and usability of webforms created with Civictheme.

Steps to reproduce
- Visit a webpage utilizing Civictheme, containing a webform with radio or checkbox elements.
- Observe the layout of the radio and checkbox elements in relation to their labels.
- Notice that the radio and checkbox elements are not properly aligned with their labels.
Expected outcome
The radio and checkbox elements within the webform should align horizontally with their corresponding labels, ensuring a cohesive and intuitive layout. Users should be able to interact with these elements seamlessly, enhancing the overall user experience of the webform.
Additional Details
This issue can be observed on the Civictheme demo website at https://www.civictheme.io/subscribe.
| Comment | File | Size | Author |
|---|
Issue fork civictheme-3432290
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
joshua1234511Comment #3
fionamorrison23 commentedComment #5
joshua1234511@alexskrypnyk
The wrapper https://github.com/civictheme/uikit/blob/main/components/02-molecules/fo...
for radios and checkbox need to be 'flex'
Reason: https://github.com/civictheme/uikit/blob/main/components/02-molecules/fo...
Label is not printed within the input element but rather outside.
Content is never passed to https://github.com/civictheme/uikit/blob/main/components/02-molecules/fo...
rather label has its own component 'form-element-label'
Comment #6
joshua1234511Comment #7
alex.skrypnykThe work required here would be happening in the UI Kit.
@fionamorrison23
We can have a hotfix for this in 1.7 or we can wait until 1.8 to get it properly fixed with all the other work done for form elements.
If we to do the hotfix, that code will be removed in the 1.8, so not a reusable piece of work.
Could you please advise on the priority of this one.
Comment #8
alex.skrypnykImplemented and will be released in 1.8
see https://www.drupal.org/project/civictheme/issues/3415674
Comment #9
alex.skrypnykComment #11
fionamorrison23 commented