-
Notifications
You must be signed in to change notification settings - Fork 7
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
Flexibus/#381/team page design #465
Conversation
I'm changing the name of PR #379 to clear that up a bit at least because this has confused me before as well... |
@deeps96 Oh I am sorry! I misunderstood the scope of this issue/PR. I actually checked out the correct branch, but was focusing on the wrong pages. We use a different naming, e.g. teams index page, teams show page, teams edit page, ... |
Response 1The colon is missing because of uniformity and cleaner design. @zhamanakov are you ok with that? ANSWER: pls just hide the whole section, if there are no sports selected. DONE!
Response 1What do you mean exactly? Response by @bakoeSorry—I have posted the wrong screenshot for the problem I described. However, the issue is rather unimportant: When there is a very long (and thus multi-line) text in the kinds of sport (“Sportarten”) section, the text has very little space (CSS:
Response 1@zhamanakov Is this important? If yes, how much margin do you want? ANSWER: min 20px margin between buttons is important DONE
Response 1Will fix DONE
Response 1Will fix that. But just for interest: When is this the case? Response by @bakoeThanks! This situation is the case whenever you look at the team page of a (public) team you are not a member of. DONE
Response 1Will fix DONE |
@deeps96 Is the design of the “Invite users by e-mail” in the scope of this issue as well? |
The hover font color of the “Leave team” button has almost no contrast to the background – maybe use something lighter than black? However, white is already “reserved” for the non-hovered button text. Maybe a light blue or something like that for the hover state would be better? cc @zhamanakov ANSWER: light blue for hover will be ok! DONE |
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 just skimmed the code changes since they contain a lot of HTML/CSS stuff for which – to my mind – always many “correct” solutions exist. What I looked into seemed very good. 👍
More intensively, I tested how the re-designed page looks and behaves on Chrome and Safari on macOS. Fortunately, I couldn't find any big bugs and only noticed some minor flaws as documented in the PR's comments section.
@bakoe to your q whether the email invitiation modal is part of the intended redesign: #381 does not seem to specify that explicitly, even though i'd personally find it bizarre to have this clearly unfinished element on the otherwise so nearly designed page. Response 1You are right - it was out of scrope for this story. Maybe it will get an own user story during the Kanban-week? @zhamanakov ANSWER: It is ok. @deeps96 even if the invitation part is out of scope for this issue, look at what happens to the top of the page after inviting a user to the team ANSWER: notification re-design is already in progress in #501 |
@tomkellog #501 addresses the second issue described by you, it's out of scope for this ticket. |
could there be anything done about the persistent, rectangular highlighting of buttons after clicking on them? Response 1I think the easiest approach would be, to remove the blue border of this selection completly. @zhamanakov are you ok with that? ANSWER: yes, just remove the blue border is ok. DONE |
app/assets/stylesheets/teams.css
Outdated
content: "*"; | ||
vertical-align: 0.5em; | ||
font-size: 0.75em; | ||
font-weight: normal; |
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.
the css you removed here affected the edit
team page, adding an asterisk after required fields, as specified in #218.
please add again!
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.
Will fix
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.
Done.
I wrote some answers into the comments. Waiting for @zhamanakov to reply - will fix everything in one go afterwards. |
…pi-swt2/sport-portal into flexibus/#381/team-page-design
@tomkellog @bakoe @zhamanakov I fixed all things mentioned. Please recheck! |
app/assets/stylesheets/teams.css
Outdated
} | ||
|
||
.genericButton, .genericButton:hover, .genericButton:focus { | ||
outline: none !important; |
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.
To my mind, removing the :focus
-outline property without adding another visual indication for focused elements is quite an anti-pattern since it reduces the accessibility of the website significantly. See http://www.outlinenone.com for further explanation.
Currently, the “Select all”, “Select none”, “Edit” and “Delete” buttons have a :focus
state that looks exactly the same as the non-:focus
state. You can inspect this e. g. by Tab-navigating (using the Tab key on you keyboard) over the Team page or by using the Chrome Developer Tools' “Force element state” panel in the Elements tab:
@deeps96 Please make the :focus
states of the buttons used on the Team page distinguishable from the normal inactive state. A simple fast solution would be to extend the existing :hover
property changes you introduced to changing not only the :hover
state, but also the :focus
states (e. g. by lightening up the buttons' background colors).
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.
@deeps96 Thanks for fixing the issues I mentioned! I took another look and can confirm that all the issues are fixed now.
However, I have a minor complaint about the :focus
states of some buttons being indistinguishable from the non-focused standard state (see my comment above). Maybe you can talk back to you SM/PO about the importance of accessibility on the page and decide whether you're going to fix this or not.
Response 1
@zhamanakov Whats your opinion?
I would be happy to merge this, as soon as @tomkellog approves that the requested changes from his review has been implemeneted.
I think @zhamanakov needs to decide on the |
@jak-ing @deeps96 @zhamanakov Have you thought about the issue I mentioned in the user story?
Response 1Still waiting for @zhamanakov response. |
…pi-swt2/sport-portal into flexibus/#381/team-page-design
…lexibus/#381/team-page-design # Conflicts: # app/assets/stylesheets/teams.css # app/views/teams/show.html.erb
Closes #381, also fixes #396.
Make sure to checkout flexibus/#381/team-page-design when reviewing since there exists a branch with a similar name.