Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug: Git diff view misaligns changed lines due to +/- icons taking horizontal space

Open Beginner friendly
#216 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
frontend

Research direction

No file or test is named; start by locating the git diff view implementation and inspecting how changed and unchanged lines render their +/- icons. Reproduce the issue with a file containing additions or deletions, then verify that content has consistent horizontal alignment for every line.

Written by the indexing model from the issue text.

Description

Hello,

I've discovered an indentation inconsistency in the git diff view where changed lines (prefixed with + or - icons) are shifted further to the right compared to unchanged lines.

The + / - change icons take up horizontal space, which pushes the actual line content farther right than lines without those icons. This creates a visually uneven indentation across the diff, making it harder to read and compare changes cleanly.

Steps to reproduce:

  1. Open a file in the editor that has uncommitted changes (i.e., a file with additions and/or deletions).
  2. Open the git diff view for that file.
  3. Observe the alignment of the lines - changed lines (showing + or - icons) will be indented further to the right than unchanged lines that don't display those icons.

Expected behavior:

All lines in the diff view should share consistent horizontal alignment, regardless of whether they're changed or unchanged. The + / - icons should not affect the indentation of the line content.

Thank you for your time!
Joshua Krimmer

Dominant language
Python
Stars
620
Forks
85
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-webui/computer

All issues in open-webui/computer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.