Add scroll-behavior: smooth to Markdown anchor links

[jussara-ti]

Feature Description

Currently, when clicking a documentation link that redirects to another section within the same Markdown file, the page jumps abruptly. We noticed that users in our environment reported feeling confused by this, as the sudden transition sometimes makes them think they were redirected to a different file rather than just navigating the same document. I tested applying the scroll-behavior: smooth CSS property via browser DevTools (F12) and it worked perfectly to provide a smooth visual transition, keeping the user's context intact and improving the UX. I searched the existing issues and couldn't find anything related to this enhancement. Implementing this would significantly enhance the reading flow and make navigating extensive documentation in Gitea much more intuitive.

Screenshots

No response

[Chigybillionz]

Please can I work on this

THANK you and please if there is a better way to apply to this issue, please let me know

[bircni]

Please can I work on this

THANK you and please if there is a better way to apply to this issue, please let me know

Feel free to

[Chigybillionz]

Sorry am asking too much questions But once I forked the repo and get the issue done and I reference the issue number, is that all the steps needed, then I will wait for the maintainer to check my PR and my Branch right, or is there a community I can join to trace the progress? Please am asking from a mind ready to move forward. THANK you

…

On Mon, Apr 27, 2026, 11:32 PM Nicolas ***@***.***> wrote: *bircni* left a comment (go-gitea/gitea#37454) <#37454 (comment)> Please can I work on this THANK you and please if there is a better way to apply to this issue, please let me know Feel free to — Reply to this email directly, view it on GitHub <#37454 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMBZJ5BFMK6TFPJUQ75AVY34X7NW7AVCNFSM6AAAAACYIA7EIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGMZQHEYDSNRXG4> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[silverwind]

First we need to decide whether we want smooth or instant scroll. Generally I prefer instant scroll. Test first if GitHub also smooth-scrolls on this, if not I'd be generally against it.

[jussara-ti]

I tested it on GitHub and you are right, they use instant scroll for Markdown anchors natively.

Knowing that, I completely understand keeping the default behavior as instant scroll to maintain consistency. However, would you be open to adding this just as an opt-in user preference?

This way, the default behavior remains exactly the same as it is today (and matches GitHub), but users who prefer a smoother reading experience in long documentation can simply enable it for themselves.

[silverwind]

Per-user settings like this are on the table, but we currently lack a clean framework to enable such per-user settings, that needs to be added first. Settings like this should be synced into the backend into the user table.

For this specifically, it should be named "Enable smooth scrolling" and apply to all cases of .scrollIntoView, .scrollTo, .scrollTop in the UI.

[jussara-ti]

@silverwind Thanks for the feedback! Makes perfect sense. Should we keep this issue on hold until the per-user settings framework is implemented?

@Chigybillionz As mentioned above, the scope just got bigger. It now requires backend work (Go + database) to build this settings framework, rather than just a simple CSS/JS fix. Are you still interested in taking on this larger task, or would you prefer to look for a simpler frontend issue?

[silverwind]

This framework is partially implemented already in backend IIRC, it just needs to be wired up against the user settings module in frontend to be able to persist certain options to the backend. Some options need backend persistence (this one) while others don't (all current ones in frontend).

As for this issue, https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/scroll-behavior seems to be the property you want to control. This seems to be the single mechanism that dictates all the various scroll APIs when scroll behavior is unspecified, so having it at :root should in theory control all scroll behaviours on the whole site.

[KalashThakare]

Would it be okay if I take this up? I’d like to give it a try.

[bircni]

Would it be okay if I take this up? I’d like to give it a try.

lets finish your other PR first but yes sure