New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 664647 link

Starred by 144 users

[History page] Client UI for renaming a device in "Tabs from other devices" page

Project Member Reported by ew...@chromium.org, Nov 11 2016 
See Issue 455925 for more background. We'd like to provide a way for users to update the device name for foreign devices in the "Tabs from other devices" subpage.

Mocks are here: https://folio.googleplex.com/chrome-ux/mocks/405-rename-device#%2Fdesktop-01.png%3Fc=show

Comment 1 by ew...@chromium.org, Nov 11 2016

Components: Services>Sync
Labels: Hotlist-Polish

Comment 2 by s...@chromium.org, Nov 14 2016

Cc: s...@chromium.org

Comment 4 by s...@chromium.org, Nov 18 2016

Cc: pkotw...@chromium.org akalin@chromium.org rpop@chromium.org yfried...@chromium.org trond@chromium.org dubroy@chromium.org
 Issue 124964  has been merged into this issue.

Comment 5 by ew...@chromium.org, Dec 9 2016

Owner: pav...@chromium.org
Status: Assigned (was: Available)
Assigning to Pavel to make the sync engine changes before UI changes are made

Comment 6 Deleted

Comment 7 by amoylan@chromium.org, Dec 15 2016

Cc: amoylan@chromium.org

Comment 8 by 3vari...@gmail.com, Jan 3 2018 

any solution in preparation?

Comment 9 by pav...@chromium.org, Jan 17 2018

Labels: SyncHandoff2018
Owner: ----
Status: Available (was: Assigned)

Comment 10 by mastiz@chromium.org, Apr 9 2018

Cc: sabineb@chromium.org
Labels: -Type-Bug Type-Feature

Comment 11 by craigtumblison@chromium.org, Jun 4 2018

Labels: Hotlist-ConOps-CrOS
(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.

Comment 12 by treib@chromium.org, Sep 26

Labels: -Pri-2 Pri-3
This is the desktop equivalent of bug 455925. Just like that one, it's very low prio.

Comment 13 by anthony....@wwrsd.org, Oct 18 

Where are you guys with getting us an identifiable hostname for DHCP? In a 1:1 school district, this really needs to happen already. This was brought up 7 years ago and it seems you guys are sleeping on this...Right now, outside of going into admin console, there's literally no way for us to identify our Chrome devices (Chromebooks, Chromebits, etc...) You have it on Android devices so why is this still an open issue on the ChromeOS devices? This needs to be bumped up the pri.

Comment 14 by anthony....@wwrsd.org, Oct 18 

I posted this here because you closed comments on the related bug threads for this issue btw...
►

Sign in to add a comment