[Presentation API] The presentation api doesn't work using Chrome on Android
Reported by
yue...@intel.com,
May 23 2016
|
|||
Issue descriptionSteps to reproduce the problem: 1. Connect the android device with second display or simulate secondary displays in Developer options. 2. Open the chrome on device and visit the url: https://honry.github.io/demo/tests/presentation.html What is the expected behavior? The start button is enabled and the Display availability is available. What went wrong? The start button is disabled and the Display availability is unavailable. Did this work before? N/A Chrome version: 50.0.2661.89 Channel: n/a OS Version: 5.1.0 Flash Version:
,
Jul 21 2016
,
Jul 22 2016
This is the intended behavior. The current Presentation API backend in Chrome for Android only supports Cast-specific URLs and commands so one should use the Cast Web SDK. There's an ongoing work on a more general solution (1-UA mode) for the API although I'm not sure when it's going to be supported on Android in particular. See issue 513859 . |
|||
►
Sign in to add a comment |
|||
Comment 1 by yue...@intel.com
, May 24 2016Connect the android device to the host and open chrome://inspect to debug. when type the >request <PresentationRequest {onconnectionavailable: null} >request.getAvailability().then(function ()<{console.log('ok');}).catch(function(e){console.log(e.name);}); the output is: Promise {[[PromiseStatus]]: "pending", [[PromiseValue]]: undefined} and no ok/error messaget print on the console. it seems like in the https://honry.github.io/demo/tests/presentation.html the following code: line 88 var presUrl = "display.html"; line 101 request = new PresentationRequest(presUrl); When use the display.html to construct the request, the display.html can't be found. We change to the display.html absolute path: var presUrl = "https://github.com/Honry/demo/tree/gh-pages/tests/display.html"; the output is the same. Then we put the presentation.html and display.html in the same folder on the android device and open the presentation.html with chrome and debug. the output is the same.