The editor content does not sync on different browsers

[tiavina-mika]

Please save me some time and use the following template. In 90% of all issues I can't reproduce the problem because I don't know what exactly you are doing, in which environment, or which y-* version is responsible. Just use the following template even if you think the problem is obvious.

Checklist

• Are you reporting a bug? Use github issues for bug reports and feature requests. For general questions, please use https://discuss.yjs.dev/
• Try to report your issue in the correct repository. Yjs consists of many modules. When in doubt, report it to https://github.com/yjs/yjs/issues/

Describe the bug
The editor content is sync across the tabs of the same browsers.
But it does not sync with different browsers.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://codesandbox.io/s/github/tiavina-mika/tiptap-editor-mui
2. Open the page in another tabs
3. Write something
4. The content is shared accross the tabs
5. Open the page in another browser
6. The content is not the same

Expected behavior
The editor content should be the same on different browsers.

Environment Information

• Browser [e.g. Chrome, Firefox]
• Yjs version: yjs v13.6.10. y-webrtc: v10.2.6

[tim-hilt]

I can confirm, that I have the same issue.

Link to minimal reproduction example: https://github.com/tim-hilt/syncedstore/blob/webrtc-minimal-repro/app/page.tsx

It works with y-websocket though.

[iamnafets]

90% sure this is because the default signaling servers have crashed. Host your own and things seem to work.

[crystalthoughts]

I had problems with firefox using this library, maybe it's related.

[Vivekagent47]

@iamnafets I also have same problem, but I found out that when we console.log peers, they are being added to bcPeers, not to the webrtcPeers. But I dont know how to make them add in the webrtcPeers

{
    "added": [
        "1348b4c7-04f9-465b-98d3-55f1c211926f"
    ],
    "removed": [],
    "webrtcPeers": [],
    "bcPeers": [
        "1348b4c7-04f9-465b-98d3-55f1c211926f"
    ]
}

[Toukassay]

So any news since so long ? It seems to be quite the core functionnality of this lib, right ?

[au-phiware]

One year on, and I experience the same issue 😞

[dmonad]

The problem doesn't fix itself.

This is open source. You can fix it yourself. You may also pay me for fixing this issue. Unfortunately, none of my sponsors use this library. I only use it for demos.

I will eventually work on this. But I have higher priorities right now.

I hope you understand.

[au-phiware]

I understand. You caught me in a moment of frustration, I apologise.

Thanks for responding. Do we have any clues about where the problem lies? Do you have any intuition? I had some success using a custom signalling server, i.e., running the example server in this repo locally. I got it working between different Firefox containers (i.e., new private window) but not across different browsers. I don't see any errors, so I'm not sure where to begin.

One thought I had was, is it CORS related? But I ran the signalling server from the same domain, and then I realised that the symptoms don't make sense with typical CORS problems...

[dmonad]

My guess is that this is related to browsers supporting different max-package sizes. y-webrtc expects that messages with arbitrary length can be sent. This is, unfortunately, not the case.

My standpoint is that this should be abstracted by the webrtc library. My recommendation is to extend the peerjs library to allow arbitrary message sizes between buffers.

However, it is also necessary to research the exact problem and how browser vendors expected this to be implemented.