For the sake of determining whether we can physically fit these warnings, here are screenshots of the implementation.

Deleted: not-secure.png 7.0 KB

	not-secure.png 7.0 KB View Download

CC'ing UX and enamel to weigh in on security chip text in VR.  Screenshots are attached.

Note that as is, enabling this would result in us bailing from VR, because we can no longer fit the origin in the remaining space.

Would it be better to simply bail from VR if we encounter a dangerous page?

Also, the choices made need to cover WebVR presentation mode as well, where an even more simple, transient URL indicator appears.

The CL for this support has landed.  Keeping the bug open while we sort out whether to enable the feature or not.

https://codereview.chromium.org/2946523002/

(not sure why the CL didn't generate a comment on this bug when it landed)

A discussion today with enamel concluded that the security chip is not launch-blocking for M-61.  However, there's agreement that the text itself is useful.

Given that we're in a new UI space, Emily suggested that the security text might be presentable in another way (ie. not in-line with the URL).

Assigning to Josh, to coordinate how we might best show this information.

Assigning to Gordon for UX input (welcome to @chromium, Gordon! :)

Gordon, can you confirm that your current Omnibox design work includes addressing this question?

Yup. Been in conversations with Enamel. Working on a recommendation.

Met with cjgrant on this and worked through edge cases together. Back to cjgrant.

Hey Gordon, I think there was a mix-up on that re-assign.  This particular bug is tracking what we should do about "secure" or "dangerous" text next to the security icon.  Nothing to do with https:// scheme, elision, etc.

Takeaway from discussion with Gordon:

"We don't want to implement the text-style security chip from Desktop. We want to implement a Clank-style icon-based security chip."

Ie. keep doing what we're already doing.