Can't cast tab to Hangout or Hangouts Meet from Pixelbook |
||
Issue descriptionGoogle Chrome 72.0.3626.49 (Official Build) dev (64-bit) Revision cb1307f71763cc1190fb8336022e245d0e1335b8-refs/branch-heads/3626@{#576} Platform 11316.66.0 (Official Build) dev-channel eve What steps will reproduce the problem? (1) Follow the instructions here to set up casting a tab to a Hangout / Hangouts Meet: https://support.google.com/chromecast/answer/6320939 https://support.google.com/chromecast/answer/3249268?p=no_cast_destination&visit_id=636832681290205539-107139043&rd=1 Specifically, sign in to the browser; enable Cloud Services in the Cast icon's right-button menu; see Calendar appointment containing Hangouts or Hangouts Meet appointment. (2) During the meeting, click the "Cast" icon to attempt to cast a tab. (The reason for doing this is to use the higher-bandwidth option for better frame rate.) What is the expected result? Expect either the Hangout to show up in the Cast destinations, or a text field to show up where the name of the Hangout can be typed. What happens instead? Cast reports "No devices found" and the Sources drop-down box is grayed out. This is key functionality that appears to be completely broken. Could someone please triage this for the next release? Thanks.
,
Jan 16
(6 days ago)
After not working multiple times - and "Report an issue" under the Cast icon having no effect - this suddenly started working. I closed the separate window that had the Slides presentation in it, opened a new tab in the main browser window containing the same presentation, and suddenly the Cast destination was present. It's now also present if I open the presentation in a new window. "Report an issue" also properly brings up the problem reporter page. Could this have been caused by the extension crashing or something similar? I've rebooted my machine multiple times today and the issue was still present after reboots. The machine just took the following update, on which things are working: Google Chrome 73.0.3669.0 (Official Build) dev (64-bit) Revision 5ca4eaf783225d46ce5f7837254f8bd96ee437b1-refs/branch-heads/3669@{#1} Platform 11578.0.0 (Official Build) dev-channel eve Downgrading to P2 because this isn't reproducible any more. No relevant crash IDs in about:crashes. This one seems to be related to the camera, but is old. Uploaded Crash Report ID 17fd275413c8871e (Local Context: Chrome) Crash report uploaded on Tuesday, January 15, 2019 at 8:37:49 AM
,
Jan 18
(4 days ago)
The "report an issue" option not working does make it sound like the component extension had crashed and wasn't working. Did you end up submitting the feedback form? I couldn't see one with your LDAP.
,
Yesterday
(35 hours ago)
Didn't send feedback. Once it started working there seemed little point. Is there anything I can provide that would help confirm whether it was the extension that crashed? Here are my most recent crash IDs from this device: Uploaded Crash Report ID 40f53e33b123cf2e (Local Context: Chrome) Crash report uploaded on Wednesday, January 16, 2019 at 4:52:48 PM Uploaded Crash Report ID 8514f894c9c6a520 (Local Context: Chrome) Crash report uploaded on Wednesday, January 16, 2019 at 4:17:29 PM Uploaded Crash Report ID 17fd275413c8871e (Local Context: Chrome) Crash report uploaded on Tuesday, January 15, 2019 at 8:37:49 AM |
||
►
Sign in to add a comment |
||
Comment 1 by taku...@chromium.org
, Jan 16 (6 days ago)Components: -Internals>Cast>Streaming Internals>Cast>Providers
Owner: jrw@chromium.org
Status: Assigned (was: Untriaged)