Jump to content
Search Community

Okano

Members
  • Posts

    2
  • Joined

  • Last visited

  1. I'm sorry. This issue has been resolved. I had coded the following in css. html, body{ width: 100%; height: 100%; overflow-x: hidden; position: relative; } Removing the "overflow-x: hidden;" in the html in this one works correctly. html{ width: 100%; height: 100%; body{ width: 100%; height: 100%; overflow-x: hidden; position: relative; } } Is this behavior a specification?
  2. const boundElements = [ '.news-list>a', '.sc-3>.box-area>.box', '.sc-4>img', '.sc-4>.img-area>picture>img' ] boundElements.forEach(element => { gsap.utils.toArray(element).forEach((el) => { gsap.to(el, { scale : 1, autoAlpha: 1, duration: 0.2, ease: "back.out(2)", scrollTrigger: { trigger: el, start: 'top bottom', toggleActions:'play none none reverse', markers: true } }); }); }); We are currently having trouble with scrollTrigger not responding on one site. The code is simple and works fine on desktop and emulator, but not on the actual device. The markers are displayed, so it appears that gsap is not locating the display area or content, rather than a loading issue. I have a feeling that there may be a style specification that is causing this problem, as another site that does the same thing displays the code correctly. Are there any such conditions?
×
×
  • Create New...