-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Fix various trivial frontend problems #34263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
wxiaoguang
commented
Apr 23, 2025
•
edited
Loading
edited
- Fix Many images don't have an alt attribute #20606
- Fix Inconsistent emoji display (emoji font ordering issue) #34246
- Fix missing spaces, fix misspells, no visual change.
- Fix missing "not-mobile", fix Shrink down Buttons with Labels to Icons when in mobile mode #34265
d61a041
to
7454bb0
Compare
web_src/css/base.css
Outdated
@@ -2,7 +2,8 @@ | |||
/* fonts */ | |||
--fonts-proportional: -apple-system, "Segoe UI", system-ui, Roboto, "Helvetica Neue", Arial; | |||
--fonts-monospace: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace, var(--fonts-emoji); | |||
--fonts-emoji: "Apple Color Emoji", "Segoe UI Emoji", "Noto Color Emoji", "Twemoji Mozilla"; | |||
/* "Twemoji Mozilla" emoji font is widely used by browsers like Firefox, Pale Moon, and it is more likely up-to-dated than the system emoji font */ | |||
--fonts-emoji: "Twemoji Mozilla", "Apple Color Emoji", "Segoe UI Emoji", "Noto Color Emoji"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #34246 (comment). Maybe we should set --fonts-emoji
to a empty value, letting the browser choose the right font? Empty so that customization still works with the variable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or better yet, just remove --fonts-emoji
altogether. Users can still alter the other vars if they want to override emoji fonts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe like this: 0b04bfb. then the var is still kept and won't cause too many changes and the var could still be customized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose a dummy won't hurt but I see no real reason to retain the variable either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are 2 reasons in my mind:
- There are not only one references to
--fonts-emoji
, I don't want to introduce too many changes or do more tests. - Keeping the dummy name makes it easier to revert in the future (if anything wrong). We can fully remove the dummy name in future releases if it has been widely tested and there wouldn't be any problem.
Co-authored-by: silverwind <me@silverwind.io>
* giteaofficial/main: Fix panic when comment is nil (go-gitea#34257) Fix various trivial frontend problems (go-gitea#34263) update go&js dependencies (go-gitea#34262) Fix runner list tmpl (go-gitea#34270) Improve "not found" error messages for API (go-gitea#34267) Add fullscreen mode as a more efficient operation way to view projects (go-gitea#34081)