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

Issue 718668 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression
Team-Security-UX


Show other hotlists

Hotlists containing this issue:
EnamelAndFriendsFixIt


Sign in to add a comment

Origin in Android omnibox is not always moved to the correct alignment place after navigating back.

Project Member Reported by lgar...@chromium.org, May 5 2017

Issue description

Chrome Version: 58.0.3029.83
OS: Android

What steps will reproduce the problem?
(1) Search for "long subdomain badssl"
(2) Click on the result for https://long-extended-subdomain-name-containing-many-letters-and-dashes.badssl.com/
(3) Press the back button

What is the expected result?
The omnibox moves the origin so that either 1) all of it fits on the left of the omnibox, or 2) the right end of the origin aligns with the right of the omnibox. (Same as it was when you first loaded the page.)
https://www.chromium.org/Home/chromium-security/enamel#TOC-Eliding-Origin-Names-And-Hostnames

What happens instead?
The *left* of the long origin is reused for google.com, scrolled so that the "m" is just barely in view if the screen is too narrow to show anything.

I don't know if this is technically a regression, but marking as one for now.

tedchoc@, could you triage?
 
Screenshot_20170504-182714.png
359 KB View Download
Cc: tedc...@chromium.org mgiuca@chromium.org
Owner: jdonnelly@chromium.org
Related to  Issue 656417  (that is specific to RTL, and general to all platforms, so please don't dupe).

Whoever on the Omnibox team is fixing that CL will have to look at horizontal scrolling and can probably ensure this is fixed at the same time. +jdonnelly

Comment 2 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt
Status: Fixed (was: Assigned)
Appears fixed to me.  jdonnelly@, as the owner of this bug, can you verify?
I suspect this was fixed by the changes for these bugs:
https://bugs.chromium.org/p/chromium/issues/detail?id=705778
https://bugs.chromium.org/p/chromium/issues/detail?id=705780

This was the primary CL:
https://chromium-review.googlesource.com/c/chromium/src/+/677881

That rewrote omnibox scrolling for the TLD on Android, so it is likely the umbrella fix for all of these.

But yes...I do believe this should be fixed :-)

Sign in to add a comment