-
-
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
Responsive view #2750
Responsive view #2750
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2750 +/- ##
==========================================
- Coverage 34.89% 34.73% -0.16%
==========================================
Files 277 277
Lines 40177 40177
==========================================
- Hits 14019 13955 -64
- Misses 24099 24178 +79
+ Partials 2059 2044 -15
Continue to review full report at Codecov.
|
Need some help here: at the moment forms are organised to be like this: This does not really cope well with mobile devices, because this is what you get: Would it be OK to replace these custom forms with Semantic UI's stock forms, having the label of the field sitting on top of the field instead of on the side? |
I use 2FA when logging into Gitea, any plans to support that in the initial responsive version? |
That should be included in the task of getting forms to look good (which is what I need to do for the login anyway). In any case, 100% of Gitea's functionality after this PR will be on mobile, too: the only difference is that some pages will look weird for the moment (and to not make this PR even bigger) |
I don't mind QA-ing if that will help you along. I greatly appreciate the work done so far! |
In mobile version input buttons must be full width and labels aligned to left |
I will also test the changes too. |
Great job so far. Some things to work on:
|
Hey there! Thanks for your feedback.
Also, I've pretty much implemented everything I previously said I would do in the first post and went ahead and removed the [WIP] tag. Reviews and further feedback welcome! |
@thehowl CI failed. |
By hard to use, I mean it sometimes disappears too soon (but I don't think you can do something about this issue). |
Seems like last time the pgsql test randomly failed. Merged master and it works now ¯\_(ツ)_/¯ @lunny ready for review. |
Please rebase |
done |
There are some conflicts with master. |
Ready for review... again |
@lunny addressed your issues and rebased ✅ sorry for taking long |
@thehowl Good job!!! Maybe this PR could be merged before v1.4 released. But some issues below: |
@lunny done & rebased |
@thehowl need rebase |
Sorry for the delay. Can we still get this in by 1.4.0 (in which case I'll proceed to the rebasing now) or since we're in the feature freeze already will this have to wait til 1.5? |
@thehowl I would like this is in v1.4. Feature freeze means new feature coming PR will be in v1.5, not mean the PR which has been marked as v1.4. |
The class was necessary, because this way the dropdown doesn't assume the contents of the selected item.
minor improvements - make login/sign up in navbar stackable - make navbar in explore and sign in not stackable Change selected class in TestPullCompare Fix typo that happened when rebasing fix dashboard on org view improve profile UI Use clearing on file diff to fix broken UI caused by floating elements remove unresolved merge conflict, and | Sanitize Fix repo home not loading
And the tests are green ☑️ If anyone reviews the code, make sure to append |
LGTM |
Other pages will come in future PRs. This PR closes #35.
Screenshots
New navbar
Example of collapsed navbar (and dashboard)
Collapsing/expanding demo
Issues page (I ask you to disregard the issue titles I use for testing 😉)
Explore