Last modified: 2014-02-12 23:46:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58359, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56359 - Special:UserLogin does not inform you you're already logged in on mobile
Special:UserLogin does not inform you you're already logged in on mobile
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
Feature requests (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Jared Zimmerman (WMF)
: design
: 56023 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-30 00:41 UTC by Steven Walling
Modified: 2014-02-12 23:46 UTC (History)
16 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Desktop screenshot (67.15 KB, image/png)
2013-10-30 00:41 UTC, Steven Walling
Details

Description Steven Walling 2013-10-30 00:41:19 UTC
Created attachment 13627 [details]
Desktop screenshot

On the desktop sight, if I visit Special:UserLogin (such as through a link in a help page), but I'm already logged in, I now get a helpful message telling me that I am already authenticated. [See screenshot attached]

On mobile, I am given the normal login form, and no indication that I don't need to log in again. It would be nice if you just displayed the same warning message that gets displayed on desktop.
Comment 1 Bingle 2013-10-30 00:42:16 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1342
Comment 2 Jon 2013-10-30 00:46:42 UTC
I would actually say the correct behaviour is to not show the page at all maybe redirecting to the main page...
Comment 3 Bartosz Dziewoński 2013-10-30 00:56:00 UTC
Just a note that the rationale for the desktop design when user is logged in was discussed on bug 53306 and change I1672ee09.
Comment 4 Steven Walling 2013-10-30 00:59:46 UTC
(In reply to comment #2)
> I would actually say the correct behaviour is to not show the page at all
> maybe
> redirecting to the main page...

That's a bad idea, because it defies normal expectations. A user clicking on a link to login or typing in Special:UserLogin expects to be sent to login. Doing something else silently would seem broken. 

Also, note that if you're already authenticated, you can in fact log in as a different account without logging out, so the warning message educates the user about this, rather than just acting as a roadblock.
Comment 5 Jon 2013-10-30 16:21:39 UTC
I was just pointing out that many websites if you go to the login page whilst logged in they will redirect you to a user dashboard. Since we don't have this equivalent though I can understand a warning message may suffice.

It doesn't seem like the end of the world to do nothing though - Tumblr seems to do that for example (www.tumblr.com/login)
Comment 6 Bartosz Dziewoński 2013-10-30 18:27:38 UTC
(In reply to comment #5)
> I was just pointing out that many websites if you go to the login page whilst
> logged in they will redirect you to a user dashboard. Since we don't have
> this equivalent though I can understand a warning message may suffice.

Unlike just about any site we allow users to register more than one account, though. And in particular we allow them to do that while being logged in. Showing the login form as well as the create account form seems like a sane thing to do (especially since it's also the only place in the UI where account creation is linked, apart from the list of all special pages).
Comment 7 Jon 2013-10-30 18:30:07 UTC
Sure but you can still only be in one account at a time. :) Maybe redirecting to a page that prompts the user saying "You are logged in as Jon, do you want to log in as another user" would make sense?
Comment 8 Jon 2013-12-09 22:06:50 UTC
*** Bug 56023 has been marked as a duplicate of this bug. ***
Comment 9 Jon 2013-12-20 00:05:00 UTC
Btw.. it actually /does/ inform you if you are logged in - an echo icon is in the top right corner.
Comment 10 Jon 2013-12-24 19:20:53 UTC
Andre / Quim - good task for Google Code in 2013. Should be put into the beta mode of the site first.
Comment 11 Quim Gil 2013-12-24 20:04:43 UTC
As long as the task is well defined, yes, this looks like a good GCI task.
Comment 12 Jon 2013-12-27 07:59:30 UTC
I think it's fine for it to replicate desktop as long as it is placed in the beta mode / alpha mode of the site first.
Comment 13 Quim Gil 2013-12-28 18:06:37 UTC
What I mean is that, after reading the discussion, it is unclear to me what is exactly the end result you want.

For instance, the subject says "Special:UserLogin does not inform you you're already logged in on mobile"but then you say in Comment 9 "Btw.. it actually /does/ inform you if you are logged in - an echo icon is in the top right corner."

Surely I m reading too fast, but this is confusing to me, and it might be confusing to a new contributor landing here for the first time.
Comment 14 Jon 2013-12-28 20:41:55 UTC
Apologies for the confusion. I'm basically suggesting we try what Steven originally suggested in comment 0 but limit it to the beta mode of the site. The Echo button does inform you but that's not it's real purpose and it might not be noticeable.
Comment 15 Quim Gil 2013-12-28 23:41:33 UTC
Understood. Thank you!
Comment 16 Theopolisme 2013-12-29 03:53:01 UTC
Is it necessary to limit this to the beta mode? It seems like just displaying something like http://i.imgur.com/MuL7w3I.png would be uncontroversial enough...Jon?
Comment 17 Jon 2013-12-29 06:48:17 UTC
It's not controversial it's just our standard practice to test things out in a beta mode first before pushing it to all our users.
Comment 18 Jon 2013-12-29 06:50:42 UTC
Screen looks great though.
Comment 19 Gerrit Notification Bot 2013-12-29 16:42:31 UTC
Change 104378 had a related patch set uploaded by M4tx:
Add "You're already logged in" information to Special:UserLogin

https://gerrit.wikimedia.org/r/104378
Comment 20 Gerrit Notification Bot 2013-12-29 16:56:00 UTC
Change 104382 had a related patch set uploaded by Theopolisme:
Show "already logged-in" notice at Special:UserLogin

https://gerrit.wikimedia.org/r/104382
Comment 21 Quim Gil 2013-12-29 17:55:02 UTC
Ok, so now you have two patches for review coming from a Google Code-in task that wasn't even claimed officially by anybody. I have deleted the GCI task, you can continue the technical review here and in the patches.
Comment 22 Jon 2013-12-30 02:25:37 UTC
Guys if you want to fix a bug in future please use the ASSIGNED status and mark yourself as the assignee. This will help everyone involved.
Comment 23 Theopolisme 2013-12-30 03:01:08 UTC
@Jon, I'm not able to modify the status setting...
Comment 24 Gerrit Notification Bot 2013-12-30 19:18:50 UTC
Change 104378 abandoned by Jdlrobson:
Add "You're already logged in" information to Special:UserLogin

Reason:
This lost the coin toss.
https://gerrit.wikimedia.org/r/#/c/104382/ got merged instead so this patch is no longer needed.

Thank you so much for the patch though. There was no problem whatsoever with this code.

https://gerrit.wikimedia.org/r/104378
Comment 25 Gerrit Notification Bot 2013-12-30 19:19:01 UTC
Change 104382 merged by jenkins-bot:
Show "already logged-in" notice at Special:UserLogin

https://gerrit.wikimedia.org/r/104382
Comment 26 Jon 2013-12-30 19:22:12 UTC
Even if you can't modify the status setting you should be able to declare "I am working on this." In future I can also update the ASSIGNED status if you say that you are working on this.

Due to the fact you both worked on this patch I just had the awkward situation of having to merge 1 of 2 near identical patches and in the end did it by a coin toss. Apologies to M4tx - I hope you understand this was nothing against your patch!
Comment 27 Jon 2013-12-30 19:23:43 UTC
Quick note: This is going to beta first. Jared and Steven/Kenan please comment back from a product and design point of view if you are happy for this change to go to stable and I will make this so.
Comment 28 Jared Zimmerman (WMF) 2013-12-30 19:35:12 UTC
based on the design I'm fine going straight to stable, but I'm also fine with it sitting in beta for a week. No strong preference to rush it through.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links