Summary: 
Customer would like to configure native printers in Chrome OS and add a username followed by an @ sign before the IP address, so that every time a print job is sent, the user that sent the job to the queue can be identified. This used to work in Chrome 69. After Chrome 70, this stopped working and they can no longer save the settings when they add the username and the “@” sign, so this FR is being submitted to request the change to be reverted.

Previously, printers where configured following these steps:
1. Add the native printer from the settings with IP address only (According to customer, Chrome OS has never allowed to save the username and @ sign the first time they add the printer). 
2. Save the native printer, go back to the printer settings and edit the printer that was just added. 
3. Include the username before the @ sign and the IP address (e.g. “username@10.10.10.10”. 
4. Save the settings.

A video of how it used to work until version 69: https://drive.google.com/open?id=1Vk1AUZCrYw2DQcYt8Gq2eE79EVvYgM9_. Note that even though the username didn’t use to show after saving the settings and opening them again, the settings did work when sending print jobs to the queue. After Chrome 70, the settings can no longer be saved when editing the printer as the save button is grayed out.

Use case / Motivation: It is important to have the username reported when sending print jobs to the queue to identify who submitted the print job. This also helps users to more easily find the content that they print. Also, the username that needs to be reported is not necessarily the same username that is used to sign into Chrome OS.

Existing workarounds: None. It seems that policies support adding printer addresses with the desired format but it's not feasible for admin to import settings for each user.

Case#: 17619054