25897 2014-05-27 19:57:16 +0000 focusin and focusout should be included in the "focus update steps" 2018-02-27 10:52:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED MOVED https://bugzilla.mozilla.org/show_bug.cgi?id=687787 http://code.google.com/p/chromium/issues/detail?id=378163 P2 normal 2014 Q4 25877 1 travil ian annevk bugs crimsteam hober0 ian mike philipj public-html-admin public-html-wg-issue-tracking contributor oldest_to_newest 106852 0 travil 2014-05-27 19:57:16 +0000 +++ This bug was initially created as a clone of Bug #25877 +++ Presumably, focusin fires immediately before focus in the algorithm, and focusout fires immediately before blur in the algorithm (neither are cancelable). 106887 1 ian 2014-05-28 05:45:50 +0000 Apparently Chrome/IE support these, and Firefox is considering implementing it: https://bugzilla.mozilla.org/show_bug.cgi?id=687787 If we could get away with removing this from Chrome, it seems like that would be a win. It's not clear what focusin/focusout add that focus/blur don't. 106888 2 ian 2014-05-28 05:49:56 +0000 Pinged Chrome devs about maybe dropping this: https://code.google.com/p/chromium/issues/detail?id=378163 107003 3 ian 2014-05-29 21:02:52 +0000 Travis, is there a compat need for these? 107007 4 travil 2014-05-29 21:22:04 +0000 (In reply to Ian 'Hixie' Hickson from comment #3) > Travis, is there a compat need for these? I had data years ago (when I asked to have them added to DOM L3 Events in 2009 [1]), but don't have recent data. I can see about gathering that for you though... :) [1] https://dvcs.w3.org/hg/dom3events/rev/6d85eb1847a4 107048 5 ian 2014-05-30 18:25:26 +0000 Do you recall what your 2009 data said? 107054 6 travil 2014-05-30 18:39:23 +0000 No, but I just re-tested on 2014 data. In a relatively small sample size of "top sites" in world-wide geographic areas I found the following data for focusin and focusout usage (e.g., registration of these events): focusin usage: 117,588 / 569,726 (20.6%) focusout usage: 117,430 / 569,726 (20.6%) jQuery looks to be one of the major contributing factors... In the jQuery 1.11.1 uncompressed file, the following is quite telling: (function() { var i, eventName, div = document.createElement( "div" ); // Support: IE<9 (lack submit/change bubble), Firefox 23+ (lack focusin event) for ( i in { submit: true, change: true, focusin: true }) { eventName = "on" + i; [...] 107063 7 ian 2014-05-30 21:48:12 +0000 So if we remove support, jQuery would keep working? 109958 8 ian 2014-08-05 19:43:06 +0000 This is pending UseCounter data from Chrome. However, I'm not sure that data is going to be that useful. We know the events are used. The question is would pages break if the support was removed, given that many pages fall back to focus/blur. 111408 9 ian 2014-09-11 23:03:32 +0000 foolip: You're king of the feature removal, any interest in removing these redundant focus events? If I can't convince you, then I should just add them to the spec. 112166 10 philipj 2014-09-25 08:07:43 +0000 The use counter for focusin/focusout reached stable a few weeks ago: http://www.chromestatus.com/metrics/feature/timeline/popularity/433 At 3-4%, removal does not seem feasible. There's also a use counter for DOMFocusIn/DOMFocusOut: http://www.chromestatus.com/metrics/feature/timeline/popularity/211 That's currently around 0.2%, and if nobody else implements it and most content listens to both just to be safe, eventual removal seems possible. 123032 11 bugs 2015-09-02 10:58:53 +0000 I doubt this is a "good first bug", given that focusout/in may change focus or remove to-be-focused element from DOM and whatnot. 126474 12 bugs 2016-05-21 21:26:28 +0000 FWIW, looks like focusin/out have been implemented in Blink (at least) totally differently to what the spec says (and what IE does), so we may need to change the spec :/ 129082 13 annevk 2018-02-27 10:52:35 +0000 This is now tracked by https://github.com/whatwg/html/issues/3514.