Error messages aren't displayed if source is missing. |
|||||||||
Issue descriptionChrome Version: 69.0.3472.3 OS: Mac What steps will reproduce the problem? (1) enable views-browser-window and views-cast-dialog flags (2) Open Cast dialog and select a Cast device to cast to (3) Power down the cast device (4) Click the Cast button What is the expected result? This should generate an error msg shown to the user. The device they Cast to is no longer available. What happens instead? No error msg is displayed. And the tab mirroring indicator appears for ~ 20 sec,
,
Jul 17
This is apparently new in the Harmony UX, Takumi can you PTAL? This is a general test case for error conditions (not just the power-down scenario)
,
Jul 31
This is due to the current design where error msgs appear next to the device name. So when the device is removed from the list, there's no place for the error msg. I confirmed that Error messages do appear if the device is still discoverable. So WAI ATM? Amy, John, Do we want to support displaying error messages if the device they occurred on is no longer in the list? I wonder if there are any other cases, (casting to a hangout, etc.) where the sink is no longer listed, but a user would benefit from an error msg?
,
Jul 31
,
Jul 31
Brendan to follow up with Amy on the treatment of this case
,
Aug 2
,
Aug 2
,
Sep 12
One new observation is that although an error message is not displayed, the icon does turn orange with an exclamation mark. If or when the device is re-discovered, the Info msg "failed to cast" is displayed, until the device is clicked on, at which point it disappears. Is this expected? Chrome: 71.0.71.0.3549.0
,
Sep 12
IMO we should time out issues so they don't appear out of context. That would require some additional plumbing to add a timestamp to the IssueInfo object. This feels like a polish issue and users hit it < 3% of the time. Good to address but Pri3. Brendan/Amy, feel free to chime in.
,
Nov 15
Changing the title to more accurately describe the issue. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by dbbrooks@chromium.org
, Jun 26 2018