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

Read-only participants can edit using keyboard shortucts #15

Open
dpp-gerrit opened this issue Feb 15, 2011 · 7 comments
Open

Read-only participants can edit using keyboard shortucts #15

dpp-gerrit opened this issue Feb 15, 2011 · 7 comments
Labels
Aspect: Consistency Issue with Saros' consistency handling

Comments

@dpp-gerrit
Copy link

Peers marked as read-only can use keyboard shortcuts to edit and cause inconsistencies. Examples include: Ctrl-D (Delete line), Ctrl-Up/Down,
Ctrl-Alt-Up/Down

Reported by: kbeecher

Original Ticket: dpp/bugs/460

@dpp-gerrit
Copy link
Author

  • status: open --> open-wont-fix

Original comment by: kargor

@dpp-gerrit
Copy link
Author

Even Eclipse has some limitations. Last but not least you can modify the file outside of the Eclipse IDE.

Original comment by: kargor

@dpp-gerrit
Copy link
Author

  • status: open-wont-fix --> pending-fixed

Original comment by: arndttigges

@dpp-gerrit
Copy link
Author

The result of the release test:
Basically it works. However, for pasting the result is not ideal. When
pasting the changes are only visible locally and the user does not get a
read-only warning but an inconsistency error. As no changes from the
write-restricted user are transfered, this behaviour is only inconvenient not critical.

Original comment by: cio

@dpp-gerrit
Copy link
Author

  • status: pending-fixed --> open

Original comment by: cio

@dpp-gerrit
Copy link
Author

dpp-gerrit commented Nov 6, 2014

I don't get it: What is "for pasting the result is not ideal" supposed to mean?
What exactly did you do as a read-only participant to circumvent the newly implemented "barrier" (see commit 2f555d).

Original comment by: fzieris

@dpp-gerrit
Copy link
Author

A description would be nice indeed. What still works are shortcuts like copy/cut/paste.

So the question is: does invoking those shortcuts also unlock the locked actions again ?

Original comment by: kargor

@dpp-gerrit dpp-gerrit added Aspect: Consistency Issue with Saros' consistency handling sourceforge labels Mar 27, 2018
@dpp-gerrit dpp-gerrit self-assigned this Mar 27, 2018
@dpp-gerrit dpp-gerrit removed their assignment Mar 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: Consistency Issue with Saros' consistency handling
Projects
None yet
Development

No branches or pull requests

2 participants