Merge pull request #968 from dynamsoft-docs/jackson-preview

Jackson preview

Author: ztyyLV

_articles/faq/index.md

@@ -209,6 +209,7 @@ description: Dynamic Web TWAIN SDK Documentation FAQ
 32.  [Why am I unable to load the TIFF file into Dynamic Web TWAIN?](/_articles/faq/unable-to-load-4-bit-tiff.md)
 33.  [Error message - CORS Errors caused by local network access permissions when using Chromium 142 and later](/_articles/faq/chromium-142-local-network-access-issue.md)
 34.  [Error message - File is Damaged and Can’t Be Opened in macOS](/_articles/faq/file-damaged-on-macos.md)
+35.  [Safari 26.2 Regression Causing Dynamic Web TWAIN v19.3 Auto-Reconnect Failure on macOS](/_articles/faq/safari-26-2-regression.md)
 
 ## Licensing and Purchase
 

_articles/faq/safari-26-2-regression.md

@@ -0,0 +1,37 @@
+---
+layout: default-layout
+noTitleIndex: true
+needAutoGenerateSidebar: true
+title: Safari 26.2 Regression Causing Dynamic Web TWAIN v19.3 Auto-Reconnect Failure on macOS
+keywords: Dynamic Web TWAIN, macos, Auto-Reconnect, 19.3, Safari
+breadcrumbText: Safari 26.2 Regression Causing Dynamic Web TWAIN v19.3 Auto-Reconnect Failure on macOS
+description: Safari 26.2 Regression Causing Dynamic Web TWAIN v19.3 Auto-Reconnect Failure on macOS
+date: 2025-12-31 13:18:47 +0800
+last_modified: 2025-12-31 13:18:47 +0800
+---
+
+# Safari 26.2 Regression Causing Dynamic Web TWAIN v19.3 Auto-Reconnect Failure on macOS
+
+### Symptom
+
+After upgrading to Safari 26.2 on macOS, a compatibility issue was observed with Dynamic Web TWAIN v19.3.
+
+When a site installs or updates the Dynamic Web TWAIN v19.3 Service for the first time, the automatic connection and reconnect mechanism fails. A browser refresh is required to restore normal behavior.
+
+### Issue characteristics
+
+- Only occurs in Safari 26.2
+- Does not occur in Safari 26.1 or earlier versions
+- Does not occur in Dynamic Web TWAIN versions prior to 19.3
+
+### Reason
+
+Dynamic Web TWAIN 19.3 introduced a new configuration in reconnect requests: `targetAddressSpace: "loopback"`, following the Chrome Local Network Access documentation to explicitly indicate that the request targets the loopback address (127.0.0.1).
+
+In Safari 26.1 and earlier, this configuration is ignored and requests are sent normally.
+
+In Safari 26.2, `fetch` throws a `TypeError` when this configuration is present, causing the request to fail before being sent. As a result, `reconnect` cannot be implemented even though the Dynamsoft Service is installed and running.
+
+### Update
+
+The WebKit team has identified this issue as a regression in Safari 26.2 and has already fixed it. The fix will be included in an upcoming Safari release.