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

Issue 869893 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Different behavior of hiding HTTP and HTTPS in the omnibox

Reported by jleedev@gmail.com, Aug 1

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3508.0 Safari/537.36

Steps to reproduce the problem:
1. Enable omnibox-ui-hide-steady-state-url-scheme-and-subdomains (or upcoming-ui-features)
2. On an HTTPS page, click twice in the omnibox to reveal the full URL, including the scheme
3. On an HTTP page, click twice in the omnibox

What is the expected behavior?
The scheme is hidden in the steady state and revealed when editing the URL.

What went wrong?
The HTTP scheme remains hidden at all times when editing a page URL.

Either behavior would really be fine — the HTTP behavior has existed for years without any churn — but now that both schemes are being hidden it feel jarring for the two behaviors to be different without any obvious reason.

Did this work before? N/A 

Chrome version: 70.0.3508.0  Channel: canary
OS Version: OS X 10.13.6
Flash Version: 

Example page: http://www.stealmylogin.com
 
Cc: jdonnelly@chromium.org
Components: -UI UI>Browser>Omnibox
Labels: Needs-Triage-M70
Cc: tommycli@chromium.org
Status: Untriaged (was: Unconfirmed)
CC tommycli@, who worked on this feature.

I think this is intended, as we can omit the "http://" for http URLs because the omnibox does http by default and it's always nice to remove unnecessary (redundant) junk.  So, there is a reason; it's just not that obvious of a reason.  That said, inconsistency in itself can be irritating.  Let's see what they say.
To add on to my previous reply:

We've always hidden the http:// in the omnibox; it's just that now that we distinguish between steady-state and editing-state, and we hide/unhide the HTTPS during that transition does it make it strange that we don't do the same thing for HTTP.
Cc: -tommycli@chromium.org groby@chromium.org
Owner: tommycli@chromium.org
Status: Assigned (was: Untriaged)
Agreed, this behavior is odd. Assigning to tommycli to figure out what to do. cc-ing groby.
Cc: emilyschechter@chromium.org
Status: WontFix (was: Assigned)
Hey -

It's working exactly as intended. We show the scheme for https:// in edit mode, and continue to omit it for http://.

In the future https-default world, we'd like to do the reverse.

Marking working-as-intended. +cc emilyschecter

Sign in to add a comment