-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Undoing causes disconnect #2802
Comments
Thank you for the detailed bug report. clear authorship (undo that, respectively) is the only changeset that can has zero (deletion) or multiple (undo) authors at once. However we cannot simply disable the check, because this would introduce impersonation scenarios where an author can send changes as another author. Maybe we should do this server-side instead of sending changesets. This also needs a test, but at the moment the test infrastructure cannot easily express scenarios that involve multiple clients. |
also we might want that anybody can reimport the authorship colours and not only the client that deleted them |
The issue still exists: replicated now on current develop branch (58c3154, 1.6.6+).
|
I think there is a more serious bug/outcome of this:
Causes pad to fail loading. Is fixed by restarting Etherpad... |
I put a fix in that stops a user from being able to undo a clear authorship event. This seems like the only sane way of doing this. |
People at Framasoft: would disallowing the undoing of clear autorship colors break some of your use cases? I think it's better than a crash. |
Clearing the authorship colors of a document with at least two authors, and then undoing that action caused a disconnect from the pad. This change disallows undoing clearing authorship colors in order to prevent the problem from affecting users. This is a change of behaviour, and is documented in the changelog. Fixes ether#2802 (sidestepping it).
Nope, it's good for us 👍 |
Clearing the authorship colors of a document with at least two authors, and then undoing that action caused a disconnect from the pad. This change disallows undoing clearing authorship colors in order to prevent the problem from affecting users, and adds the relative test coverage. This is a change of behaviour, and is documented in the changelog. Fixes ether#2802 (sidestepping it).
Clearing the authorship colors of a document with at least two authors, and then undoing that action caused a disconnect from the pad. This change disallows undoing clearing authorship colors in order to prevent the problem from affecting users, and adds the relative test coverage. This is a change of behaviour, and is documented in the changelog. Fixes #2802 (sidestepping it).
Turns out the fixes for this should be re-evaluated |
I reproduced this bug as well. 😢 |
Hello Etherpad Team,
We've found a reproducible bug with the clear authorship action that causes a disconnect.
To reproduce this bug :
User B should be disconnected from the pad.
Here is a relevant stack trace :
The issue seems to be in PadMessageHandler.js. The clear authorship message does not specify any author, thus not triggering the test on line 699.
However, when hitting the Undo button, two authors are specified, triggerring the error message.
Regards,
François
The text was updated successfully, but these errors were encountered: