Blank space with naked header

[noxdiurna]

Just realized that the “going crazy” thing is specific to Safari on MacOS. Apparently on Chrome and Firefox, it works perfectly (couldn’t try it on IE).

#header-section.header-6 #header {
  transition: all 0.5s ease-in-out 0s;
}

Otherwise, your latest recommandation doesn’t seem to animated the logo as the above modification does.

[Kyle – SUPPORT]

Please can you provide me with a login so I can try different css until it works?

– Kyle

[noxdiurna]

This reply has been marked as private.

[Kyle – SUPPORT]

Please check now

– Kyle

[noxdiurna]

It is really bothering me to continue hassling you but it still is as smooth as I wish.

Here is what I see after your intervention.

[video src="http://www.minoeurope.com/bug.m4v" /]

With your previous recommandation
`#header-section.header-6 #header {
transition: all 0.5s ease-in-out 0s;
}

this is what I see on Chrome and Firefox.

[video src="http://www.minoeurope.com/nobug.m4v" /]

[Kyle – SUPPORT]

And which one do you prefer?

– Kyle

[noxdiurna]

Well, the objective is to get the animation on the logo to work on Safari as it does on Chrome and Firefox (video 2) if it is technically possible.

For the info, this is what happens on Safari if I used the codes mentioned above that works like a charm on other browsers.

[video src="http://www.minoeurope.com/safari.m4v" /]

[Kyle – SUPPORT]

The issue is the padding, to make the logo transition like you want it to, you have to set the padding to ease, however that causes the issue in safari.

– Kyle

[noxdiurna]

Thank you for the explanation. But considering that the ease transition effect on the logo on your naked header example page works perfectly on Safari, can I change the picture size, or replace parallax by video to resolve the issue?

[Kyle – SUPPORT]

The demo is using an old version of the theme where the structure is slightly different. Changing the parallax type will not make a difference to the header transition

– Kyle

[noxdiurna]

OK… So that means that I will have to either wait for Safari to update and solve the issue (if it does) or wait for you to figure out how this is to be bypassed?

[Kyle – SUPPORT]

Yes I will look into another method

– Kyle