- From: Dave Methvin <notifications@github.com>
- Date: Mon, 10 Oct 2016 09:32:38 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Message-ID: <w3c/uievents/issues/88/252672694@github.com>
We discussed this issue in the jQuery core team meeting today and our recommendation is: 1) Browsers should use the standards-mandated event order: focusout, focusin, blur, focus. Since focusout and focusin are cancellable they need to happen before focus/blur to prevent take-backsies. 2) Browsers **must** provide some feature detect so that developers can know if focusin/out are implemented. Ideally this would be done at the same time as the first point so developers could know that the events are also implemented *per-spec*. At the moment we don't know of any reliable feature detect for these events. The only thing jQuery guarantees right now is that focusin happens before focus and focusout happens before blur. Only IE11 has a reliable way to detect the events so jQuery simulates them even when the browser has them, which would be bad except that nobody seems to implement them correctly anyway. Once there is a reliable feature detect jQuery can defer to the working browser implementation. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/88#issuecomment-252672694
Received on Monday, 10 October 2016 16:33:11 UTC