This repository was archived by the owner on Mar 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
[$40] Make toastr messages always visible #95
Labels
Milestone
Comments
MadOPcode
added a commit
to MadOPcode/micro-frontends-taas-admin-app
that referenced
this issue
Aug 14, 2021
…opcoder-archive#94, topcoder-archive#95. - Adds fixes for adding and editing payments (topcoder-archive#80, topcoder-archive#82) - Adds working period data reloading after adding and editing payments (topcoder-archive#94) - Makes toastr messages always stay withing the viewport (topcoder-archive#95)
Challenge https://www.topcoder.com/challenges/38b1552b-380b-4326-b222-7b0497b5858e has been created for this ticket. |
Challenge https://www.topcoder.com/challenges/38b1552b-380b-4326-b222-7b0497b5858e has been assigned to madopcode. |
Payment task has been updated: https://www.topcoder.com/challenges/38b1552b-380b-4326-b222-7b0497b5858e |
Verified on Prod Env. Working as expected. cc: @nkumar-topcoder |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Follow up issue from #82 (comment) issue 6:
When the page has a scrollbar and we make some operations at the bottom of the page we don't see the toastr which migh lea to confusion. For example when we perform some operations like editing payment or adding additional payment and it fails, the modal would stay open but we would not know that some issue happened.
To fix it we have to make sure that toastr is always visible even if scroll down.
The perfect solution if toastr message would be sticky see demo https://react-sticky.netlify.app/#/basic (this library seems to be maintained, but maybe there is a better one which is maintained https://www.npmjs.com/package/react-sticky-el)
When we on top of the page we show toastr at this place
When we scroll a bit, we are showing it at the same place.
But when we scroll down and the toastr if going to be hided, we make it fixed 20px from the top.
The text was updated successfully, but these errors were encountered: