Enable CRD remote command for ARC++ Kiosk apps. |
|||
Issue descriptionCurrent implementation allows connection to non-ARC Kiosks only. Change implementation to allow connection to auto-started ARC++ Kiosks too.
,
Sep 18
,
Sep 18
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/95eae432c1a4f6c69b31e602e7df94468f8d4bf4 commit 95eae432c1a4f6c69b31e602e7df94468f8d4bf4 Author: Denis Kuznetsov <antrim@google.com> Date: Tue Sep 18 20:00:05 2018 Followup for Enable CRD for ARC Kiosks Bug: 885086 Change-Id: I1eb764626437c07008a0f44d4a7b0f47b05f931a Reviewed-on: https://chromium-review.googlesource.com/1232093 Reviewed-by: Sergey Poromov <poromov@chromium.org> Commit-Queue: Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#592164} [modify] https://crrev.com/95eae432c1a4f6c69b31e602e7df94468f8d4bf4/chrome/browser/chromeos/policy/remote_commands/crd_host_delegate.cc [modify] https://crrev.com/95eae432c1a4f6c69b31e602e7df94468f8d4bf4/chrome/browser/chromeos/policy/remote_commands/device_command_start_crd_session_job.h
,
Sep 25
Is the code for ARC++ in? Do I need to file a new launch bug for Kiosk CRD for ARC++ apps?
,
Sep 25
Code is in (see #3). Changes are small, but I believe that we should have separate launch bug (client-side only, as server-side does not distinguish between ARC/non-ARC kiosks)
,
Sep 27
Is there a reason this is blocking the Kiosk CRD for Chrome app? They're separate right?
,
Sep 28
verified on 09/20/2018 using DMS server |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Sep 18