Jump to content
Search Community

mimeartist

Business
  • Posts

    133
  • Joined

  • Last visited

Posts posted by mimeartist

  1. One question on this, if I'm calling this when the user uses a finger press for iPad etc. what the best method of avoiding the autoKill thinking that the touch is actually a request to kill? Should I only be using touched for example?

     

    I spotted someone else with this issue a while back but it came to a headend.

     

    Thank you.

     

     

  2. Thanks Rodrigo,

     

    I mistakenly had the autoKill outside of the scrollTo, like this...

     

    //DON'T DO THIS//

    gsap.to(window, {
                duration: 1,
                scrollTo: '#anchor' + jumpChapter,
                autoKill: true
            });

    //DON'T TO THIS//

    • Like 2
  3. Have searched around and have seen various topics about interrupting scrollTo, but they seem to offer bespoke versions of the gasp scrollTo plugin and are a few years old... What is the latest way to interrupt a scrollTo... e.g I've clicked a link to scroll to a point on the page, but then decided to scroll, is there a setting for this now, or should I just listen for a scrollwheel and then kill the tween?

     

    Want to keep it as simple as possible if I'm able.

  4. thank you, that works.

     

    Is there no other way of parsing a value using my for loop, as I may not want to use stagger as I'm going to be using it for things that also aren't splitText etc?

     

     

  5. Having a bit of a brain melt with this having not done any gsap for a while...

     

    i'm trying to see when each tween in a loop of stuff starts by returning it's index, or even just it's ID, so I can then get various values from it...

     

    I'm actually using splitText, but this is a very simple version of what I'm trying to achieve... how do I get the index of the for loop when each tween starts?

     

    Thank you!!

    See the Pen yLQPxJg by mimeArtist (@mimeArtist) on CodePen

  6. Ok, in this case I think it's better I not post any more pens as it's going to confuse things even more... they're all the same codepen which makes describing this even harder, so even though it's possibly not a gsap issue, it perhaps comes across as one because the embeds are acting strangely and giving false negatives.

     

    So....

     

    1. On this page we're on now, there are several (now 3 since your last post) embed code pens called Image Parallax (url ending /PoOpobM).

     

    2a. The second of these code pens intermittently doesn't work in safari.

     

    2b. On my daughters iMac the 2nd one doesn't seem to ever work with the mouse wheel scrolling.

     

    2c. On my MacBook, it's intermittent with the trackpad scroll wheel (but more often that not it doesn't work) 

     

    3. When opening the codepen in a new window it works every time (only tested on my iMac)

     

     

     

  7. No... sorry... the two embed on this page are of the mountain parallax scroll demo, the first one works in the page but the second one doesn't. So I assumed they were different demos. However when I looked at the URL's they were the same. e.g I use the scroll wheel over the one at the top of this page, and it scrolls, but the second doesn't.

     

    The second embed (Posted Saturday at 01:12 AM) doesn't work but the first does. It obviously works when you click 'edit on codepen' and it opens in a new window.

  8. 50 minutes ago, GreenSock said:

    Are you absolutely positive that you cleared your cache and aren't accidentally using an old file? I'm on a Mac, Safari 16, and it works great. Scrolls fine. Can you also please confirm which URL you're looking at exactly? 

     

    Just tried it again on my daughters iMac that has never been on this page, and it was working 'occasionally'... however it does work when you click and open it in it's own window?!?  Sorry for possibly giving a false negative, but perhaps it's to do with the embed... one one occasion it worked when I clicked the 'rerun' button while embedded on the forum... they both work when opening in a new window.

     

    Update (as writing this) Was just about to post the two embeds to show the one that works and the one that doesn't when embedded and realised they're the same embedded URL... so it must be something weird going on with the embeds in the forum? 

     

  9. On 9/17/2022 at 1:12 AM, GreenSock said:

    Hm, are you positive? With my workaround in place, I can't seem to break it. Got a minimal demo I can look at that shows the workaround in place but with it still broken in Safari 16? 

     

    I just updated the CodePen-only beta file with the workaround (internal) and it seems to work for me: 

    https://assets.codepen.io/16327/ScrollSmoother.min.js

     

     

     

     

    This demo doesn't scroll on my Mac... also I'm a little confused about whether I've been using normalise or normalise Scroll... so will need to test my stuff again just to make sure I've not been testing without having it set etc... I think when normalizeScroll is correctly set the url bar in safari on an iPhone no longer shrinks, interestingly (From the documentation it previously stated this was not possible to stop from shrinking)

  10. The workaround doesn't work for me, but I've been doing lots of workarounds myself with parts of it, so I wouldn't take that as written. One of the issues I've resolved is by scrolling using gsap and scroll to, rather than the scroller, and that seems to iron out issues with the normaliseScroll I was having and I can still have the nice smoothness.

  11. Wondered why normalizeScroll wasn't working... was using the English spelling normaliseScroll...

     

    Fixes my issue for MacOS, however 'normalizeScroll' is now breaking my scrollTo with smoothscroll on iOS... It seems to not want to redraw the screen (I've a fixed image underneath the scroller, and it doesn't remove it?)

     

    Is there a simple way of normaliseScroll only run on mobile?

     

    James

  12. Is anyone else getting weird results on Safari with the new version 16.0.... I've been working on a site for the last couple of weeks and everything was fine, but today I've noticed when I scrolled on my build that it wasn't scrolling?!?!

     

    I can't share the code... however when I looked at this demo... it's working in Chrome but not Safari? Anyone else getting the same?

     

    See the Pen PoOpobM by GreenSock (@GreenSock) on CodePen

  13. Hello,

     

    Is it possible to only have data-lag to work when scrolling down? eg when scrolling up it is normal? I really like the effect I'm getting when I scroll down as my text all cascades nicely into place, but in the opposite direction (scrolling back up the screen) content is obviously overlapping 

     

    Thank you,

    James

    NFTs

    I've started created NFT artworks, mainly through procreate as it's nice to get away from coding ocassionally.

     

    https://www.hicetnunc.xyz/tz/tz1ZsNvZKUveN7FjRhMHTm9NiAUNAmrwdFKV

     

    However, they're now allowing HTML NFTs so I'm looking to create some interative pieces, just enquiring, does anyone here have any experience in creating them, and if I wasnt allowed to link to external libraries, as a business user am I allowed to include the code within my NFT?

     

    This is all very new, so I'm just enquiring before just going ahead and doing stuff.

  14. Thank you both,

     

    I have quite a few items on screen, so figured saving a few milliseconds on each might make things even smoother... it's smooth on my 5 year old iMac so not to  bothered... but it's nice to get it as trim as possbile before launch rather than after :)

     

    So just to confirm - it's fine to use the id then class, and right to left is unlikely to make much differnce?

  15. Just trying to squeeze the last drop of speed out a project...

     

    Reading up on CSS speed checks, I was surprised to read https://css-tricks.com/efficiently-rendering-css/ that in CSS you put the class before the ID as it renders right to left, I'd imagine this is not as important as it once was - However thought I'd ask... which is the quickest way to animate a class with an ID div...

     

    Is it (as I use presently)

     

    gsap.to('#circle_logo .roundTextShadow',theSpeed, { 'fill':theTextColor});

     

    or is it, as per CSS in the document, 

     

    gsap.to(' .roundTextShadow #circle_logo',theSpeed, { 'fill':theTextColor});

     

    I imagine GSAP is doing all it can to speed things up, so just wondered out of interest whether this is something I should be considering

     

     

     

  16. This is perfect, thank you Zach, i was trying to make sure this would work with ipad etc. and it seems to, that's why I was tying it in with draggable, so you could distinguish between dragging and clicking.

×
×
  • Create New...