
admnrqst
New Member
Hello
as the title says: when resizing browser (also the editor by choosing tablet or mobile view) the header adds an extra full screen white element...
...that is gone when the browser left resized and the page gets refreshed.
Very interesting fact: I use two "header" templates. One is for the start page and for articles which is working fine (background is transparent by using Sticky Header Effects for Elementor) and the other is for the subpages. This latter seems to be broken, but the only difference between the two is that the first has the Sticky Header effects activated, has a bottom margin of -70px and nothing else. This is very annoying and I can't solve it.
There you go, this is the page:
https testinstallation (dot) online/
And here is one of the pages where the problem occurs:
https testinstallation (dot) online/cannabis-inhalative-anwendung
Please note that I'm aware of the Uncaught TypeError which is not causing the above problem since it is everywhere on the page.. The solution to that will be implemented at a later point.
Thanks very much for looking into this! Highly appreciated.
Greetings,
Adam
as the title says: when resizing browser (also the editor by choosing tablet or mobile view) the header adds an extra full screen white element...
...that is gone when the browser left resized and the page gets refreshed.
Very interesting fact: I use two "header" templates. One is for the start page and for articles which is working fine (background is transparent by using Sticky Header Effects for Elementor) and the other is for the subpages. This latter seems to be broken, but the only difference between the two is that the first has the Sticky Header effects activated, has a bottom margin of -70px and nothing else. This is very annoying and I can't solve it.
There you go, this is the page:
https testinstallation (dot) online/
And here is one of the pages where the problem occurs:
https testinstallation (dot) online/cannabis-inhalative-anwendung
Please note that I'm aware of the Uncaught TypeError which is not causing the above problem since it is everywhere on the page.. The solution to that will be implemented at a later point.
Thanks very much for looking into this! Highly appreciated.
Greetings,
Adam