3 ms·

And with the timer thing you're consuming CPU unnecessarily. No timers please.

• ReactiveJelly 7y ago
  Edit: I rewrote my comment because I misunderstood yours. You could tie it to an "on-scroll" type of event, like how many text boxes will fire an event X milliseconds after a text edit event, so that they can process the text when the user is not likely to be typing. A single timer by itself won't busy-wait, but I agree that running a timer all the time is a waste. Just run it when scrolling, when CPU use will already be high.
  • winrid 7y ago
    +1 for running it after the event
    • dcow 7y ago
      WTF just no. Cancel the request once the image has left the viewport.
      • winrid 7y ago
        You mean just clear the src attribute? That would work. I didn't know the browser would actually cancel the request.