When i return the scroball in a browser, a very fast imbalance is observed with images of slider: http://www.mirandalifestyle.com/CompanyDetail.aspx
Please see the attachment.
Regards
Pavel
7 replies · opened Jun 15, 2016
When i return the scroball in a browser, a very fast imbalance is observed with images of slider: http://www.mirandalifestyle.com/CompanyDetail.aspx
Please see the attachment.
Regards
Pavel
When you return the scroball browser, a very fast imbalance is observed with images of slider: http://www.mirandalifestyle.com/CompanyDetail.aspx
Please see the attachment.
Regards
Pavel
Hello,
Simply add the following code just after the </header> Tag:
This will definitely fix the issue. Let us know if we can help you with anything else or if you find any further issues.
Hello:
Thank you for your prompt assistance. The display error has decreased but still remains. See attached image and link: http://www.mirandalifestyle.com/CompanyDetail.aspx
Regards
Pavel
Hello:
Any response here? Please, is urgent.
Regards
Pavel
Hello,
We have checked out this for you but this is not actually an Issue but the Default Behavior of the Header Transition and the Slider Parallax Functionality. There are 2 Options to stop this:
#header,
#header #header-wrap {
-webkit-transition: opacity .3s ease;
-o-transition: opacity .3s ease;
transition: opacity .3s ease;
}This will definitely work fine. Let us know if we can help you with anything else or if you find any further issues.
Hi:
Thank you. Both solutions work fine What is the difference between them? What do I lose by eliminating "Header Transition" or "Slider Parallax Functionality"?
Regards
Pavel
Hello,
Disabling the Slider Parallax Functionality is a more recommended solution since disabling the Header Transition will make the Header slightly jump on Sticky.
Let us know if we can help you with anything else or if you find any further issues.
Have the same question, or something new?
Sign in to the Canvas dashboard to reply or open your own topic. Canvas owners get direct help from the SemiColonWeb team.
Reply on the dashboard