-
Notifications
You must be signed in to change notification settings - Fork 6
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
Copy answer button not working #3
Comments
Unfortunately webview does not support that. But you can long click on the text and select it |
Sorry to spam all your open issues but this is again possible if you know the class ID where the data is located: https://stackoverflow.com/questions/53945593/copy-button-in-a-webview-doesnt-work-why Many thanks for making this app btw. If it could simply retain login on my device it would be more than good enough for me. |
I have seen that as well, but I don't know the class ID where data is located... |
You can't test it in developer mode? Ask it something and find the class ID which has the answer in it. |
If there are several answers in the thread, it will get more complex. And I am not a html / javascript expert. You can simply mark the part you need and copy it |
Seems to be a bug in WebView reported long ago in 2015 and still not fixed: |
This version shows a message when the user clicks on the copy button and tells him to do it manually. https://github.com/woheller69/gptAssist/suites/13658024142/artifacts/754206126 |
Strange. The README says, that the app is partly based on GMaps VW, where coping (via the share button) works perfectly fine for me! In gptAssist it is broken though. WebView: Vanadium (GrapheneOS) System WebView |
somehow Google manages this probably in their own Javascript code of Google Maps. GMapsWV only has a listener for a change in clipboard and reacts if clipboard changes |
The button simply doesn't do anything. The copy button can be pressed and briefly changes to a checkmark but doesn't actually copy the answer.
Tested on Android 11, OnePlus 9 Pro
The text was updated successfully, but these errors were encountered: