Skip to content

Commit 1698125

Browse files
authored
Merge pull request #967 from dynamsoft-docs/preview
update chrome 142 faq (#966)
2 parents 12574b9 + 8ee44e8 commit 1698125

File tree

1 file changed

+23
-11
lines changed

1 file changed

+23
-11
lines changed

_articles/faq/chromium-142-local-network-access-issue.md

Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords: Dynamic Web TWAIN, Error Troubleshooting, CORS, unknown address space,
77
breadcrumbText: Error message - Permission was denied for this request to access the unknown address space
88
description: CORS unknown address space
99
date: 2025-11-04 17:21:42 +0800
10-
last_modified: 2025-12-12 10:04:00 +0800
10+
last_modified: 2025-12-17 16:00:00 +0800
1111
---
1212

1313
# Error Troubleshooting
@@ -72,6 +72,9 @@ Dynamic Web TWAIN relies on a locally installed service that listens on a loopba
7272

7373
### Resolution
7474

75+
> [!WARNING]
76+
> The steps outlined below **do not “fix” or bypass this restriction**, nor can Dynamic Web TWAIN override it programmatically. They simply ensure that the browser’s required permission is correctly granted so the local Dynamic Web TWAIN service is allowed to communicate with your application.
77+
7578
***1. To Manually Correct This in Chrome***
7679

7780
- Navigate to your Dynamic Web TWAIN page.
@@ -154,27 +157,36 @@ If the permission is not granted, consider displaying a user-friendly message di
154157
155158
This approach provides a more polished user experience, especially during onboarding or troubleshooting.
156159

157-
### Roadmap
160+
### Product Improvements Related to Local Network Access
161+
162+
Dynamic Web TWAIN v19.3 introduces **user-experience enhancements** to better surface local service connectivity and permission issues.
158163

159-
Dynamsoft plans to add a feature that automatically detects local service connectivity and permission status. If the connection is blocked, users will be prompted with a message and directed to this FAQ page.
164+
These changes **do not alter or bypass Chromium’s security model**. Their purpose is to make permission-related failures easier to identify and understand, and to guide users to the appropriate browser settings when access is blocked.
160165

161-
Here are the details:
166+
The key improvements include:
162167

163-
* When local network access is blocked, prompt the user with the following dialog:
168+
* **Explicit detection of blocked local network access** \
169+
When the browser blocks communication with the local service, a clear dialog is displayed explaining the cause and directing users to this FAQ.
164170

165171
![prompt blocked](/assets/imgs/local-network-access/prompt-blocked.jpg)
172+
173+
*Dialog 1 - Permission Guidance*
174+
175+
* **Clearer messaging during service installation** \
176+
A notice is added to the service installation dialog to inform users that a connection failure may be caused either by the service not being installed or by local network access being denied, as these two cases cannot be reliably distinguished.
166177

167-
*Dialog 1*
178+
![dialog installation](/assets/imgs/local-network-access/service-installation-dialog.png)
168179

169-
* Add a sentence about the permission in the service installation dialog, since we cannot determine whether the connection failure is due to the service not being installed or the access being blocked.
180+
*Dialog 2 - Service Installation*
170181

171-
![dialog installation](/assets/imgs/local-network-access/service-installation-dialog.png)
182+
Clicking "Guide" opens the permission guidance dialog shown above.
172183

173-
*Dialog 2*
184+
These improvements are **available starting with Dynamic Web TWAIN v19.3**.
174185

175-
Clicking "Guide" will open dialog 1, prompting the user to enable the permission.
186+
For older versions, a supplemental JavaScript file can be provided upon request by contacting [Dynamsoft Support](mailto:[email protected]).
176187

177-
This design will be integrated in v19.3. For old versions, we can include an extra js file, which can be retrieved by contacting [support](mailto://[email protected]).
188+
> [!NOTE]
189+
> This file improves user guidance only and does not change the underlying browser permission requirements.
178190
179191
## Other Causes of Failure to Connect to the Service
180192

0 commit comments

Comments
 (0)