Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

y-webrtc doesn't work on different browsers #53

Open
apandagre opened this issue Jul 22, 2023 · 3 comments
Open

y-webrtc doesn't work on different browsers #53

apandagre opened this issue Jul 22, 2023 · 3 comments
Labels

Comments

@apandagre
Copy link

apandagre commented Jul 22, 2023

Content doesn't sync between different browser, or on the same browser when using the incognito mode.

I guess I am missing some configuration or something.

Any help would be appreciated.

    // frontend code...
    const doc = new Y.Doc();
    doc.clientID = randomInt(0, 100);

    const provider = new WebrtcProvider(room, doc, {
      signaling: ["ws://localhost:4444"],
    });
    const type = doc.getText("monaco");
    const awareness = provider.awareness;

    const binding = new MonacoBinding(
      type,
      editorRef.current.getModel(),
      new Set([editorRef.current]),
      awareness
    );

signaling server - https://github.com/yjs/y-webrtc/blob/master/bin/server.js

@apandagre apandagre changed the title y-webrtc doesn y-webrtc doesn't work on different browsers Jul 22, 2023
@SebastianStehle
Copy link

Why is this set to "wontfix"? I have the same issue and this is a critical issue, I would say.

lirsacc added a commit to lirsacc/siren-chorus that referenced this issue Nov 27, 2023
I'd prefer WebRTC over websocket here (especially as the WS
implementation isn't encrypted; however I've run into issues around
cross browser collaboration - namely:

yjs/y-webrtc#56
yjs/y-webrtc#53
yjs/y-webrtc#19

For now having websocket allows iterating on the editor and the UX until
I can look at those issues more in depth.
lirsacc added a commit to lirsacc/siren-chorus that referenced this issue Nov 28, 2023
I'd prefer WebRTC over websocket here (especially as the WS
implementation isn't encrypted; however I've run into issues around
cross browser collaboration - namely:

yjs/y-webrtc#56
yjs/y-webrtc#53
yjs/y-webrtc#19

For now having websocket allows iterating on the editor and the UX until
I can look at those issues more in depth.
@tiavina-mika
Copy link

Is it a bug? I have the same issue

@tim-hilt
Copy link

Related to #63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants