I think that the operation of 'float-in-bottom' doesn't work with amp viewer of google cache.
float-in effects do not work inside AMP viewer
The element remains out.
| origin AMP | AMP viewer (google cache) |
----|----
|
|
|
| https://nuxtjs-test.tanakayuki.now.sh/ | https://www.google.com/amp/s/nuxtjs-test.tanakayuki.now.sh/ |
https://www.google.com/search?q=amp-fx-collection_demo_page
↑ cahce find it via SERP
https://www.google.com/amp/s/nuxtjs-test.tanakayuki.now.sh/
<div amp-fx="float-in-bottom" class="nav__wrap">
<div class="nav__content">
content area
</div>
</div>
Maybe all browsers
I don't know but it happens in version 1910161528000
@alanorozco wasn't this fixed recently?
@nainar @alanorozco
Is this issue likely to go away?
I use this component too.
for the same effect
it still not work inside Google AMP viewer.
amp-version 1912201827130
Support for viewer is additional¹ and still pending since it was rolled back early on and wasn't resumed due to some underlying FixedLayer work occurring at the same time.
I'll prioritize this due to demand, it's mainly a refactor of previously written code.
¹For context on why the viewer needs additional support, it's mainly due to a workaround of an iOS WebKit bug where iframed documents flicker their fixed elements. (looks like this)
@alanorozco any update on this? we've just hit the same issue (but using float-in-top) so it doesn't appear to have been resolved yet
Most helpful comment
Support for viewer is additional¹ and still pending since it was rolled back early on and wasn't resumed due to some underlying
FixedLayerwork occurring at the same time.I'll prioritize this due to demand, it's mainly a refactor of previously written code.
¹For context on why the viewer needs additional support, it's mainly due to a workaround of an iOS WebKit bug where iframed documents flicker their fixed elements. (looks like this)