Forum | Appery.io

Hello,

I have weird styling problem. Somehow I am unable to change font size of one of the labels in my app. In the Appery builder size is set to 22px, but when I open the app in web preview the size is incorrect.

This is what I see in web preview:

and this is the Appery builder view:

I checked the source css generated by Appery and this is the part responsible for styling of the label in question

/* ArtEqC */
.ViewList_ArtEqC {
font-weight: normal; text-align: center; font-size: 16px;
margin: 0px 0px 0px 0px;
word-wrap: break-word;

It is somehow related with the label name. Once I change the name to anything else the styling is applied and the size is displayed correctly. Looks like the builder keeps that old name somewhere and generates the css regardless on what is actually in the app project.

Tried to flush browser cache, undo all source changes, refresh etc. Nothing helped.

Can you please help me? I would like to avoid changing source css to fix it.

My app is shared with the support (3mamcukier).

Cheers,
Adam

Hi Adam.
We'll take a look.

Adam,

Did you change source files?
Please undo all changes: http://docs.appery.io/tutorials/sourc...

No Katya. As I wrote I tried to undo all source changes (just to be sure).

Here is my source tree, as you can see no blue items indicating source modifications.

Adam,

Please try cleaning cache, I see 22px font.

Hi Katya,

Do you mean browser's cache? I already did this. I also tried to open it via Firefox (fresh install). Here is what I see:

Also Appery tester on iOS shows 16px instead of 22px.

Any ideas?

Adam,

This is pretty strange. Please rename or add custom CSS. Let us know if this helps.

Yes. I agree. Once I saw it I immediately know it is not going to be easy...
Thanks anyway. I will follow your advice.

The problem was related to elements naming. Somehow Appery builder let me create two elements with exactly the same name on the same page. Normally it warns you that names are identical and will not let you proceed with name changing. But in my case the second element was created via custom component which was then broken apart and the second name landed on the page...
After renaming problem was gone.

Hello! Thank you for update! We'll test it more.