Skip to content
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

UI is broken on multiple pages #1418

Closed
5 of 7 tasks
Morlinest opened this issue Mar 30, 2017 · 16 comments
Closed
5 of 7 tasks

UI is broken on multiple pages #1418

Morlinest opened this issue Mar 30, 2017 · 16 comments
Labels
topic/ui Change the appearance of the Gitea UI type/bug
Milestone

Comments

@Morlinest
Copy link
Member

Morlinest commented Mar 30, 2017

  • Gitea version (or commit ref): 1.1.0+79-g4fa691c4 (sha: 4fa691c)
  • Git version: Not relevant
  • Operating system: Not relevant
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: Not relevant

Description

Broken UI graphic, at least on pages:

  • repo -> settings -> branches
  • repo -> settings -> githooks

I think its caused by mergin PR #1389.

Another broken UI is on org ->settings -> webhooks (I think this was broken before).

Screenshots

repo -> settings -> branches:
chrome_2017-03-31_00-16-37

repo -> settings -> githooks:
chrome_2017-03-31_00-15-07

org ->settings -> webhooks:
chrome_2017-03-31_00-28-25

@andreynering andreynering added type/bug topic/ui Change the appearance of the Gitea UI labels Mar 30, 2017
@andreynering andreynering added this to the 1.2.0 milestone Mar 30, 2017
@Morlinest
Copy link
Member Author

Morlinest commented Apr 3, 2017

@andreynering and others.
What you like more?
Using classic semantic styles (description not in list):
chrome_2017-04-03_15-52-00
or using old custom (".hook") styles:
chrome_2017-04-03_15-52-22
or (also with ".hook" list style, but description is not as list option):
chrome_2017-04-03_16-44-55

Also are you OK with branches UI like this?
chrome_2017-04-03_16-01-06
chrome_2017-04-03_16-02-12

@sapk
Copy link
Member

sapk commented Apr 3, 2017

For the hook and branch page the .settings .list .item:not(:first-child) (introduce in my PR #1389.) just need to not be applied on hook to fix UI. I will look into it furthermore.

@sapk
Copy link
Member

sapk commented Apr 3, 2017

So .settings .list:not(.hook ) .item:not(:first-child) should be enough

@sapk
Copy link
Member

sapk commented Apr 3, 2017

But a long term solution that I will have to look into is to improve #1389 and continue to remove specific css like .settings .hook.list

@sapk
Copy link
Member

sapk commented Apr 3, 2017

Simply removing .table class from the parent of list : class="ui attached table segment" with removing specific .hook css code is enough to fix ui and remove also specific selector we could also remove hook class that is use also in branch html just to apply the same "hack".

@sapk
Copy link
Member

sapk commented Apr 3, 2017

For org ->settings -> webhooks it is possible that my PR also impact since I remove some .grid code from css. I will have a look at it and maybe migrate to new UI format ?

@Morlinest
Copy link
Member Author

OK, here is how it looks like (no .hook and .table + replace description from list to p tag before list):
webhooks:
chrome_2017-04-03_17-23-14

githooks:
chrome_2017-04-03_17-23-57

@Morlinest
Copy link
Member Author

Need to solve this:
chrome_2017-04-03_17-25-30

@Morlinest
Copy link
Member Author

What about removing "&:not(:first-child)" and just use "ui divided list" instead?

@Morlinest
Copy link
Member Author

Morlinest commented Apr 3, 2017

Like this (no extra classes, only semantic ui):
chrome_2017-04-03_17-49-51
chrome_2017-04-03_17-50-12
chrome_2017-04-03_17-50-23
chrome_2017-04-03_17-50-32
chrome_2017-04-03_18-11-30

@sapk
Copy link
Member

sapk commented Apr 3, 2017

It is missing a space and border are not connected to border like there were before. Why not keeping item list and not changing the first desc to p since &:not(:first-child) is there to keep not display border-top on first item ?
Just removing .hook and .table is enough (at least for hook and branch page)

@sapk
Copy link
Member

sapk commented Apr 3, 2017

.settings .list .item:not(:first-child) {
/*** */
min-height: 60px;
}
could also maybe removed to have a more compact list ...

@sapk
Copy link
Member

sapk commented Apr 3, 2017

+1 : .divided could be a solution to go further at cleaning custom css but we will need to keep fix to extend borders to borders or find a other solution in semantic

and use relaxed to add spacing in between horizontals borders.

@sapk
Copy link
Member

sapk commented Apr 3, 2017

For dropdown .list .item need to be more specific to .list>.item

@Morlinest
Copy link
Member Author

Morlinest commented Apr 4, 2017

I think it looks good with .relaxed .divided. No need for border to border extend, If you want that look, you can use attached segment or table instead of list. I like this look. Options tab has the same look. What do you think?

chrome_2017-04-04_11-49-34
chrome_2017-04-04_11-49-42
chrome_2017-04-04_11-49-51
chrome_2017-04-04_11-50-01

@sapk
Copy link
Member

sapk commented Apr 4, 2017

I haven't time to test but for having .divided border we could simply set and remove all extras custom ? .settings .list.divided>.item {
margin-right: -1rem; padding-right: 1rem;
margin-left: -1rem; padding-left: 1rem;
}
If you prefer you could also use .segment.table .list.divided.relaxed but it need a padding inside item to looks good.

And globally you should keep the desc as .item so that it have a border at his bottom. (i think)

Advice from long term maintainers could be good.

sapk added a commit to sapk-fork/gitea that referenced this issue Apr 6, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/ui Change the appearance of the Gitea UI type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants