-
-
Notifications
You must be signed in to change notification settings - Fork 116
Issues: yjs/y-webrtc
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
The editor content does not sync on different browsers
bug
#63
opened Dec 13, 2023 by
tiavina-mika
1 of 2 tasks
Use existing (3rd party) signaling server implementation
enhancement
#55
opened Aug 29, 2023 by
WofWca
2 tasks done
Allow for or extend checking connectedness of the provider
enhancement
#49
opened May 22, 2023 by
lukashaertel
Library fails with missing global declarations when run inside nodejs (ES6)
enhancement
#36
opened May 7, 2022 by
lukebayes
Explore options for smaller footprint, browser-based webrtc clients
enhancement
#35
opened May 2, 2022 by
lukebayes
Issue when peer got reconnected after disconnected by using webrtc provider
bug
#24
opened May 10, 2021 by
abdashaffan
'peers' event on on SignalingConn emits 'added' peer from peer's close event
bug
#23
opened Mar 13, 2021 by
disarticulate
2 tasks done
Sync issues Safari ⇔ Chrome
bug
first issue
A good first issue
help wanted
#19
opened Nov 7, 2020 by
dmonad
Sync issue - yjs.dev does not sync with clients that are indirectly connected
#3
opened Feb 4, 2020 by
dmonad
ProTip!
Mix and match filters to narrow down what you’re looking for.