-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Adjust class for mobile has the problem of double small bells #20236
Conversation
Co-authored-by: Gusted <williamzijl7@hotmail.com>
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.
What is your browser? |
tried with Chromium-backed QuteBrowser and Firefox Aurora and Firefox Dev (both > v10x). |
I can not reproduce it on try.gitea.io (this PR has been deployed there) Is it related to your theme? Or do you have more clues? |
@wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf double check that you have #20236 and not #20108 Please provide us with the sha of your head version and ensure that it is at least v1.18.0-dev-64-ga168609e8 |
I integrated both, the former only caused the double bell in mobile view, the latter (chronologically) causes the bell to be shifted upwards for me. |
I suspect you've not quite integrated correctly. Check your version of this line: gitea/templates/base/head_navbar.tmpl Line 117 in 8ee8230
In #20108 this was: gitea/templates/base/head_navbar.tmpl Line 117 in c174bdc
And before that it was: gitea/templates/base/head_navbar.tmpl Line 103 in 2921d3c
it might be that it needs the |
thanks for all the effort. line 117 in my the previous version worked fine for me (except the double bells), the one with
I may try with item and I bet it will be fine again. however, how could fonts make an svg shift its position? I thought the bell is just "paths", there is no text to render using any font, is there? |
indeed, adding if it doesn't do any harm (and it's for non-mobile anyway), wouldn't it be more {fool,future}proof to just keep the |
yeah I suspect we should be putting the item back in. Looking at it again when changing the |
yay, so it's not just me? :D why isn't it manifested on try, though? caches again? |
it's not as obvious on different fonts. |
I am using FiraCode in all browsers (rejecting remote fonts) and I even have a patch preprending FiraCode to the list of Gitea fonts (something.less) at build time (as that list is hardcoded).
btw I am no expert in the web stuff used in Gitea, but in my experience, adding anything else apart from |
so is it with just i.e., which one is it:
EDIT: a) and b) both work for me (mentioned a couple of comments earlier), but I don't know which one is the preffered one.. |
the change I was making was simply switching the m-4 for item I'm not certain that "text black" will be needed if "item" is set. |
so that is essentially a revert to where we've been before this change. |
ah crap the original problem is the display property on the item class. |
OK it looks like the |
The use of `m-4 text black` for the notification bell results in this icon being shifted upwards. Instead we should use the `item` class but adjust `not-mobile` and `mobile-only` to make their `display: none` settings `!important`. (As an aside: This is probably one of the only times we should use `!important` in our less files and the rest should be avoided or removed.) Ref go-gitea#20069 Revert go-gitea#20236 Signed-off-by: Andrew Thornton <art27@cantab.net>
The use of `m-4 text black` for the notification bell results in this icon being shifted upwards. Instead we should use the `item` class but adjust `not-mobile` and `mobile-only` to make their `display: none` settings `!important`. (As an aside: This is probably one of the only times we should use `!important` in our less files and the rest should be avoided or removed.) Ref #20069 Revert #20236 Signed-off-by: Andrew Thornton <art27@cantab.net>
…itea#20236, go-gitea#20251) Backport go-gitea#20108 Backport go-gitea#20236 Backport go-gitea#20251 Make notification bell more prominent on mobile Co-authored-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Tyrone Yeh <siryeh@gmail.com> Signed-off-by: Andrew Thornton <art27@cantab.net>
* upstream/main: Modify milestone search keywords to be case insensitive (go-gitea#20266) Fix toolip on mobile notification bell (go-gitea#20270) Allow RSA 2047 bit keys (go-gitea#20272) Refix notification bell placement (go-gitea#20251) Bump mermaid from 9.1.1 to 9.1.2 (go-gitea#20256) EscapeFilter the group dn membership (go-gitea#20200) Only show Followers that current user can access (go-gitea#20220) Init popup for new code comment (go-gitea#20234) Bypass Firefox (iOS) bug (go-gitea#20244) Adjust max-widths for the repository file table (go-gitea#20243) Display full name (go-gitea#20171) Adjust class for mobile has the problem of double small bells (go-gitea#20236) Adjust template for go-gitea#20069 smallbell (go-gitea#20108) Add integration tests for the Gitea migration form (go-gitea#20121) Allow dev i18n to be more concurrent (go-gitea#20159) Allow enable LDAP source and disable user sync via CLI (go-gitea#20206)
…ea#20236) * Adjust class for mobile has the problem of double small bells * Update templates/base/head_navbar.tmpl Co-authored-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: Gusted <williamzijl7@hotmail.com>
The use of `m-4 text black` for the notification bell results in this icon being shifted upwards. Instead we should use the `item` class but adjust `not-mobile` and `mobile-only` to make their `display: none` settings `!important`. (As an aside: This is probably one of the only times we should use `!important` in our less files and the rest should be avoided or removed.) Ref go-gitea#20069 Revert go-gitea#20236 Signed-off-by: Andrew Thornton <art27@cantab.net>
…ea#20236) * Adjust class for mobile has the problem of double small bells * Update templates/base/head_navbar.tmpl Co-authored-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: Gusted <williamzijl7@hotmail.com>
The use of `m-4 text black` for the notification bell results in this icon being shifted upwards. Instead we should use the `item` class but adjust `not-mobile` and `mobile-only` to make their `display: none` settings `!important`. (As an aside: This is probably one of the only times we should use `!important` in our less files and the rest should be avoided or removed.) Ref go-gitea#20069 Revert go-gitea#20236 Signed-off-by: Andrew Thornton <art27@cantab.net>
Sorry, I didn't notice that the item class has a display property, and I will see two small bells on the phone
for #20069 improve
Before:
After: