Hero Tabbed Heading gone on product pages after 1.30 update

[Swift Ideas – Ed]

Can you show me the animation on another page, not a product? Just so we can be sure we are talking about the same thing?

Sure – can you provide a link to your site for me to check?

– Ed

[contemascetti]

Sure, for me all the pages except products show the proper hero-animation on load, with exact same results on my site and atelier demo site. for example:

– http://swiftideas.com/product-category/accessories/

– http://swiftideas.com/pages/meet-the-team/

– http://swiftideas.com/shop/?product_display=standard&product_columns=2&product_gutters=1&fullwidth=0

in all these pages the hero image slides out on page load on every device/browser I use, while in product pages the hero image appears suddenly and full on load. Again, till 1.22 product pages were fine too.

For the CSS code, I’m still under construction so cannot share links yet. If you could just suggest a custom CSS code to change the height of the main header it would be great, thanks.

[Swift Ideas – Ed]

Ok thanks for the details – I have just found the issue there and resolved that.

The main header is based on the logo height in the theme options – if you reduce that you should be able to reduce the header height.

– Ed

[contemascetti]

Really glad it’s sorted.
Many thanks for your assistance.

[Kyle – SUPPORT]

Great, thanks Ed

[contemascetti]

My apologies for bothering again with this long discussed topic.

After updating to 1.50 the issue with the hero tabbed animation we discussed here is fixed (thanks), but I see that the fancy-heading animation (slide-down) is now extended also to the once static standard hero heading pages, not only the hero-tabbed ones like it was till the latest update.

I was wondering if you could please consider adding an option to enable/disable the hero fancy animation on a per page basis (with meta?), or suggest a way to disable completely sitewide if there’s no other way.
I find that with big, tall headers (600px) the animation sometimes gets heavy and slow on some machines, so I’d like to keep a static hero heading for those pages.

I tried disabling the fancy-heading transition with this css code from a forum post, but the result is a two steps, abrupt loading of the heading.

.page-heading.fancy-heading {
transition: none;
transform: none!important;
min-height: 425px;
}

Sorry again and thanks for the support.

[Rui Guerreiro – SUPPORT]

Hi,

Will forward it to Ed to he can reply.

-Rui

[Swift Ideas – Ed]

Hi there,

Can you provide an instance of it being slow on a page? We’ll check this out for you.

We’ll also add it to the list to consider adding an option to disable per page.

– Ed

[contemascetti]

Hi, thanks for replying.

My bad for the poor explanation.
For slow I mean that on pages with very big heading (600+px) there is a more noticeable delay on load created by the pull down animation, which I think is intended and indeed works great for pages like shop and products with small headers (300px) where I prefer to use this style.

But with tall, almost full screen heading pictures I feel the ‘jump’ in the two steps animation is just too big and causes an unnecessary delay on load, that’s why I had chosen a simple, static heading that loads in full instantly without pushing down the page contents.

I already created a lot of descriptive content driven, tall heading pages with the static hero heading style in mind, but now everything is moving/animating and does not fit very well anymore.

It would be of great and very much appreciated help if you could consider adding an option to get back the old choice of hero tabbed+animation and normal hero+static heading. In my opinion it was the perfect solution for different styles and tastes.

Any other solution I tried from the forums to disable the fancy animation causes problems either with desktop or mobile viewport (incorrect heading resizing, conflicts with woocommerce shop page options, etc), so I came back here to ask for help.

Please let me know if more feedback on this is welcome.

Thank you for keeping up on this.

regards

[Swift Ideas – Ed]

I agree with that. Will see what I can do.

– Ed

[contemascetti]

Glad to hear that 🙂

Thanks

[Kyle – SUPPORT]

No problem 🙂

[contemascetti]

To Ed

After checking 1.51 update I just wanted to thank you for being so open to user feedback/suggestion. Not every developer around does the same.

Didn’t expect to see the flash ‘fix’ too in this one. Peace of mind achieved 🙂

Again, thank you.

Regards

[Kyle – SUPPORT]

No problem 🙂