github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-10 16:44:50 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

WISH: Sticky issue titles #5028

New Issue
Open
opened 2025-11-02 06:11:46 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-02 06:11:46 -06:00
Owner
Copy Link

Originally created by @HenrikBengtsson on GitHub (Mar 8, 2020).

  • Git version: 1.11.2
  • Operating system: all
  • Database (use [x]):

Description

I'd like to propose an option for having issue titles be sticky when scrolling in the browser so that it is possible to always see what the title of the issue is regardless how far down you the comments you scroll. See below screenshots for behavior. This idea probably apply to other areas too, e.g. 'Pull requests'.

Screenshots

gitea_sticky_1
gitea_sticky_2

Proof-of-Concept Patch

I've implemented an ad-hoc patch myself that be in use for 3-4 months now. It is particularly useful in screen-share meetings where the moderator goes through issues and audience have no control of the interface. Using sticky issue titles avoid the question "What issue is this again?". The patch I apply for each Gitea update is:

--- view_title.tmpl 2020-03-08 14:07:39.647415337 -0700
+++ new_view_title.tmpl     2020-03-08 13:38:17.576454430 -0700
@@ -1,4 +1,4 @@
-<div class="sixteen wide column title">
+<div class="sixteen wide column title" style="position: -webkit-sticky; position: sticky; top: -10px; z-index: 10; background-color: white;">
        <div class="ui grid">
                <h1 class="twelve wide column">
                        <span class="index">#{{.Issue.Index}}</span> <span id="issue-title" class="has-emoji">{{.Issue.Title}}</span>
@@ -16,6 +16,8 @@
                        </div>
                {{end}}
        </div>
+</div>
+<div class="sixteen wide column title">
        {{if .HasMerged}}
                <div class="ui purple large label"><i class="octicon octicon-git-pull-request"></i> {{.i18n.Tr "repo.pulls.merged"}}</div>
        {{else if .Issue.IsClosed}}
Originally created by @HenrikBengtsson on GitHub (Mar 8, 2020). - Git version: 1.11.2 - Operating system: all - Database (use `[x]`): ## Description I'd like to propose an option for having issue titles be sticky when scrolling in the browser so that it is possible to always see what the title of the issue is regardless how far down you the comments you scroll. See below screenshots for behavior. This idea probably apply to other areas too, e.g. 'Pull requests'. ## Screenshots ![gitea_sticky_1](https://user-images.githubusercontent.com/1616850/76170988-44503900-6144-11ea-8e2f-b14935109633.png) ![gitea_sticky_2](https://user-images.githubusercontent.com/1616850/76170990-44503900-6144-11ea-9224-f7689554fb78.png) ## Proof-of-Concept Patch I've implemented an ad-hoc patch myself that be in use for 3-4 months now. It is particularly useful in screen-share meetings where the moderator goes through issues and audience have no control of the interface. Using sticky issue titles avoid the question "What issue is this again?". The patch I apply for each Gitea update is: ```diff --- view_title.tmpl 2020-03-08 14:07:39.647415337 -0700 +++ new_view_title.tmpl 2020-03-08 13:38:17.576454430 -0700 @@ -1,4 +1,4 @@ -<div class="sixteen wide column title"> +<div class="sixteen wide column title" style="position: -webkit-sticky; position: sticky; top: -10px; z-index: 10; background-color: white;"> <div class="ui grid"> <h1 class="twelve wide column"> <span class="index">#{{.Issue.Index}}</span> <span id="issue-title" class="has-emoji">{{.Issue.Title}}</span> @@ -16,6 +16,8 @@ </div> {{end}} </div> +</div> +<div class="sixteen wide column title"> {{if .HasMerged}} <div class="ui purple large label"><i class="octicon octicon-git-pull-request"></i> {{.i18n.Tr "repo.pulls.merged"}}</div> {{else if .Issue.IsClosed}} ```
GiteaMirror added the topic/uiissue/confirmed labels 2025-11-02 06:11:46 -06:00
GiteaMirror commented 2025-11-02 06:11:46 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (Mar 8, 2020):

Fixed: I posted a patch/diff toward the wrong code base so it looked much bigger - tI've updated the patch/diff - it's really a small update

@HenrikBengtsson commented on GitHub (Mar 8, 2020): Fixed: I posted a patch/diff toward the wrong code base so it looked much bigger - tI've updated the patch/diff - it's really a small update
GiteaMirror commented 2025-11-02 06:11:47 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (May 7, 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 (May 7, 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.
GiteaMirror commented 2025-11-02 06:11:47 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (May 8, 2020):

unstale[human]

@HenrikBengtsson commented on GitHub (May 8, 2020): unstale[human]
GiteaMirror commented 2025-11-02 06:11:47 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 8, 2020):

@HenrikBengtsson Could you send a PR to gitea?

@lunny commented on GitHub (May 8, 2020): @HenrikBengtsson Could you send a PR to gitea?
GiteaMirror commented 2025-11-02 06:11:47 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (May 8, 2020):

@lunny, would the diff in my top post suffice? I'm not familiar with the Gitea template framework, so it's a bit of a good-enough hack.

@HenrikBengtsson commented on GitHub (May 8, 2020): @lunny, would the diff in my top post suffice? I'm not familiar with the Gitea template framework, so it's a bit of a good-enough hack.
GiteaMirror commented 2025-11-02 06:11:47 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (May 8, 2020):

@HenrikBengtsson I think we would run into issues with the dark theme (e.g. white background style), as well we would want it to be optional and probably controlled by a class rather than inline styling if possible.

@jolheiser commented on GitHub (May 8, 2020): @HenrikBengtsson I think we would run into issues with the dark theme (e.g. white background style), as well we would want it to be optional and probably controlled by a class rather than inline styling if possible.
GiteaMirror commented 2025-11-02 06:11:48 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Aug 21, 2020):

I'd oppose this. It is one of the annoyances of GH that I don't like and which I disable with userstyles.

Issue title is not important enought not warrant taking away screen estate. It's duplicating with the browser tab title and easily visible when opening the issue, which ought to be enough.

@silverwind commented on GitHub (Aug 21, 2020): I'd oppose this. It is one of the annoyances of GH that I don't like and which I disable with userstyles. Issue title is not important enought not warrant taking away screen estate. It's duplicating with the browser tab title and easily visible when opening the issue, which ought to be enough.
GiteaMirror commented 2025-11-02 06:11:48 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (Aug 21, 2020):

I'd oppose this. ... Issue title is not important enought not warrant taking away screen estate.

Maybe it could be an optional feature?

So, the background for this feature request is to improve the Gitea experience during group meetings (in person or online) going through issues in the issue tracker. You have one person controlling the Gitea interface who share/project their screen. Since that person is in control, they also know exactly which issue they are currently on. In contrast, everyone else tends to get lost in which issue is currently discussed. This happens because the transition to the next issue is often too quick, or people tend to keep chatting with attention elsewhere when moving to the next issue. The issue title provides everyone with minimal, necessary info to catch up without having to ask the host to scroll back up to show the title and so on. We have used "stick issue titles" for 6+ months now and it helped us a lot.

@HenrikBengtsson commented on GitHub (Aug 21, 2020): > I'd oppose this. ... Issue title is not important enought not warrant taking away screen estate. Maybe it could be an optional feature? So, the background for this feature request is to improve the Gitea experience during group meetings (in person or online) going through issues in the issue tracker. You have one person controlling the Gitea interface who share/project their screen. Since that person is in control, they also know exactly which issue they are currently on. In contrast, everyone else tends to get lost in which issue is currently discussed. This happens because the transition to the next issue is often too quick, or people tend to keep chatting with attention elsewhere when moving to the next issue. The issue title provides everyone with minimal, necessary info to catch up without having to ask the host to scroll back up to show the title and so on. We have used "stick issue titles" for 6+ months now and it helped us a lot.
GiteaMirror commented 2025-11-02 06:11:48 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Aug 21, 2020):

Yeah sticky headers are certainly something to consider having a option for. Some people like them, some don't and they can be very distracting, especially on small screens.

I guess we need to introduce a "UI Options" section, can probably be localStorage-backed only.

@silverwind commented on GitHub (Aug 21, 2020): Yeah sticky headers are certainly something to consider having a option for. Some people like them, some don't and they can be very distracting, especially on small screens. I guess we need to introduce a "UI Options" section, can probably be localStorage-backed only.
GiteaMirror commented 2025-11-02 06:11:48 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (Aug 21, 2020):

Your and my "use case" made me realize that this type of feature then might belong to whoever is currently browsing Gitea, rather than the repos owner or Gitea admin. (I deploy my hack throughout Gitea at each update)

@HenrikBengtsson commented on GitHub (Aug 21, 2020): Your and my "use case" made me realize that this type of feature then might belong to whoever is currently browsing Gitea, rather than the repos owner or Gitea admin. (I deploy my hack throughout Gitea at each update)
GiteaMirror commented 2025-11-02 06:11:49 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Aug 21, 2020):

I'd make it a browser-specific option (e.g. localStorage does that). I guess you could sticky that header with a simple Userstyle too, so no need to touch server code.

@silverwind commented on GitHub (Aug 21, 2020): I'd make it a browser-specific option (e.g. localStorage does that). I guess you could sticky that header with a simple Userstyle too, so no need to touch server code.
GiteaMirror commented 2025-11-02 06:11:49 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (Aug 21, 2020):

Not really an option for us - too many people, computes, and browsers hosting - it's hard enough to get people to use issue trackers in the first place :p

@HenrikBengtsson commented on GitHub (Aug 21, 2020): Not really an option for us - too many people, computes, and browsers hosting - it's hard enough to get people to use issue trackers in the first place :p
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 issue/confirmed topic/ui
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#5028
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?