How would you implement throttle with leading and trailing edges for scroll?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
Leading runs immediately, then ignores calls until the window ends
WHY — JavaScript instead of guessing?
Why interviewers care about JavaScript:
question about JavaScript.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Leading runs immediately, then
ignores calls until the window ends
- 2trailing fires once more
with the last args if calls happened during the wait.
- 3Scroll position UIs usually
want both so the first frame updates and the last position is not dropped.
- 4I store lastArgs and
a timeout, which is what I sketch on a board.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Leading runs immediately, then ignores calls until the window ends trailing fires once more with the last args if calls happened during the wait.