11699 2011-01-08 16:20:12 +0000 When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define 2011-08-04 05:34:12 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other CLOSED FIXED https://bugzilla.mozilla.org/show_bug.cgi?id=408595 http://www.whatwg.org/specs/web-apps/current-work/#focus-management Disagree P3 normal --- 1 contributor ian ayg ian mike mounir Ms2ger public-html-admin public-html-wg-issue-tracking shadow2531 public-html-bugzilla oldest_to_newest 43942 0 contributor 2011-01-08 16:20:12 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html Section: http://www.whatwg.org/specs/web-apps/current-work/#focus-management Comment: When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define Posted from: 91.181.240.75 by ms2ger@gmail.com 44663 1 mounir 2011-01-24 16:10:04 +0000 I wonder if we couldn't let .focus() behavior be the one used by the system and require authors to use .setSelectionRange() if they need to cursor to be at a specific position? 44782 2 ayg 2011-01-27 00:10:51 +0000 What's "the one used by the system" supposed to be? Normally you'd focus things by clicking on them, which would place the cursor where you click. So you mean what you'd get by alt-tabbing to it? Do platforms actually differ on where the cursor goes then? (Linux seems to select the contents.) 44805 3 mounir 2011-01-27 15:30:10 +0000 (In reply to comment #2) > So > you mean what you'd get by alt-tabbing to it? Do platforms actually differ on > where the cursor goes then? (Linux seems to select the contents.) For example, yes. But the idea is it doesn't seem to be very useful to specify that given that an API is available to set the cursor wherever the author wants. 44808 4 ayg 2011-01-27 19:08:44 +0000 I don't get what you're saying. Surely it's always good to specify things exactly so that browsers are interoperable, even if there are clearer ways of doing the same thing? 44837 5 mounir 2011-01-28 14:56:30 +0000 What I meant is it's better to request the UA to behave like the system usually behave to keep some consistency. If we do that, authors would not be able to [sanely] rely on a particular behavior but given that we have the selection API, it doesn't seem to be a big deal. 44861 6 ayg 2011-01-28 21:07:55 +0000 Is platform consistency relevant to focus()? Would users expect behavior of focus() to match the platform behavior of tabbing to the field? That seems unlikely to me, unless it's being used specifically to emulate tabbing for some reason. 44883 7 mounir 2011-01-29 23:31:04 +0000 Given that systems might have different behavior for that and the web platform has an API to override this behavior, it doesn't sound really important to force all UAs to have the same behavior on all platforms. FWIW, a lot of things in focus management seems to be "do whatever the platform do". Anyway, that's no big deal. 45849 8 ian 2011-02-19 00:11:03 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: It's platform-specific, but I've explicitly called out where it has to happen if it happens. (It has to be platform-specific, because users will complain if, e.g., tabbing to a field doesn't do the same thing as in other apps on their platform.) 45851 9 contributor 2011-02-19 00:26:18 +0000 Checked in as WHATWG revision r5911. Check-in comment: Define when the platform-specific focusing behavior happens relative to focus events, etc. http://html5.org/tools/web-apps-tracker?from=5910&to=5911 53889 10 mike 2011-08-04 05:34:12 +0000 mass-move component to LC1