[TYPO3] Marlie's forms version 4.0

[Christopher]

Hi,

On 5/19/06, Jens Gammelgaard <jens.gammelgaard at optimon.dk> wrote:
> Christopher skrev:
> > Hello,
> >
> > On 5/19/06, Jens Gammelgaard <jens.gammelgaard at optimon.dk> wrote:
> >> Peter Klein skrev:
> >> > Hej Jens. Just add som classes to the various form elements, then
> >> you can
> >> > style everything using CSS..
> >> >
> >> > Like described here:
> >> >
> >> http://www.typo3wizard.com/en/snippets/menus/mailformular-buttons-und-felder-mit-klassen-belegen.html
> >>
> >> >
> >>
> >> Hej Peter!
> >>
> >> Thanks for your swift reply, I did paste:
> >>
> >> tt_content.mailform.20.params.textarea = class="mf-text"
> >>
> >> And I tested with: tt_content.mailform.20.params.textarea =
> >> class="csc-mailform-field"
> >
> >
> > Why TWO different declarations trying to assign a class to one type of
> > element?
> >
> >
> >> In my Templates' Setup field and made a class in my stylesheet like:
> >>
> >> .mf-text { border:1px solid #333333; }
> >>
> >> Refreshed my cache - but no result.
> >>
> >> What have I missed?
> >
> >
> > You've missed the only piece of information that matters ;-)
> >
> > Did your the class attribute appear on the textarea in the html source
> > of the page in the FE?
> >
> >
> > -Christopher
>
> Hi Chrisopher!
>
> The class that appears in the FE is csc-mailform-field and I just tried
> the other one since it was mentioned in the example...
>
> So with this information - then YOU might have the last peace in the puzzle?


Hard to say; but IF the class in the stylesheet matches the class
element on the attribute in the element, AND the styles in the
relevant css declaration do not affect the element in the rendered
page, then it probably is a problem of specificity.

Got a url where this is happening?


-Christopher