In T73490#872409, @Daniel Pratt (Danl) wrote:

I made a request for help and was emailed back for more information regarding my request. [...] Can you help me with this?

I made a request for help and was emailed back for more information regarding my request. I cannot seem to reply back with the information that was needed. The email is blocked. So how can i email back to Robert Guetzkow. I tried to drag and drop it into this window, but all that it put in was a number. So did my reply get to Robert Guetzkow or not. Can you help me with this?

Please don't close Blender Cloud bug reports, better leave that to the Blender Cloud team.

@Evan Wilson (EAW) Please don't close Blender Cloud bug reports, better leave that to the Blender Cloud team.

This is working with Firefox 72.0.2 on Win 10

Right.

Hi, thanks for your patch.

Moving to the workboard to keep in mind for the new design system.

Archiving this 3 year old task. This issue should be tackled in the new design system.

Fixed in production.

I can't work on this at the moment, but will keep this task in the backlog since this is part of the design system in Attract/Pillar/Cloud which is soon to be worked on by Michael at the Blender Institute.

Not sure what the status is of this task, and how much is already done. Archiving for simplicity.

The issue has been addressed by raising the token time limit several months ago. Feel free to reopen if the problem persists.

This issue was old and is now solved.

@Francesco Siddi (fsiddi) Please describe the error in more details as you can, including system info, some example & screen shots and so on.

Any resolution here? Triage at some reasonable priority?

I started looking into this. The issue can be fixed by:

This report is no longer valid with the new navigation design.

This has been fixed time ago. If it's still an issue please feel free to open.

Hey there @Tobias Johansson (mutze) - I think you actually fixed this issue. Could you confirm?

Could you outline the reasoning behind storing the watch progress in the user document instead of in the node docs?

Sounds good. We should discuss how to handle node_type properties overrides (for example predefined values, or allowed values).
Probably this makes "migrations" easier, and reduces complexity when validating nodes so it's really exciting!

Awesome! I add a comment here, to be discussed tomorrow.
Could you outline the reasoning behind storing the watch progress in the user document instead of in the node docs?
I think that storing such info in the node docs would allow for simpler/faster queries both when fetching an individual video and when fetching a series.

I'm working on this in the wip-video-progress branch. We're not storing progress in local storage, but actually in the database, so that it's independent of the machine you're viewing the video on. It's implemented as VideoJS plugin, so it should work in all supported browsers and be independent of the exact element IDs etc.