github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Diff split view paints the whole line for both the new and the old version in a single color #188

New Issue
Closed
opened 2025-11-02 03:13:06 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 03:13:06 -06:00
Owner
Copy Link

Originally created by @alvaroaleman on GitHub (Jan 1, 2017).

Description

The split view mode always paints the whole line for both the new and the old version in a single color. This is especially irritating when a line was changed, because then it is completely red which makes it look like that line was removed.

IMHO the view should:

  • Display lines that were added white on the left side and green on the right side
  • Display lines that were modified red on the left and green on the right side
  • Display lines that were removed red on the left and white on the right side
Originally created by @alvaroaleman on GitHub (Jan 1, 2017). - Gitea version (or commit ref): 1.0.0 - Can you reproduce the bug at https://try.gitea.io: - [X] Yes: https://try.gitea.io/test/gitea/commit/d4924d45d6d4e991240d207a834d8d6709781449?style=split ## Description The split view mode always paints the whole line for both the new and the old version in a single color. This is especially irritating when a line was changed, because then it is completely red which makes it look like that line was removed. IMHO the view should: * Display lines that were added white on the left side and green on the right side * Display lines that were modified red on the left and green on the right side * Display lines that were removed red on the left and white on the right side
GiteaMirror added the topic/uitype/bug labels 2025-11-02 03:13:06 -06:00
GiteaMirror commented 2025-11-02 03:13:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 5, 2017):

resolved by #584

@lunny commented on GitHub (Jan 5, 2017): resolved by #584
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/ui type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#188
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?