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

Toast(modal) behavior is different from native toast #49

Closed
markzhai opened this issue Apr 22, 2016 · 2 comments
Closed

Toast(modal) behavior is different from native toast #49

markzhai opened this issue Apr 22, 2016 · 2 comments

Comments

@markzhai
Copy link

markzhai commented Apr 22, 2016

In Android native Toast, if one toast is still showing, and the second one comes, the first one will soon be replaced (may with a crash animation)

While in weex, the second toast (or you may call it modal) can appear only if the first completes its showing duration. This problem is more serious if we have a sequence of toast, which makes user have a wait a long long time to see all toasts.

@markzhai markzhai changed the title Toast behavior is different from native Toast(modal) behavior is different from native toast Apr 22, 2016
@luics luics assigned zshshr and unassigned YorkShen Apr 22, 2016
@zshshr
Copy link
Contributor

zshshr commented Apr 23, 2016

@markzhai thank you for your feedback, Android native toast can support these two behavior, And when you call Toast.makeText() to create a toast object every time ,it will be show one by one . otherwise it can be replace at once . I will think to change the behavior .

@zshshr
Copy link
Contributor

zshshr commented Jul 8, 2016

fixed ,please check the latest version @markzhai

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants