Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 48195 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 18695 [details]
Webview opens youtube page with video.
On Android (tested using 5.0) open Chrome and navigate to https://www.youtube.com/user/JenzabarVideo, start the video, wait for the sound to start, then press the power button. The sound stops.
Run the app in the attached project which opens a ContentPage containing a Webview whose source is the same url. Wait for the sound to start, then press the power button. The sound continues to play.
Why does this behave differently in the webview in the App than it does in chrome?
This is not a Xamarin forms issue, but the normal Android behaviour. you can use Adrian's fix in a custom renderer.
This is causing Google to reject apps, as it violates the Device and Network Abuse policy, and is NOT normal android behavior because the same steps in Chrome on Android produce different results. This should at least be added as a configuration option so every app that is capable of playing video through a webview doesn't need a custom renderer.
I agree with Christine.
I don't see this problem in XF 184.108.40.206934. Can you re-run your tests and let the team know if this is still an issue?
I still experience this problem in XF 220.127.116.11934