Either way, it does not sound like a Chrome issue.
It is either an issue with the tools you use (it perhaps makes Headless Chrome use a Safari user agent, you can verify that by going to whatsmyuseragent.com or something and taking a screenshot, I guess, or using your own server or Fiddler), or a Google Accounts issue where it does not identify the Headless Chrome user agent properly.

You can go to https://myaccount.google.com/device-activity, click on the appropriate entry that will show Safari instead of Chrome, click on the question mark icon at the top right, click on "Send feedback" and elaborate on the issue.

I think this can be closed.

Either way, it seems Chrome Support Team seems to disregard a crucial loophole through a vague dialog.

None of the tools used (Selenium, chromedriver, Java Binding) have anything to do with how Google Analytics identifies a browser. 

As you mentioned the url "whatsmyuseragent.com" now resolves to "http://www.whoishostingthis.com/tools/user-agent/" url which only shows the User Agent and other browser attributes but not the desired ones.

For your better analysis here is the snapshot from "http://www.useragentstring.com/" [Attachment - user_agent_info.png] & "https://www.whatismybrowser.com/developers/tools/user-agent-parser/?analyse-my-user-agent=yes" [Attachment - user_agent_info_again.png] clearly detects it as "Chrome 60".

Where as when I login to my Gmail account "Inbox" Google Analytics treats it as "Safari".

Finally you are asking me to "go to https://myaccount.google.com/device-activity, click on the appropriate entry that will show Safari instead of Chrome, click on the question mark icon at the top right" only to forget about it, which is completely unethical.

You can "Close" the issue right away but "Apple Inc" will be surely notified about the violation of the trademark "Safari" by Chromium.

Deleted: user_agent_info.png 63.0 KB

	user_agent_info.png 63.0 KB View Download

Deleted: user_agent_info_again.png 69.1 KB

	user_agent_info_again.png 69.1 KB View Download

1. The user agent of Chrome has always included Safari for web compatibility. It is not a trademark issue (and if it is, I am positive that the court would allow it as fair use, but I am not a lawyer or a judge ;)).

2. I think the issue is that the Google backend perhaps looks for " Chrome/" (a space character before the word "Chrome", or in regular expression, expects a word boundary, like in /\bChrome\/\d+/) and not just "Chrome/" in the user agent. Since "HeadlessChrome/" does not match the first pattern and only matches the second pattern, the Google backend would identify it as Safari (a fallback from failed the Chrome detection).

3. It is not a loophole and it is not so crucial. It is a misdetection (this tends to happen to many instances detection code every time a browser changes anything other than the version in its user agent string and this is no exception) and one that will probably be fixed at some point. The Google Accounts case is arguably more crucial, because it is security sensitive, but it does not really matter whether it says "Chrome" or "Safari" since it is Headless Chrome anyway and not a real user and the one that runs Headless Chrome can easily change the user agent to whatever they want.
Reporting this issue to Google Analytics and Google Accounts might make them act on it quicker, which is why I advised it.
I am not a Google employee or anything, so I cannot file an internal issue about that, which is why this is my suggestion. :)

(So now you can hopefully see that there is nothing unethical about my comment)

Attention: phistuck@gmail.com  kavvaru@chromium.org  nyerramilli@chromium.org

Either a regex issue or a fallback issue, I want Chromium to acknowledge it's a Defect/Bug/Issue in their services which violates "Safari" and "Apple" Trademarks,Copyrights,Privacy Policy by "The Chromium Projects" / "Chromium" / "Chromium OS".

You seem to be pretty confused about this issue. First you say "It is not a loophole and it is not so crucial. It is a misdetection" and very next you mention "be fixed at some point". Finally you finish up with "Google Accounts case is arguably more crucial, because it is security sensitive"

I understand as you are unable analyze and deep-dive to recognize the impact and Priority/Severity of this issue & you are forcing me to Close the issue as in "I think this can be closed." which is totally unethical and unjustified from a brand like "The Chromium Projects" / "Chromium" / "Chromium OS"

FYI, I will be notifying Apple Inc soon.

Thanks

#6 -

You are confusing things as well.
Chromium does not need to acknowledge anything, it is a Google backend issue. "Safari" will remain in the Chrome/Chromium/Vivaldi/Yandex Browser/Android browser user agent strings (trivia - Edge has "Safari" in its string as well. It also has "Chrome").

I am not confused about it. It is a bug, but not a critical one, so it probably should be fixed (by the Google backend, not by Chromium). It is security sensitive, but not a critical security issue.

Finally, I do not represent the Chromium project, I am just a user. :)

I encourage you to notify Apple. You will be wasting your time, of course, but you will at least have some peace of mind, which is important.

I will just end this with a small note - the user agent of Safari (and Chrome and Edge and Firefox) includes the words "Gecko" and "Mozilla".

As phistuck@ mentioned, the string being displayed comes from the website you're accessing, not from Chrome. That is, this represents a message the server sent - not a Chrome behaviour.

I'm marking this as WontFix.