This is by design though. We have a debounce that only injects history when your browser settles?
@saquetim recently ported this off widgets to Ember, but I am not noticing anything different here with our behavior than what it was previously?
This is by design though. We have a debounce that only injects history when your browser settles?
@saquetim recently ported this off widgets to Ember, but I am not noticing anything different here with our behavior than what it was previously?