Hi, I'm trying to set up an event capture custom form in 2.20. It looks like a style="100%" attribute is added directly to all input elements, making it impossible to use use css classes in the custom form. Unless it has changed recently, this has always been possible in the aggregate custom forms and can be quite useful. Would it be possible to make it to work in a similar way for tracker custom forms?
A cheap and cheerful workaround could be to append ‘!important’ to the css statements which you need to override. It should force your style regardless of the specificity of the selector in the original stylesheet.
Hi, I’m trying to set up an event capture custom form in 2.20. It looks like a style=“100%” attribute is added directly to all input elements, making it impossible to use use css classes in the custom form. Unless it has changed recently, this has always been possible in the aggregate custom forms and can be quite useful. Would it be possible to make it to work in a similar way for tracker custom forms?
Normally we don’t style custom form, it is up to the user to style.
···
On Mon, Sep 21, 2015 at 3:37 PM, Halvdan Grelland halvdanhg@gmail.com wrote:
A cheap and cheerful workaround could be to append ‘!important’ to the css statements which you need to override. It should force your style regardless of the specificity of the selector in the original stylesheet.
Hi, I’m trying to set up an event capture custom form in 2.20. It looks like a style=“100%” attribute is added directly to all input elements, making it impossible to use use css classes in the custom form. Unless it has changed recently, this has always been possible in the aggregate custom forms and can be quite useful. Would it be possible to make it to work in a similar way for tracker custom forms?
Abyot, yes, that’s also what I thought, it defeats the purpose of the custom form.
Halvdan, thanks, didn’t think of that - will do that in the interim.
Olav
···
On Mon, Sep 21, 2015 at 3:37 PM, Halvdan Grelland halvdanhg@gmail.com wrote:
A cheap and cheerful workaround could be to append ‘!important’ to the css statements which you need to override. It should force your style regardless of the specificity of the selector in the original stylesheet.
Hi, I’m trying to set up an event capture custom form in 2.20. It looks like a style=“100%” attribute is added directly to all input elements, making it impossible to use use css classes in the custom form. Unless it has changed recently, this has always been possible in the aggregate custom forms and can be quite useful. Would it be possible to make it to work in a similar way for tracker custom forms?