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

Issue 906836 link

Starred by 1 user

Issue metadata

Status: Fixed
Closed: Dec 21
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression

Sign in to add a comment

chrome://proximity-auth no longer displays software feature names

Project Member Reported by, Nov 19

Issue description

Numerical values are displayed instead of readable values; example:

Supported/Enabled Features {1: [enabled], 3: [enabled], 5: [enabled], 7: [enabled]}
It was a regression from, which removed the relevant #include.

Working on a fix now.
Summary: chrome://proximity-auth no longer displays software feature names (was: chrome://proximity-auth no longer display software feature names)
Project Member

Comment 3 by, Nov 20

The following revision refers to this bug:

commit 29ced3fcef80063c8d3feef7932ddd6ab08fbd5e
Author: Kyle Horimoto <>
Date: Tue Nov 20 00:05:06 2018

[CrOS MultiDevice] Fix broken chrome://proximity-auth page.

This CL fixes a regression which replaced feature names on this page
with numbers representing the features. The regression was caused by
erroneous removal of the #include containing the operator<<() function
which prints the enum names.

Bug:  906836 
Change-Id: Idb35e491ff379cc0ea97e63b57b4078a85efd0af
Reviewed-by: Ryan Hansberry <>
Reviewed-by: Bailey Berro <>
Commit-Queue: Kyle Horimoto <>
Cr-Commit-Position: refs/heads/master@{#609516}

Status: Fixed (was: Started)
Status: Started (was: Fixed)
Actually, I'll leave this open for now. I'll look at adding a test which ensures that this does not regress.
Status: Fixed (was: Started)
Fixed by, which defines chromeos::multidevice::SoftwareFeature with an operator<<().

Sign in to add a comment