-
Notifications
You must be signed in to change notification settings - Fork 275
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 flashes on screen tap with Samsung Galaxy S6 and S7 Edge #95
Comments
Can you debug it or at least record a video of what's going on? I've tried many emulators and devices, even a new Nexus 6P with Android 7, but it's all just fine with your code sample. |
Yup, no issues on any of my other phones except for these recent Samsung devices. YouTube link showing the problem: https://www.youtube.com/watch?v=lgI-oBSnK14 And a rather long logcat of what happens as the toast is flashing:
|
@ds8k Really appreciate your attempt to clarify this for me but I'm not sure this is entirely clear. However, before continuing.. can you remove the include of the css file so it's all blank and ugly - and see if the same problem occurs? |
Same behavior with the CSS include removed. If I trigger the toast and don't touch the screen it displays and goes away after the specified time. If I trigger it, then tap the screen, it begins to flash. Let me know if I can provide any other information. |
That's clear. I need someone with a similar device to test this as I don't have one and none of my devices have this issue. |
I can confirm this issue on Samsung Galaxy S5 - Android 5.1.1, the same behaviour as declared above. |
any update on this issue, I am also facing this issue on samsung s6 and s7 |
This issue is also present on the S9 |
Expected behaviour
Toast displays until provided time elapses
Actual behaviour
If I tap the screen the toast begins to flash in and out until the time elapses
I'm seeing this behaviour on
Hardware models
Samsung Galaxy S6
Samsung Galaxy S7 Edge
OS versions
Android 5.1.1, 6.0.1
I'm not a dummy, so I've checked these
deviceready
to fire.window.onerror
catches nothing).So how can we reproduce this?
I'm running the following code in the Chrome console and experiencing this:
I've created a fresh Cordova application with the following steps:
and can confirm the same behavior occurs here.
The text was updated successfully, but these errors were encountered: