nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue when applying Font datum in appearance tab to Textarea datum in content tab

Sanjoy

I have two component in a page.
First is the header component which includes a CSS which has class defined for

tag.

Second component is a text component which has textarea datum in the content tab and font datum in the appearance tab. It does not have any CSS applied.
In the xslt i apply the slected font to the values entered in text area. The edit window shows the font datum color / font / fontsize being applied on the Text area value.

But when previewed, the font datum doesnot seem to apply on the text area values. This is happening only for Textarea datum. String datum is working fine..
Is it due to the default

tag that gets added with the textarea datum??

Find more posts tagged with

Comments

Sanjoy

Sorry: P tag got deleted in the previous msg. pls refer below.

I have two component in a page.
First is the header component which includes a CSS which has class defined for P tag.

Second component is a text component which has textarea datum in the content tab and font datum in the appearance tab.
In the xslt i apply the slected font to the values entered in text area. The edit window shows the font datum color / font / fontsize being applied on the Text area value.

But when previewed, the font datum doesnot seem to apply on the text area values. This is happening only for Textarea datum. String datum is working fine.. Is it due to the default P tag that gets added with the textarea datum??

shanon

Hi Sanjoy,

Can you please attach your CSS and .component file to this thread so we can take a look?

Thanks,
Shanon

rexstaples

It is likely that the textarea control is adding its own style rules which are overriding the styles you've defined in your css block. If you could supply us the HTML source that would reveal the problem as well.