max-nextcloud

I guess one can argue whether this is a bug or an enhancement. Technically it enhances the direct editing API. Inside notes from a user perspective its a bug.

Lemme check what happens here @max-nextcloud **update**: Interesting... i don't get a notification either. I would have expected to get one as a way of adding this to my inbox.

> Do you have the notifications app installed locally? Ah... I see how my comment was confusing. I just tried notifications for self-mentioning on github to see how other systems...

I profiled the workspace loading some and it turns out rendering the menubar is surprisingly expensive. I experimented some with it and we can postpone that until the content has...

I just tried the following: * edit a document * disconnect (via network throttling) * type some more before reconnect button shows * cleanup document with `./occ text:reset -f 1390`...

I think we will need to separate the sync service session and the yjs session conceptually and in practice. ## Sync service session Connects all users that are editing the...

Even if we keep the yjs doc around there's still a way to be missing steps from one peer: * one client keeps edits, closes lid * some steps send...

Planning to tackle this as part of the y.js based collaboration rework in #2669. There's little use in looking into it before hand as a lot of the collaboration API...

Uh... interesting. Had forgotten about this one. It's probably still failing as my fix only applies after some document state has been saved. But it could (and probably should) be...

@mejo- Are you sure this one is fixed? Upstream issue is still open but it looks like the test was flaky because files could not be deleted during preview generation....