New issue
Advanced search Search tips

Issue 665795 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature

Blocking:
issue 604105



Sign in to add a comment

bluetooth: android: align orign in chooser with omnibox

Project Member Reported by fbeaufort@chromium.org, Nov 16 2016

Issue description

I've noticed while playing too much with Web Bluetooth chooser these days that the origin wasn't aligned vertically and horizontally the same on Chooser and Omnibox.
Do you think we could try to match those to make it nicer on transition?

See video attached or you can try it yourself by picking "Swipe" at https://github.com/beaufortfrancois/sandbox/commit/01d5514523e04400684160ac0015f951c82611fd?diff=unified

This is pure polish.
If it's an easy fix for juncai@, let's do it.
 
web-bluetooth-chooser-alignment.webm
860 KB View Download
web-bluetooth-chooser-alignment.png
160 KB View Download

Comment 1 by juncai@chromium.org, Nov 16 2016

Cc: rolfe@chromium.org
hmm...If the origin string is aligned with the Omnibox, then it is not aligned with the strings on the chooser.

Also the origin string belongs to different UI item (Omnibox and chooser), not sure if it is necessary to make them aligned.

Comment 2 by rolfe@chromium.org, Nov 17 2016

I think fbeaufort@ meant bottom-aligning rather than left-aligning (so reducing top padding by 1 or 2dp and seeing if they line up better.) It's not necessary to make them aligned, correct, but it could be considered very small polish. I'm OK holding off/archiving if you don't feel strongly.

Comment 3 by juncai@chromium.org, Mar 20 2017

Cc: juncai@chromium.org
Owner: ----

Comment 4 by rolfe@chromium.org, Mar 29 2017

Cc: -rolfe@chromium.org
Removing myself as design contact. If you need visual support still you can reach out to hannahs@
Project Member

Comment 5 by sheriffbot@chromium.org, Apr 11 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
I think trying to keep these in sync doesn't make sense given that padding around text in the omnibox is likely to change as well without looking at all the dialogs that display an origin.

Sign in to add a comment