-
Notifications
You must be signed in to change notification settings - Fork 29
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
Disturbs the mouse icon location in non-snap software #31
Comments
Could not reproduce with Ubuntu 22.04 with ghome-shell 42.4. The only thing I did see is that OSK wasn't showing up when you tap on input fields. But it behaves the same way with the original Gnome OSK, so it's likely an issue with Brave not implementing/emitting some Gnome event when the user taps on a text input. |
By "disturbed" I mean that when I try to select a text for coping,
another element or text of website is selected/copied.
…On L, okt 1 2022 at 13:21:00 -0700, Nick Shmyrev ***@***.***> wrote:
Could not reproduce with Ubuntu 22.04 with ghome-shell 42.4.
What do you mean by "disturbed"? Please describe in more details
what you're seeing, or better yet take a screenshot, or record a
gif/video.
The only thing I did see is that OSK wasn't showing up when you tap
on input fields. But it behaves the same way with the original Gnome
OSK, so it's likely an issue with Brave not implementing/emitting
some Gnome event when the user taps on a text input.
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXBRQLK64VEI6N7A24YOSDWBCMKZANCNFSM6AAAAAAQ2R7Q4Y>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This extension does not interact with copy, paste or text selection functions in any way. |
Screencast from 06.10.2022 10:30:28.webm |
Describe the bug
Clicking on a website elements (buttons, places where text can be inserted) is disturbed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The button or other clickable element should be selected and/or become available/focused. Instead, website reacts like I have clicked on something else, rather on the needed button. Seems like the on-screen keyboard moves the website up or down instead focusing a mouse click on a place what I have clicked.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
System is a fresh installation.
No other extension is interfering with on-screen keyboard.
Does
journalctl /usr/bin/gnome-shell -f -o cat
show any errors?(../clutter/clutter/clutter-actor.c:12430):clutter_actor_event: runtime check failed: (retval == CLUTTER_EVENT_PROPAGATE) (../clutter/clutter/clutter-actor.c:12430):clutter_actor_event: runtime check failed: (retval == CLUTTER_EVENT_PROPAGATE) (../clutter/clutter/clutter-actor.c:12430):clutter_actor_event: runtime check failed: (retval == CLUTTER_EVENT_PROPAGATE) meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Ignored exception from dbus method: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownInterface: Object does not implement the interface Window manager warning: last_focus_time (337608) is greater than comparison timestamp (380). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: last_user_time (337608) is greater than comparison timestamp (380). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: W12 appears to be one of the offending windows with a timestamp of 337608. Working around... Window manager warning: W0 appears to be one of the offending windows with a timestamp of 310923. Working around...
Can you see any errors in looking glass? No
The text was updated successfully, but these errors were encountered: