The "corrected" clock2.js is still wrong
Opened this issue · 0 comments
sypham2909 commented
The current clock2.js that seems "to be corrected" still have an issue. The timing is right but calling the next() method sequentially all returns the same value of the count variable due to the closure.
Tested in Chrome browser version 108.0.5359.125