@atlaskit/editor-plugin-type-ahead 2.2.0 → 2.2.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @atlaskit/editor-plugin-type-ahead
 
+## 2.2.1
+
+### Patch Changes
+
+- [#130684](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/pull-requests/130684)
+  [`0656a8915e18f`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/0656a8915e18f) -
+  updated existing fix for focusOut typeahead trigger duplication to also include IE/Edge
+
 ## 2.2.0
 
 ### Minor Changes

package/dist/cjs/ui/InputQuery.js

@@ -284,15 +284,12 @@ var InputQuery = exports.InputQuery = /*#__PURE__*/_react.default.memo(function
         return;
       }
 
-      // See ED-14909: Chrome may emit focusout events where an input
-      // device was not directly responsible. (This rears in react v17+ consumers
-      // where react-managed node removal now appears to propagate focusout events to
-      // our event listener). As this path is strictly for click or other typeahead
-      // dismissals that don't involve typeahead item selection, we carve out an
-      // exception for Chrome-specific events where an input device was not the initiator.
-      if (_browser.browser.chrome && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
+      // Chrome and Edge may emit focusout events without direct input.
+      // This path handles dismissals that don't involve item selection, so we ignore these events.
+      // In Edge this also lead to duplication in the trigger character (@, /, :) as `cancel` would be called twice
+      if ((_browser.browser.ie || _browser.browser.chrome) && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
       // eslint-disable-next-line @typescript-eslint/no-explicit-any
-      !('sourceCapabilities' in event && event.sourceCapabilities)) {
+      !event.sourceCapabilities) {
         return;
       }
       cancel({

package/dist/es2019/ui/InputQuery.js

@@ -269,15 +269,12 @@ export const InputQuery = /*#__PURE__*/React.memo(({
         return;
       }
 
-      // See ED-14909: Chrome may emit focusout events where an input
-      // device was not directly responsible. (This rears in react v17+ consumers
-      // where react-managed node removal now appears to propagate focusout events to
-      // our event listener). As this path is strictly for click or other typeahead
-      // dismissals that don't involve typeahead item selection, we carve out an
-      // exception for Chrome-specific events where an input device was not the initiator.
-      if (browser.chrome && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
+      // Chrome and Edge may emit focusout events without direct input.
+      // This path handles dismissals that don't involve item selection, so we ignore these events.
+      // In Edge this also lead to duplication in the trigger character (@, /, :) as `cancel` would be called twice
+      if ((browser.ie || browser.chrome) && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
       // eslint-disable-next-line @typescript-eslint/no-explicit-any
-      !('sourceCapabilities' in event && event.sourceCapabilities)) {
+      !event.sourceCapabilities) {
         return;
       }
       cancel({

package/dist/esm/ui/InputQuery.js

@@ -273,15 +273,12 @@ export var InputQuery = /*#__PURE__*/React.memo(function (_ref) {
         return;
       }
 
-      // See ED-14909: Chrome may emit focusout events where an input
-      // device was not directly responsible. (This rears in react v17+ consumers
-      // where react-managed node removal now appears to propagate focusout events to
-      // our event listener). As this path is strictly for click or other typeahead
-      // dismissals that don't involve typeahead item selection, we carve out an
-      // exception for Chrome-specific events where an input device was not the initiator.
-      if (browser.chrome && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
+      // Chrome and Edge may emit focusout events without direct input.
+      // This path handles dismissals that don't involve item selection, so we ignore these events.
+      // In Edge this also lead to duplication in the trigger character (@, /, :) as `cancel` would be called twice
+      if ((browser.ie || browser.chrome) && !(((_window$getSelection = window.getSelection()) === null || _window$getSelection === void 0 ? void 0 : _window$getSelection.type) === 'Range') &&
       // eslint-disable-next-line @typescript-eslint/no-explicit-any
-      !('sourceCapabilities' in event && event.sourceCapabilities)) {
+      !event.sourceCapabilities) {
         return;
       }
       cancel({

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@atlaskit/editor-plugin-type-ahead",
-	"version": "2.2.0",
+	"version": "2.2.1",
 	"description": "Type-ahead plugin for @atlaskit/editor-core",
 	"author": "Atlassian Pty Ltd",
 	"license": "Apache-2.0",
@@ -48,7 +48,7 @@
 		"@atlaskit/primitives": "^14.2.0",
 		"@atlaskit/prosemirror-input-rules": "^3.3.0",
 		"@atlaskit/theme": "^18.0.0",
-		"@atlaskit/tmp-editor-statsig": "^4.2.0",
+		"@atlaskit/tmp-editor-statsig": "^4.4.0",
 		"@atlaskit/tokens": "^4.5.0",
 		"@babel/runtime": "^7.0.0",
 		"@emotion/react": "^11.7.1",