In Guest mode, Report an Issue option does not work for Cast icon.
Reported by
lpa...@etouch.net,
Jan 19 2017
|
|||||||
Issue descriptionChrome Version: 57.0.2986.0 (Official Build) 12c8d70173fc1a04fa588b75be71ab5e80655c60-refs/heads/master@{#444600} (32/64-bit) OS: Windows (7,8,10), Mac (10.11.6, 10.12.1), Linux (14.04 LTS) What steps will reproduce the problem? 1) Launch chrome, click on avatar icon and select 'Guest' option. 2) Right click anywhere and select 'Cast' (Cast overlay opens). 3) In action box, right click on cast icon, select ‘Report an Issue’ option and observe. On clicking Report an Issue option, Report an Issue page does not open. On clicking Report an Issue option, Report an Issue page should open. This is a Non-Regression issue seen from M-56 (Chrome version: 56.0.2916.0) Note: Cast icon was not seen in action box prior to above mentioned build.
,
Jan 19 2017
Is this specific to the Cast extension? It seems like it's a Cast problem then, not a UI>Browser>Profiles issue.
,
Jan 27 2017
Over to apacible@ for cast triage.
,
Jan 30 2017
M55: I'm seeing "<extension id> is blocked". M56+ Feedback does not open if the user is not signed in (incognito, non-guest but not signed in). Over to takumif@, who probably has more recent context.
,
Jan 30 2017
This seems like an issue with the extension resource loader. The component should be enabled in incognito. Any thoughts Devlin?
,
Feb 9 2017
Devlin, ping re comment #5.
,
Feb 10 2017
What incognito mode does cast use? [1] If it uses spanning, it's fundamentally impossible for us to show an extension resource in an incognito window. This is because the extension resource runs in the extension process, which would be non-incognito, and we can't have a non-incognito renderer in an incognito window. [1] https://developer.chrome.com/extensions/manifest/incognito
,
Feb 10 2017
(back to mfoltz)
,
Feb 10 2017
I don't think it's feasible to run the MR component in split mode for performance and other reasons; last time we tried this it caused crashes in downstream APIs. Fixing those issues is likely as much work as migrating to use the native MD feedback, which we plan to do later this year. In the meantime, we can hide the feedback menu item from incognito/guest profiles to not offer a dead-end. Over to Stephen to make a UX call (and file a separate issue to track any followup work). |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ranjitkan@chromium.org
, Jan 19 2017