So, this issue seems related to the iframe setting at backend of Hype wordpress plugin.
2#
IT is not added by myself, it is handled by Tumult Hype Animations Plugin.
The real reason might be as following reason:
There are two layout:
The mobile layout height is 7500, and the pc layout height is 8000.
and only 8000 is in APPLIED if the project document is set as Iframe at the backend of Hype wordpress plugin.
But only 8000 seems to be applied for both mobile and pc layouts in case of Wordpress.
@Daniel, does that mean this issue is related to the Hype wordpress plugin and it is needed to be upgrade?
These two issues only happen when it set as Iframe.
Since it has to be set to iframe for "Add a container around the animation" to make the font color gradient working, in this case, only Desktop layout height will be applied both for mobile and desktop too.
Just a side not: @Daniel explained multiple ways to embed Hype in WordPress … iFrame is only one of them. Using bold font seams very demanding … (off topic).
I wouldn’t go with iFrame and just include the styles used in head into your “additional CSS” in the WordPress customizer.
1# For commercial wordpress sites, there are always several guys works on it, not like personal blog site. Cross managing might cause potential problems.
2# Themes are always kept upgrading, but there might be some issue with new latest version, and we always need to switch different themes to check issue.
3#For different themes, there are different ways to insert custom CSS, and might we need third party plugins to insert CSS for some of theme.
Anyway, the issue should be resolved within limitation itself, otherwise, it might become quite complicated.
As to these two ways:
I found these two ways are PRACTICALLY same after my test, since we need make three settings for BOTH of them to make them working:
Uncheck "protect from external styles"
Check "position with CSS left/top" to make it work with Firefox.
Then put it into a style tag inside of Hype. Like Daniel suggested. Don’t use the iFrame in that case. The styles only need to be included once in a first scene (or once per layout if the first layout is already responsive).
Actually, It works in preview mode, but not work in wordpress.
To make it works on our wordpress site, I found it has to be set as iframe on Tumult Hype Animations as following screenshot, otherwise, the gradient style setting will not work :
Do you mean, the style tags should be removed from mobile layout?
For test purpose, I already upload a document for your test, and you will note I already set desktop layout as responsive and removed style tags on Mobile layout, here is the screenshot :
Thanks, I see it now. Viewport Actions are currently based on the document and not the window; this effectively means they can't be used correctly in iframes. It sounds like using the <div> method for the wordpress plugin will solve a lot of the problems (but may cause others for you based on how your site is made).
There is a newer technology called IntersectionObserver that can be a solution to this problem. We plan to adopt it for Hype's waypoints, but until then you can manually use it. I believe there's a couple examples in the forums with an "IntersectionObserver" search. Just be aware it does require semi-newer browsers to use.
Please read my replies… use the !important keyword on the styles. You are using the !important keyword only on some style rules not all… specially the background rule and text mask etc.
Screenshots are not helping. Please only include when necessary and please learn to use the Browser Console and Inspector. They can tell you a lot about style rules and what is applied and not!
Thanks, I am sure that I already test to input !important for all of them, but it does not work either in this case, and I already add CSS into theme. For now, it seems it is only way to make it work just like @daniel show below, it is not perfect, but it is working way indeed:
The !important keyword is missing from every second line. Put it at the end of the lines … specially the WebKit lines and the behind the URL of the texture.
About the mentioned implementation of intersection Observer. It tracks the events and enter and exit and broadcasts them as custom behavior. The progress can also be used with a call back. These are fairly easy concepts. So If you create a square from starting at 600px with a height of 1000px and set the trigger offset to your desire … like 0.5 (middle if the screen) you get an enter custom behavior when the square touches the trigger line in the middle of the screen. Then for a height of 1000 pixel you get the progress in percent that can be used in the callback. Then you get the exit event. Technically you also get directional exit and enter events too. Thats all illustrated in the example. So include the minified version and then transfer some of the data settings from the example. If this is to much to ask maybe the project is still not well enough document for your level of expertise. I might make one explainer video on it but that might take some time so …