Formatting of branches ahead/behind broken on narrow windows #5743

Closed
opened 2025-11-02 06:34:44 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @edgar-bonet on GitHub (Jul 15, 2020).

Description

The repository's branches overview page displays, next to each non-default branch, a couple of bars that graphically show how many commits each branch is ahead and behind the default branch. The display of these bars is broken if the browser's window is between 768 and 1199 pixels wide:

Branches overview page

Tested on Firefox. The behavior on Chrome is qualitatively the same, although I did not check the exact width thresholds.

For reference, GitHub displays those bars correctly for widths ≥ 1012 px, and removes them on narrower windows.

Originally created by @edgar-bonet on GitHub (Jul 15, 2020). - Gitea version (or commit ref): 1.12.2 and 1.13.0+dev-311-gbae5293d2 - Git version: 2.7.4 and 2.11.0 - Operating system: Ubuntu 16.04 and Debian 9 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: https://try.gitea.io/edgar/test-svg-mime/branches - [ ] No - [ ] Not relevant - Log gist: ## Description The repository's branches overview page displays, next to each non-default branch, a couple of bars that graphically show how many commits each branch is ahead and behind the default branch. The display of these bars is broken if the browser's window is between 768 and 1199 pixels wide: ![Branches overview page](https://user-images.githubusercontent.com/7680786/87534022-c83ba400-c695-11ea-986e-c305921aa827.png) Tested on Firefox. The behavior on Chrome is qualitatively the same, although I did not check the exact width thresholds. For reference, GitHub displays those bars correctly for widths ≥ 1012 px, and removes them on narrower windows.
GiteaMirror added the topic/uitype/bug labels 2025-11-02 06:34:44 -06:00
Author
Owner

@stale[bot] commented on GitHub (Sep 20, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 20, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@edgar-bonet commented on GitHub (Sep 20, 2020):

@stale: The issue is still valid: it affects both the latest release (1.12.4) and the development version at try.gitea.io (1.13.0+dev-656-g7f966f316).

@edgar-bonet commented on GitHub (Sep 20, 2020): @stale: The issue is still valid: it affects both the latest release (1.12.4) and the development version at try.gitea.io (1.13.0+dev-656-g7f966f316).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5743