8000 Option to step through changes in revision history · Issue #5694 · outline/outline · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Option to step through changes in revision history #5694

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

Open
tommoor opened this issue Aug 16, 2023 Discussed in #5693 · 9 comments
Open

Option to step through changes in revision history #5694

tommoor opened this issue Aug 16, 2023 Discussed in #5693 · 9 comments
Labels
enhancement It would be nice if… history

Comments

@tommoor
Copy link
Member
tommoor commented Aug 16, 2023

Discussed in #5693

Originally posted by thumDer August 16, 2023
It would be great to have a control on the revision views which allows the user to step through each and every changes that are part of the current revision. Currently the user has to go through the whole document and look for the highlighted parts, which is quite cumbersome on long documents. The way it is implemented in vs cvode is quite convinient:
kép

@tommoor tommoor added enhancement It would be nice if… history labels Aug 16, 2023
@includesec-erik
Copy link

This is a great idea thanks for suggesting it @thumDer!

It does feel like it's a bit of heavy lift for the UI to code this.

Suggestion (if doing this all in one go is too much work), break this into two parts:

  1. Adding the "list of changes as arrows" in the right nav so that one can see from the micro-nav bar on the right where the changes are and scroll until the change is in the view port of the text box
  2. Finish the feature with"up/down nav" and keeping a quantified total of number of changes "x of y changes" as the up/down buttons are clicked

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the stale label Jan 24, 2024
@tommoor tommoor removed the stale label Jan 24, 2024
@almereyda
Copy link

In GitHub and GitLab PRs, this is the review mode.

Might depend on

and more, or less, on

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the stale label Sep 22, 2024
@includesec-erik
Copy link

Still a good feature to add, but if you don't think it makes it on to the next year's roadmap perhaps you can throw it to a back burner queue @tommoor ?

8000

@tommoor tommoor removed the stale label Sep 22, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the stale label May 22, 2025
@includesec-erik
8000
Copy link

@hmacr what do you think, still remove stale flag? As a person who uses the diff UI often, I'd love to see this feature

@hmacr
Copy link
Collaborator
hmacr commented May 22, 2025

There was ongoing work in the recent past, we'll see if that can be taken forward.

@github-actions github-actions bot removed the stale label May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement It would be nice if… history
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0