Hugh Gallagher

Hi. Thanks for the bug report. I'm not able to replicate this; If it's still a problem, could you let me know what OS and browser version you are on.

Thanks for the details. Although I have a Thunderbolt display, I can only test this on Macbook Pro with High Sierra and a Radeon 555. With that configuration it all...

There's not a lot to it, but maybe have a look where the timer is drawn; https://github.com/pughpugh/react-countdown-clock/blob/548acc55e2452a8df3a7f9097bc3abb32db037ad/coffee/react-countdown-clock.coffee#L177 There are some vague notes on building the component on the following issues....

I think I was being vague as I do not know what module system the consuming code is using; Node require vs. ES6 import. I suppose it would be best...

Sorry for the delayed response. If this is still a problem, please post an example and I will take a look.

OK thanks @zchauhan , I will take a look.

Yup. Timeout IDs need to be stored in state, not on the component definition. They are currently bleeding across instances. I think this is the cause of a number of...

Hi, Yes it was a stylistic choice to drop hours and minutes as they become exhausted. I'm not sure what you mean in regards to preventing `toFixed` on the seconds...

It seems like a sensible request and I apologies for not attending to it sooner. I might have chance to look at it over the xmas period.

No need to be quite so dramatic @sjmp . What action are you proposing would reset the timer? I've not looked at this in a while, but I believe if...