- From: Rottsches, Dominik <dominik.rottsches@intel.com>
- Date: Tue, 22 Jul 2014 15:49:09 +0000
- To: Francois Daoust <fd@w3.org>
- CC: "public-webscreens@w3.org" <public-webscreens@w3.org>
Hi Francois, > I see the Chromium build in the repo is 7 months old. Could it be that the build uses a version of Chromium that does not yet support Promises (added end of last year AFAICT)? > http://www.chromium.org/developers/calendar > http://www.chromestatus.com/features It is a bit old indeed. I’ll try to find the time to port the patches to a recent version and release newer builds. > The main difference I can think of between this code and the code of the video demo otherwise is that the "window.open" call occurs in an asynchronous callback as opposed to as a synchronous response to user input (which explains why the pop-up window will be blocked by default). > The messages logged to the console on the receiver side should look like: > [[ > code is running in a receiver app > dispatch "present" message > open slideshow at "https://[...]" > ]] I saw only the first two msgs. > I'll try to: > - improve the messages logged to help with debugging > - find time to setup a Linux environment > - add the required polyfills to support Promises or drop them altogether. > > Can you confirm it works correctly (with a pop-up window that is) with a regular Google Chrome on a Mac? On Release Chrome, unfortunately not, the window opens, and the title changes to HTML Slidy Receiver (so, it’s certainly loading something), but then it stays white. But I can debug it and look into what’s going on tomorrow for a while as well, no worries. >> Together with Anssi’s demo for video file playback, how about merging Intel’s OTC demos and yours under >> http://webscreens.github.io/demo/ ? > > That would make a lot of sense to me, yes :) > I'll get back to you once I have prepared a merged version of the demos. If you can take over merging them, that’s even better. Thanks! Dominik
Received on Tuesday, 22 July 2014 15:50:14 UTC