Closed (duplicate)
Project:
Drupal core
Version:
8.4.x-dev
Component:
user.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Apr 2005 at 17:32 UTC
Updated:
11 Nov 2017 at 22:36 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
cosmicdreams commentedI agree with #1 but can't reproduce #2. I think we should alter our default themes to incorporate this change.
Comment #2
elv commentedIsn't this a duplicate of http://drupal.org/node/29060 ?
Comment #3
cosmicdreams commented#2 is a duplicate of that issue and has been fixed. But #1 is still happening. My default drupal beta-2 site doesn't put the cursor on the login textbox when I go to it.
Perhaps we should triage this to the Drupal project?
Comment #4
stevenpatzFeatures go in 7.x
Comment #5
cosmicdreams commentedThank you, I'll make note of that.
Comment #6
jody lynnSetting the cursor focus on the login page sounds like a decent idea to me.
Comment #7
Tor Arne Thune commentedStill a valid issue. I don't like having to tab or click every time I go to login and can imagine others feel the same way.
Comment #8
dead_arm#1174936: Allow FAPI usage of the autofocus attribute was won't fixed, so this would need to be added via #attributes.
Autofocus is HTML5 only, but that's not a problem for D8.
Comment #10
tim.plunkett#8: drupal-20446-8.patch queued for re-testing.
Comment #11
jody lynnI approve this patch to this 7yo usability issue. Thank you dead_arm for joining core office hours!
Comment #12
catchNice! Committed/pushed to 8.x.
Comment #13
ZenDoodles commentedDiscussion in IRC webchick said, "The biggest reason not to backport that is, I imagine it breaks XHTML validation." So we won't backport to D7.
Comment #16
mgiffordI was looking at autocomplete for #2096347: Add "autofocus" attribute to the module search and we're not being consistent about how we use autocomplete in Drupal 8 and we have no means to identify when it is appropriate to do so.
Right now it's used in most user forms, but not /user/register
Users should be able to predict when user forms will be presented. They need to have sufficient context such that screen reader users aren't confused by them.
Comment #17
mgiffordComment #18
mgiffordComment #20
aaronchristian commentedAnyone know the status of this task?
Comment #21
dawehnerWell it works for
/user/loginbut doesn't for/user/registerMoving to the right issue queue.
Comment #28
andrewmacpherson commentedtagging, just gathering issues which requested autofocus
Comment #29
andrewmacpherson commentedtCurrent status:
user/login - has autofocus, works
user/password - has autofocus, works
user/register - does not have autofocus.
We have #2861374: Inconsistent user interface with focusing fields to discuss this inconsistency, and it has more detail. So I'm closing his as a duplicate.
Comment #30
andrewmacpherson commented