Closed (outdated)
Project:
Webform
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Jan 2019 at 22:54 UTC
Updated:
23 Sep 2025 at 13:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tostinni commentedHere is a patch to add this option back.
Comment #3
tkcent commentedPatch works as expected. This is very helpful when using CSS frameworks with grid system.
Comment #4
liam morlandIs there a reason the classes couldn't just be added in the markup?
Comment #5
lucasscPatch #2 rerolled. I'm not attaching the interdiff because there are no differences between one patch and another, but it's only changing 1 line, so you can easily compare with the first patch.
Comment #6
liam morlandPeople are able to add any classes they want to the markup they add to the page. It has been this way for a decade. Is there a reason this does not work?
Comment #7
lucasscHi, Liam!
Could you please provide some documentation or steps to reproduce?
Comment #8
liam morlandThe
markupcomponent just puts HTML on the page. Include any needed classes in that HTML.Comment #9
ravi kant commentedThe custom wrapper class can add from
Webform->Setting->form and add custom class on form attributes class.This class will add on form element.
Comment #10
liam morlandDrupal 7 is no longer supported. If this applies to a supported version, please re-open.