Problem/Motivation

Currently, when CivicTheme encounters a form element that it does not support it renders a default textfield form input. This happens with non-standard form elements that are rendered on the front-end.

When I add conditional elements for webforms and they are not showing / hiding based on conditions as expected

When I add markup fields from webform and note that they do not render correctly.

Steps to reproduce

Add conditional elements for webforms and note that they are not showing / hiding as expected.

Add markup fields from webform and note that they do not render correctly.

Proposed resolution

1. Create an opt-in system (setup in CivicTheme) that allows Drupal to provide templates for form elements that are not directly supported CivicTheme.
2. Update the form preprocessing system to allow attributes to be correctly added by modules and form builder layers by Drupal and are not restricted.

Note this fixes the related issues

PR for community review / feedback: https://github.com/civictheme/monorepo-drupal/pull/1306

User interface changes

API changes

No API changes, this should work as expected

Data model changes

No Data model changes

Comments

richardgaunt created an issue. See original summary.

richardgaunt’s picture

richardgaunt’s picture

richardgaunt’s picture

  • 69fccfe8 committed on 1.x
    Issue #3486893, #3478484, #3483064, #3415662, by joshua1234511,...
fionamorrison23’s picture

Issue tags: +civictheme-release-1.9
richardgaunt’s picture

Status: Active » Reviewed & tested by the community
richardgaunt’s picture

Version: 1.8.2 » 1.9.0
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.