[Is easing functions accessible for other operations than DOM manipulation?]

Hi everyone,

 

I was about to implement something like this in my current project, but I guess the GSAP codebase already have it, is it accessible for something else than DOM manipulation?

Best.

See the Pen XWrjJVN by yyy589 (@yyy589) on CodePen

[GSAP Draggable scrollTop snap IOS bug]

Nope, it's all stuck. Also I'm using this method to avoid page jumps because of the adress bar: https://css-tricks.com/the-trick-to-viewport-units-on-mobile/

I'm using TweenLite and not TweenMax, and added:

 

Wr.addEventListener('touchmove', function(e) {
  e.preventDefault()
}, false)

Maybe it's related?

[GSAP Draggable scrollTop snap IOS bug]

Hi,

 

I'm building something like this for a mobile view (in a Vue.js webApp), everything work properly on desktop, but the snap doesn't work on Safari / Chrome mobile.
I tried many things (like using type: 'y' instead) but the problem is still the same...

 

Any help would be appreciated,

 

Thanks.

See the Pen OJLNaZw by yyy589 (@yyy589) on CodePen

[GSQP Draggable get scrollTop position on scroll event]

Hi,

 

I use the Draggable plugin locked on the y axis to manage scrolling in a section. I would like to retrieve the y position of the scrolled element to trigger an event when reaching the end of the scroll area. It's working as follow when the user drag but not when he use the mouse wheel for ex.

 

Draggable.create(Pr, {
  type: 'scrollTop',
  ...
  onDrag: function(e) {
    type: 'scrollTop',
    this.update()
    console.log(this.y)
  }
})

 

How can I get a unified way to retrieve the y position between the different events, drag, scroll, etc.

[onComplete not firing in Vue.js router navigation guards]

Ho yes! Working perfectly, thank you.

[onComplete not firing in Vue.js router navigation guards]

Hi,

 

I'm using in components navigation guards with vue router to manage transitions between vues but can't get the onComplete firing the "next" argument:

 

  beforeRouteLeave(to, from, next) {
    const self = this
    const { Im } = self.$refs
    const tl = new self.TimelineLite
    tl.to(Im, .4, {
      y: -40, 
      opacity: 0,
      onComplete: next
    })
  }

 

So I ended up with this kind of hacky solution:

 

  beforeRouteLeave(to, from, next) {
    const self = this
    const { Im } = self.$refs
    const tl = new self.TimelineLite
    tl.to(Im, .4, {
      y: -40, 
      opacity: 0,
      // onComplete: next
    })
    setTimeout(function(){
      next()
    }, 400)
  },

 

Any ideas about how I could actually trigger the "next()" argument with the onComplete callback?

Thks.