Add a safelyBlurElement util.

Author: tugorez

lib/web_ui/lib/src/engine/semantics/semantics.dart

@@ -1928,7 +1928,7 @@ class SemanticsObject {
   void dispose() {
     assert(!_isDisposed);
     _isDisposed = true;
-    element.remove();
+    EnginePlatformDispatcher.instance.viewManager.safelyBlurElement(element, removeElement: true);
     _parent = null;
     semanticRole?.dispose();
     semanticRole = null;

lib/web_ui/lib/src/engine/semantics/text_field.dart

@@ -114,16 +114,7 @@ class SemanticsTextEditingStrategy extends DefaultTextEditingStrategy {
     }
     subscriptions.clear();
     lastEditingState = null;
-
-    // If the text element still has focus, remove focus from the editable
-    // element to cause the on-screen keyboard, if any, to hide (e.g. on iOS,
-    // Android).
-    // Otherwise, the keyboard stays on screen even when the user navigates to
-    // a different screen (e.g. by hitting the "back" button).
-    // Keep this consistent with how DefaultTextEditingStrategy does it. As of
-    // right now, the only difference is that semantic text fields do not
-    // participate in form autofill.
-    DefaultTextEditingStrategy.scheduleFocusFlutterView(activeDomElement, activeDomElementView);
+    EnginePlatformDispatcher.instance.viewManager.safelyBlurElement(activeDomElement);
     domElement = null;
     activeTextField = null;
     _queuedStyle = null;

lib/web_ui/lib/src/engine/text_editing/text_editing.dart

@@ -1411,9 +1411,9 @@ abstract class DefaultTextEditingStrategy with CompositionAwareMixin implements
         inputConfiguration.autofillGroup?.formElement != null) {
       _styleAutofillElements(activeDomElement, isOffScreen: true);
       inputConfiguration.autofillGroup?.storeForm();
-      scheduleFocusFlutterView(activeDomElement, activeDomElementView);
+      EnginePlatformDispatcher.instance.viewManager.safelyBlurElement(activeDomElement);
     } else {
-      scheduleFocusFlutterView(activeDomElement, activeDomElementView, removeElement: true);
+      EnginePlatformDispatcher.instance.viewManager.safelyBlurElement(activeDomElement, removeElement: true);
 		}
     domElement = null;
   }
@@ -1573,29 +1573,6 @@ abstract class DefaultTextEditingStrategy with CompositionAwareMixin implements
   void moveFocusToActiveDomElement() {
     activeDomElement.focusWithoutScroll();
   }
-
-  /// Move the focus to the given [EngineFlutterView] in the next timer event.
-  ///
-  /// The timer gives the engine the opportunity to focus on another element.
-  /// Shifting focus immediately can cause the keyboard to jump.
-  static void scheduleFocusFlutterView(
-    DomElement element,
-    EngineFlutterView? view, {
-    bool removeElement = false,
-  }) {
-    Timer(Duration.zero, () {
-      // If by the time the timer fired the focused element is no longer the
-      // editing element whose editing session was disabled, there's no need to
-      // move the focus, as it is likely that another widget already took the
-      // focus.
-      if (element == domDocument.activeElement) {
-        view?.dom.rootElement.focusWithoutScroll();
-      }
-      if (removeElement) {
-        element.remove();
-      }
-    });
-  }
 }
 
 /// IOS/Safari behaviour for text editing.

lib/web_ui/lib/src/engine/view_embedder/flutter_view_manager.dart

@@ -113,6 +113,29 @@ class FlutterViewManager {
     return viewId == null ? null : _viewData[viewId];
   }
 
+  /// Safely manages focus when blurring and optionally removing a DOM element.
+  ///
+  /// By using a zero-delay timer, this function ensures the blur operation doesn't
+  /// disrupt the framework's view focus management.
+  ///
+  /// [removeElement] controls whether the element is removed from the DOM after being blurred.
+  void safelyBlurElement(DomElement element, {bool removeElement = false}) {
+    final EngineFlutterView? view = findViewForElement(element);
+
+    Timer(Duration.zero, () {
+      // If by the time the timer fired the focused element is no longer the
+      // editing element whose editing session was disabled, there's no need to
+      // move the focus, as it is likely that another widget already took the
+      // focus.
+      if (element == domDocument.activeElement) {
+        view?.dom.rootElement.focusWithoutScroll();
+      }
+      if (removeElement) {
+        element.remove();
+      }
+    });
+  }
+
   void dispose() {
     // We need to call `toList()` in order to avoid concurrent modification
     // inside the loop.