Add subtractIdleTimeoutOnIdle flag

[d9k]

1) With new flag

Initialization

timeout: 1000ms
subtractIdleTimeoutOnIdle: true

Test algo

1. active 5000ms
2. idle 2000ms

Expected result

getTotalActiveTime(): 5000ms
getTotalIdleTime(): 2000ms

2) Without new flag

Initialization

timeout: 1000ms
subtractIdleTimeoutOnIdle: false

Test algo

1. active 5000ms
2. idle 2000ms

Expected result

getTotalActiveTime(): 6000ms
getTotalIdleTime(): 1000ms

[SupremeTechnopriest]

Im pretty sure this is the default behavior. Looking at my tests, the idle time isnt timestamped until after the idle event fires. Meaning the timeout value counts toward active time and not idle time. Can you create a code sandbox that demonstrates the issue?