-
AuthorPosts
-
August 30, 2019 at 2:44 pm #1132313
For years I’ve had a simple landing page to a site which forced vertical alignment of its content to the top using the commands below.
.landing_desktop.av-minimum-height .container .content {
vertical-align: top !important;
}This no longer seems to function. WHY?
Below is what is being forced by Enfold within the browser console. When I make the manual change within the console to change vertical-align: middle; to vertical-align: top; (which is the way it should be) it all looks fine again. Also, the Custom ID Attribute I had in the specific color section was no longer there. I re-input it and it does not work any longer.
.avia-section.av-minimum-height .container .content {
display: table-cell;
vertical-align: middle;
height: 100%;
float: none!important;
}August 31, 2019 at 10:07 am #1132509Support Team?? Are you there?? This is a simple question. Just trying to get my content loaded at the top of a page.
September 2, 2019 at 4:19 am #1132786Hi,
Please try this instead:
.home .template-page { vertical-align: top; }
Make sure that you delete the old CSS and JS files under Enfold->Performance before checking the results.
Best regards,
RikardSeptember 2, 2019 at 10:58 am #1132920Hi Rikard, thanks for the effort but that did not correct the problem. Content on that page is still vertically aligned middle. See below in the snippet from the browser console. Flushed cache and disabled joining and compression.
.avia-section.av-minimum-height .container .content {
display: table-cell;
vertical-align: middle;
height: 100%;
float: none!important;Please refer to other folks issues within the thread below. I am reasonably sure these issues are inter-related.
https://kriesi.at/support/topic/4-6-update-doesnt-recognize-old-custom-css-class/#post-1132942
- This reply was modified 5 years, 1 month ago by crtdude.
September 3, 2019 at 7:05 am #1133235Hi,
Please try this instead:
.home .template-page { vertical-align: top !important; }
Best regards,
RikardSeptember 3, 2019 at 10:04 am #1133294Thank you Rikard, issue fixed.
Can you explain the rationale behind changing the DeveloperID functionality? I see your javascript is targeting the page template and not the target item as we previously had done.
September 4, 2019 at 8:09 am #1133643Hi,
Great, I’m glad that you got it working. I’m not sure I understand your new question though, could you try to explain a bit further? The CSS is only targeting a class on the home page, it’s normal.
Best regards,
RikardSeptember 4, 2019 at 9:46 am #1133723We are good now Rikard, no further issue. Thanks again. Günter explained it all at the link below.
https://kriesi.at/support/topic/4-6-update-doesnt-recognize-old-custom-css-class/#post-1133483
-
AuthorPosts
- You must be logged in to reply to this topic.