You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree in general going back to the previous node makes sense. This way histroymap better reflects the logical flow; currently it is very much time oriented (going back adds a new node). The logics for this is in hmController.js and the code is not very clean after new changes being constantly added :-).
I'm also thinking about if we need other status attributes for the node (besides clicked)? For example to distinguish if a page has ever been opened? It would also be interesting to capture the time the user spends on the tab?
Yes, the old extension tracks whether a page ever becomes visible. If we add this back, it would be interesting to track how long user spends on that page (actively). Can you create a new issue for the page open time?
I agree in general going back to the previous node makes sense. This way histroymap better reflects the logical flow; currently it is very much time oriented (going back adds a new node). The logics for this is in
hmController.js
and the code is not very clean after new changes being constantly added :-).Yes, the old extension tracks whether a page ever becomes visible. If we add this back, it would be interesting to track how long user spends on that page (actively). Can you create a new issue for the page open time?
Originally posted by @kaidatavis in #135 (comment)
The text was updated successfully, but these errors were encountered: