Skip to main content
eug_k
Level 2
Oct 16, 2015 2:26 AM UTC
Solved

Parsys container location

Hi.

I've created an component, which have CSS property { floaf: left}. When I place it to parsys, parsys container move at the top. Please see screenshots. On the second I've deleted float: left property.

[img]1.PNG[/img]

 

[img]2.PNG[/img]

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Ove_LindströmAccepted solution
    Level 6
    Oct 16, 2015 2:26 AM UTC

    Yes, that is correct. AEM adds quite a lot of "decorators" to the markup that you have to take in consideration when you write the CSS. There is an option to have no decorations in a component. Take a look at https://dev.day.com/docs/en/cq/current/developing/components.html and search for cq:noDecoration.

    However, my opinion (and I fight with every new front end developer that starts with AEM) is that you should have a markup and a CSS that makes it look nice both in author in edit and priview modes and in publish.

    View in thread

    4 replies

    eug_kAuthor
    Level 2
    Oct 16, 2015 2:26 AM UTC

    Thank you.

    I will look for a solution.

    Translate
    Ove_Lindström
    Level 6
    Oct 16, 2015 2:26 AM UTC

    Is this in edit mode or in preview mode?

    Have you considered the div tags that are used by the parsys and the extra divs that are used by the author environment in your css?

    Translate
    eug_kAuthor
    Level 2
    Oct 16, 2015 2:26 AM UTC

    It is in edit mode.

    I suppose that location of this block is calculated automatically somehow.

     

    [img]2013-08-09_164525.png[/img]

    Translate
    Ove_LindströmAccepted solution
    Level 6
    Oct 16, 2015 2:26 AM UTC

    Yes, that is correct. AEM adds quite a lot of "decorators" to the markup that you have to take in consideration when you write the CSS. There is an option to have no decorations in a component. Take a look at https://dev.day.com/docs/en/cq/current/developing/components.html and search for cq:noDecoration.

    However, my opinion (and I fight with every new front end developer that starts with AEM) is that you should have a markup and a CSS that makes it look nice both in author in edit and priview modes and in publish.

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...