-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Text boxes In Google drive #5833
Labels
Comments
Try |
Thanks, I will update the issue. I still wish to block all device recognition attempts. |
As @srirambv mentioned you'll need to set All device recognition attempts allowed in shields for this text box feature to work. Closing. Marking wontfix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When device recognition shield is set to block all device recognition attempts text boxes in Google drive (Drawing and slides) break.
Steps to Reproduce
4.Hit space and type another word, watch the words layer up on top of each other
Actual result:
Words are layered on top of each other.
Expected result:
The words should not layer on top of each other.
Here is the exact same document but opened on Firefox rather than brave.
Reproduces how often:
This is easily reproduced, every time a text box is loaded while brave is blocking all device recognition attempts this will happen.
Brave version (brave://version info)
Brave | 0.68.132 Chromium: 76.0.3809.132 (Official Build) (64-bit)
Revision | fd1acc410994a7a68ac25bc77513d443f3130860-refs/branch-heads/3809@{#1035}
OS | Windows 10 OS Version 1903 (Build 18362.295)
This also happened before I updated to 0.68.131
Version/Channel Information:
Yes
Not sure
Yes
Yes
Other Additional Information:
yes - If device recognition is set to block only cross site or allow all, text boxes work as usual.
No
I refuse to download chrome, but there is no block device recognition option so no.
Miscellaneous Information:
Nothing else to say here
The text was updated successfully, but these errors were encountered: