-
Notifications
You must be signed in to change notification settings - Fork 4
update chrome 142 faq #966
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the FAQ documentation for troubleshooting Chromium 142+ local network access restrictions when using Dynamic Web TWAIN. The changes clarify that the provided steps help users grant browser permissions but do not bypass Chromium's security model, and outline upcoming UX improvements in v19.3 to help users better identify and resolve permission-related issues.
- Added warning clarifying that the resolution steps grant browser permissions rather than bypassing security restrictions
- Updated roadmap section to describe planned UX enhancements for better error messaging and permission guidance
- Updated metadata to reflect the latest modification date
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I think we have completed some UI/UX improvements in 19.3, should we update the wording in the |
Yes, we can update the title "Roadmap", like "How Web TWAIN Prompts the User about the Permission"? |
Co-authored-by: Louie-Dynamsoft <[email protected]>
This pull request updates the FAQ article on troubleshooting local network access issues with Dynamic Web TWAIN in Chromium-based browsers. The main focus is to clarify the limitations imposed by browser security, improve user guidance, and outline upcoming user experience enhancements.
Clarifications on browser restrictions and user guidance:
Roadmap and user experience improvements:
Metadata update:
last_modifieddate in the article front matter.