Repository navigation
Auth: Fixed remember-device label wrapping - #179
Merged
whereareiam merged 2 commits intoNov 1, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Allow the sign-in remember-device label to use the available field width instead of inheriting Forgejo’s 200 px desktop label width. This prevents premature wrapping for wider translations while retaining natural wrapping for longer text and narrow screens. The change is scoped to the remember-device row.
Closes #178. Scope discussion with maintainers is pending.
Before and after
Russian locale, 1440 × 900 viewport, DejaVu Sans. These captures use the live sign-in page with the label width toggled between the 200 px baseline and the proposed fix; they are not from the project’s dev preview.
Verification
bun run commit: formatting, build, type check and Vitest passed (581 tests).bun run lintfails on both the unchanged base and this branch because the installed typescript-eslint does not yet support TypeScript 7; the existing CI workflow also skips ESLint for that reason.Release notes
Area: Descriptionformat and describes the user-visible fix.buglabel.