Jump to content
GreenSock

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

OSUblake last won the day on August 15 2019

OSUblake had the most liked content!

OSUblake

Administrators
  • Posts

    4,260
  • Joined

  • Last visited

  • Days Won

    439

OSUblake last won the day on August 15 2019

OSUblake had the most liked content!

About OSUblake

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

19,098 profile views

OSUblake's Achievements

  1. Sorry if it came off that way. I brought up CSS grid because animating tables can be very problematic. Tables were not designed with animations in mind, which is why you still have to use attributes to get some table elements to display correctly. And there is usually more than one way to solve a problem. Using CSS grid was part 1 of my recommendation. You called me a troll before I got to part 2 below. The gaps are caused because of rounding. An 81px wide element at a scale of 0.786 is 63.666000000000004 pixels. Not exactly a whole number, so you might see artifacts bleeding through. To get rid of those gaps, you can use will-change: transform; in your css. The browser can rasterize (take a snapshot) of the layout before scaling gets involved. https://developer.mozilla.org/en-US/docs/Web/CSS/will-change
  2. Why are you even using a table? Tables are designed to display data. If you want a table-like layout, then use CSS grid. https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout/Basic_Concepts_of_Grid_Layout
  3. You can't use the variable name top at the global level because it refers to something else. https://developer.mozilla.org/en-US/docs/Web/API/Window/top Just rename your top variable to something else.
  4. Not really. Google has its own walled planet sans China. I'm not saying that's a good thing... but that's the reality of the internet right now. I agree. Web components are awesome. No React. No Vue. No frameworks. Just good old fashioned HTML.
  5. Using a letter makes no sense. Numbers are your friend when it comes to repeating something... and so are loops. There are many ways to do a loop, and here is one. https://codepen.io/osublake/pen/c35a7a69af6a6db997249a6111e6f930
  6. And that's why we have AMP. At its core, Google is an advertising company.
  7. Then do the same thing. GSAP classes will be on the parent from inside an iframe. var box = document.querySelector("#box"); window.parent.TweenMax.to(box, 1, { x: 100 }); Depending on how deep your iframe is, you may need to something like window.parent.parent...
  8. You may need to use a fully qualified URI for caching to work, but this is a server question, and you will probably get a better answer on StackOverlow. https://stackoverflow.com/ Also, caching. https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching
  9. As an outsider to the banner ad industry, I will say that animated ads are very frustrating on mobile. I can deal with static ads, but I will click away from a site if it looks like the animated ads are making the site unresponsive.
  10. Why would you need to make another file? The only reason to ever create another file is for organization of your code. Make sure you proofread the file you're already working on. 'hook' can't be right. That's looking for a <hook></hook> element. Did you mean '#hook'? const scene2 = new ScrollMagic.Scene({ triggerElement: 'hook', duration: 395, triggerHook: 0.9 })
  11. Rounding error. Seems that happens in other languages too.
  12. If you need something to be sticky, just use CSS. https://codepen.io/osublake/pen/41a997ea6297132313629b608d0ba39f
  13. Yep. Works fine without ScrollMagic. A wise man once said, "You might not need ScrollMagic".
  14. Oh, I see. In that case, you might want to look at lagSmoothing ad well. https://greensock.com/docs/TweenLite/static.lagSmoothing()
  15. Any particular reason you need to know when it updates? But you can add an event listener to the ticker. https://greensock.com/docs/TweenLite/static.ticker
×