Open bruzzers opened 1 year ago
👋 @bruzzers
NOTE: This comment is auto-generated.
Are you sure you have already searched for the same problem?
Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!
If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.
In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE]
or ios WKWebView [MY ERROR HERE]
keywords.
Following these steps can save you, me, and other people a lot of time, thanks!
Hi, I too have the same problem.
The problem is systematic and we have not found a solution online. Accessibility not working, other flutter webview plugins read accessibility correctly.
Have the same problem too, had to revert back to v5.7.1+2
Hi @pichillilorenzo
The issue is cased by the removal of the options.useHybridComposition
constraint in c2ce274. I've had some experience with screen readers and noticed that they can be a bit fussy when working with an overflow. It looks like it's something to do with the layout params for pull to refresh.
Semantics is completely broken for inAppWebView on Android and iOS.
Could you please provide an update on when this problem might be resolved, @pichillilorenzo ?
Environment
Device information: all Android
Description
Using this version of the plugin when the talkback recognise the web view, when swipe talkback not move to web page elements but to the next element of the app. If I move to 5.7.1+2 version of plugin it work correctly. I think the change in 5.7.2 broke something inside the accessibility and talkback.