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

Unable to configure TapToDismiss on a Toast by Toast basis #178

Closed
benhaynie opened this issue Oct 1, 2018 · 2 comments · Fixed by #220
Closed

Unable to configure TapToDismiss on a Toast by Toast basis #178

benhaynie opened this issue Oct 1, 2018 · 2 comments · Fixed by #220
Assignees
Milestone

Comments

@benhaynie
Copy link

In my application, I want to be able to tapToDismiss some Toast messages, and not enable this property on other messages. For example, one Toast message may include a link for the user to click on. On these messages, I want to disable the tapToDismiss. On other Toast messages, I want to be able to tapToDismiss.

Prior to version 5, there was a ToastConfiguration property on the Toast object. This allowed us to set the tapToDismiss property on an individual Toast method.

This property has been removed.

Is there a recommended pattern to achieve this behavior? I understand that there is a Config object that can be used, but this seems to be a global setting, and not on a Toast by Toast basis.

@Stabzs
Copy link
Owner

Stabzs commented Nov 10, 2020

I apologize for inadvertently removing functionality, even if it wasn't exactly intended for that use case.

Let me look into expanding the toast api to allow for tapToDismiss functionality per toast.

@Stabzs Stabzs self-assigned this Nov 10, 2020
@Stabzs Stabzs added this to the 11.0.0 milestone Nov 19, 2020
@Stabzs
Copy link
Owner

Stabzs commented Dec 1, 2020

This has been closed in version 11.0.0

@Stabzs Stabzs closed this as completed Dec 1, 2020
@Stabzs Stabzs linked a pull request Dec 1, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants