Project

General

Profile

Bug #12383

Feature #5464: Revamp Greeter interface

Feature #11643: Greeter revamp: Phase 1.1

Use black shell theme in the greeter as we do in the session

Added by alant over 1 year ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
03/19/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
bugfix/12383-theme
Type of work:
User interface design
Blueprint:
Starter:
Affected tool:
Greeter

Description

The greeter shell theme should be black, as the session's one.

History

#1 Updated by alant over 1 year ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from alant to anonym
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/12383-theme

#2 Updated by intrigeri over 1 year ago

  • Assignee changed from anonym to sajolida
  • Type of work changed from Code to User interface design

I was reported by at least one user that the different theme helps understand when you're still in the Greeter session vs. when the regular GNOME session is/has started. So this proposed change seems to have UX implications ⇒ reassigning to sajolida.

#3 Updated by sajolida over 1 year ago

#4 Updated by sajolida over 1 year ago

#5 Updated by sajolida over 1 year ago

  • Status changed from In Progress to Rejected
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

I understand this argument and I'm fine with the current state of things :)

#6 Updated by alant over 1 year ago

  • Status changed from Rejected to Confirmed
  • Assignee set to sajolida

I was reported by at least one user that the different theme helps understand when you're still in the Greeter session vs. when the regular GNOME session is/has started.

The white shell theme was introduced in the greeter code by me, to match the GNOME Shell theme used in Tails. It's thus a mistake that it is now diffrent from the one used in the session.

I doubt that one single user report is enough to diverge from GNOME in terms of UX as well as in terms of code diff.

I'm up for more discussions/studies, but in the current state of things, I'd very much like we don't ship a "feature" that is actually a lack of polishing without better arguments that one user report an a feeling.

#7 Updated by intrigeri over 1 year ago

I'm up for more discussions/studies, but in the current state of things, I'd very much like we don't ship a "feature" that is actually a lack of polishing without better arguments that one user report an a feeling.

I did not mean to enter this debate, and still would rather not. All I did was provide a data point, and redirect to sajolida. So I won't argue about this topic further, even if I find your arguments pretty weak as well.

Meta²: the way I see it, UX feedback like "helps understand" is a bit different than "feelings". (And even if it were indeed mere feelings I reported, these things happen to be an integral part of the UX :)

#8 Updated by intrigeri over 1 year ago

  • Parent task changed from #8230 to #11643

#9 Updated by sajolida over 1 year ago

  • Assignee changed from sajolida to alant

I don't care enough to discuss this more. Alan, please do whatever you prefer and I'll be happy in both cases.

Also available in: Atom PDF