Obstructive notifications (snackbar)

btzr-io commented

2018-09-19 02:34:32 +02:00

(Migrated from github.com)

The Issue

Snackbar notifications obstruct some elements on the header component.
~~Also would be nice to have an option to remove it without having to wait.~~

Steps to Reproduce

Trigger a snackbar notification (click on the copy wallet address button)

Expected Behaviour

Non-obstructive notifications.

Screenshots

## The Issue Snackbar notifications obstruct some elements on the header component. ~Also would be nice to have an option to remove it without having to wait.~ ### Steps to Reproduce 1. Trigger a snackbar notification (click on the copy wallet address button) ### Expected Behaviour Non-obstructive notifications. ## Screenshots  ![snackbar](https://user-images.githubusercontent.com/14793624/45723967-45b52c80-bb71-11e8-95bc-d4aa709c9c73.png)

neb-b commented

2018-09-20 02:21:13 +02:00

(Migrated from github.com)

@btzr-io Do you have any ideas on how we can improve this? I think a good first step is to add an "X" to hide them earlier.

btzr-io commented

2018-09-20 03:52:30 +02:00

(Migrated from github.com)

@seanyesmunt some good suggestions:

Snackbars should be placed at the bottom of a UI, in front of app content. Avoid placing a snackbar in front of frequently used touch targets or navigation.

In wide layouts, snackbars can be left-aligned or center-aligned if they are consistently placed on the same spot at the bottom of the screen.

https://material.io/design/components/snackbars.html#placement

@seanyesmunt some good suggestions: > Snackbars should be placed at the bottom of a UI, in front of app content. Avoid placing a snackbar in front of frequently used touch targets or navigation. > In wide layouts, snackbars can be left-aligned or center-aligned if they are consistently placed on the same spot at the bottom of the screen. https://material.io/design/components/snackbars.html#placement

👍 1

sanketsingh24 commented

2018-10-05 19:51:35 +02:00

(Migrated from github.com)

If this issue is free, I would like to work on this, but would need some more info on where to place the snackbar, I think adding a close button would be necessary.

kauffj commented

2018-10-05 20:20:36 +02:00

(Migrated from github.com)

Material specifically does not have close buttons. Is there something unique about our app that requires them vs. Google which does not? Or do we think Google is wrong in not having them?

Unless we're answering in the affirmative to one of those questions, it is probably better to start with different/smarter placement and consider tweaking timing or usage if people feel a need to close.

Material specifically does not have close buttons. Is there something unique about our app that requires them vs. Google which does not? Or do we think Google is wrong in not having them? Unless we're answering in the affirmative to one of those questions, it is probably better to start with different/smarter placement and consider tweaking timing or usage if people feel a need to close.

sanketsingh24 commented

2018-10-05 21:02:45 +02:00

(Migrated from github.com)

Usually, snackbar is placed on bottom-right or bottom-left, the reason being the fact that people usually try to keep the relevent info nearer to top of the screen, and hence the bottom side of website is not used. Even the website which @btzr-io linked says that. Also, size and timing can be tweaked.

👍 1

neb-b commented

2018-10-05 21:05:46 +02:00

(Migrated from github.com)

I think if we move the snackbar to the bottom left, a close button would not be necessary. The only reason an argument could be made to have one now is because it covers the search bar.

👍 1

btzr-io commented

2018-10-05 21:10:36 +02:00

(Migrated from github.com)

Yeah, we don't need the close button if isn't obstructing important stuff 👍

Yeah, we don't need the close button if isn't obstructing important stuff :+1:

sanketsingh24 commented

2018-10-05 21:51:47 +02:00

(Migrated from github.com)

Bottom-left is cool but might hide some menu buttons, which is my only concern.

kauffj commented

2018-10-05 22:33:01 +02:00