Jump to content
GreenSock

Search In
  • More options...
Find results that contain...
Find results in...

GreenSock last won the day on August 21

GreenSock had the most liked content!

GreenSock

Administrators
  • Content Count

    13,201
  • Joined

  • Last visited

  • Days Won

    412

GreenSock last won the day on August 21

GreenSock had the most liked content!

Community Reputation

8,201 Superhero

About GreenSock

  • Rank
    Administrator

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    Chicago Area
  • Interests
    Volleyball, Basketball, Christian Apologetics, Motorcycling

Recent Profile Visitors

48,266 profile views
  1. Thanks for the suggestions, @RolandSoos. I do plan to make some similar changes in the next release. 👍
  2. Maybe at some point, but as you probably know @OSUblake we've got a LOT going on at the moment so this isn't really something we can dig into right now. I can put it on the list of possible additions down the road though. 👍
  3. I'm a little confused - do you have what you need now or were you still looking for some help? I thought you were gonna post something of your own that you were trying to add anchors to, but it looks like you just copied one of our codepens that already had anchors showing. If you need some help with something of your own, just let us know and we'd be glad to take a peek. Otherwise if you're all set, even better!
  4. @knalle sure, if you provide a reduced test case in codepen or something, I don't mind taking a peek. There may be a tool in MorphSVGPlugin that'd make it a bit easier.
  5. Glad to hear you're enjoying the tools! What you're asking for isn't exactly a super simple case, but here's one approach: https://codepen.io/GreenSock/pen/vYByKZN?editors=1010 Is that what you're looking for? Hopefully it's easy to dissect. Happy tweening/dragging!
  6. Yep, I see the same thing. Ha. Yeah, that certainly seems like an incorrect namespace.
  7. Yeah, I totally get that. Makes sense. Hey, if GSAP 2.0.2 is working well for you and there really aren't any pain points, why risk the upgrade? I did put a fix in for the issue we're discussing here, so it may very well be worth the risk in this case. Let me know if there's anything else we can do. Happy tweening!
  8. It seemed like a browser (or other environment) bug where [only in that particular environment] createElementNS() produced an element whose "style" was completely inaccessible! Weird, right? I can't imagine it's related to GSAP in any way. Is there a reason you don't want to update to the latest GSAP? Just curious.
  9. Well this is pretty ambiguous because technically this is like defining two different color values that you're asking the tween to animate to at the same time - one from the className and one from the "color" you're defining in the tween itself. Like @ZachSaucier said, we really don't recommend className tweens because it requires literally analyzing every single property, finding the ones that are different and animating those. It's much cleaner to just tell GSAP the specific properties/values you want to animate (plus I think that makes your code more readable and direct - less ambiguity).
  10. Have you tried using the Draggable instance's pointerX and pointerY values? That's one of the ways it smooths out cross-browser differences. And to be clear, the docs don't indicate that the event will always have pageX/pageY values - it has no control over that. It simply passes along whatever it gets from the browser.
  11. Yeah, I'd guess that is indeed related.
  12. Is it something Draggable-related? If you need help, feel free to share more details. But yeah, I think that as long as you're trying to straddle between your own native handlers of click/touch/pointer events and using Draggable (which smooths most of that out), I'd guess you'll have your hands full
  13. I didn't have a lot of time to look at this, but there are some inherent challenges with scrolling on iOS. If you look at the scrollbar, you'll see that Draggable is indeed being responsive to your touch but iOS is counteracting it in certain cases (no doubt it's trying to be "helpful"). I'd probably avoid the whole scrollTop thing and just affect transforms instead, kinda like this: https://codepen.io/GreenSock/pen/mdbPaqv?editors=0010 Is that any better for you?
×