max-nextcloud
max-nextcloud
Since this does not fix the 403s fully, there's no rush to get it into todays RC anymore. I'll fix the tests and see if it fixes https://github.com/nextcloud/collectives/issues/1114 .
I fixed quite a few of the cypress tests and the failing ones are also failing for me locally. One major issue remains though. When typing at the beginning of...
> One major issue remains though. When typing at the beginning of the heading nothing happens. I suspect this is due to the slightly different markup: I figured it out....
> The push request (with HTTP 403) seems to come from nowhere (????). It seems to stem from an awareness update. (`this._awarenessupdateHandler` in the trace). When the yjs websocket provider...
The log files pasted in the issue description look like an unexpected 404 response. Those will probably not show in the logs.
Sounds like a load order issue when initializing the different apps. In particular seems like text app is initialized after `createEditor` is called.
Thanks for your report @Coqorico - I was able to confirm this even in collectives itself using the smart picker to link to another collectives landing page. In the end...
Closed too early. There was a similar issue created by the latest version of the collectives app. But this is a regression from moving the width toggle into the toolbar...
Since we do not have the toolbar for plaintext files I suggest we put the full width toggle next to the save indicator. Also noticed the drag handle is showing...
WidthFull and WidthNormal seem like a good choice for icons: