[Patternfly] Toast notification positions

Allie Jacobs ajacobs at redhat.com
Mon Jan 25 15:06:22 UTC 2016


One of the users I tested during customer convergence said he was concerned
about the toast covering up an important menu item in the top right. He
suggested having the notifications come down from the top middle. I agree
that would prevent the notifications from covering anything in OpenShift
but that's not true for everything. Also the menu items we have in the top
right are not primary items, which I believe is true for most of our
products.

Anyway - I agree with Leslie we should stick to what our recommendation is
for the design. If a developer wanted to put it top left and had a good
design reason, would they be able to? Or would we have to code in something
to allow that?

On Mon, Jan 25, 2016 at 9:15 AM, Leslie Hinson <lhinson at redhat.com> wrote:

> Per the page documentation [1], "The notifications should have a
> consistent location in each application. We recommend the top-right of the
> application."
>
> So when you say we should offer more positions, do you mean show actual
> examples of other locations? We purposely did not do this because we are
> making a recommendation to ensure consistency across apps that are using
> PatternFly. That said, we know the app come with there special set of use
> cases hence why we just recommend vs requiring.
>
> Thoughts?
> Leslie
>
> [1] https://www.patternfly.org/patterns/toast-notifications/
>
> On Mon, Jan 25, 2016 at 5:47 AM, Andres Galante <agalante at redhat.com>
> wrote:
>
>> At the moment we are offering the option to position the toast
>> notification at the top right corner by adding the class
>> ".toast-pf-top-right".
>>
>> This follows the patterns recommended position.
>>
>> I've notice today that Angular Material offers top, left, right or bottom
>> positions, so the developer can easily choose where to place the
>> notification: https://material.angularjs.org/latest/demo/toast
>>
>> I was wonder if it is a good idea to add more positioning options to our
>> implementation, or if we should stick to what we recommend.
>>
>> What do you think?
>>
>>
>>
>> _______________________________________________
>> Patternfly mailing list
>> Patternfly at redhat.com
>> https://www.redhat.com/mailman/listinfo/patternfly
>>
>>
>
> _______________________________________________
> Patternfly mailing list
> Patternfly at redhat.com
> https://www.redhat.com/mailman/listinfo/patternfly
>
>


-- 

Allie Jacobs
UXD

calendar
<https://www.google.com/calendar/b/1/embed?src=ajacobs@redhat.com&ctz=America/New_York>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/patternfly/attachments/20160125/895ce72e/attachment.htm>


More information about the PatternFly mailing list