According to the discussion with Masayuki, the root cause here is that we don't support mouse on mobile formally/by default. We agreed with makoto-san’s comment 5; ideally we should handle this on Gecko. We need thorough audits and tests to support this properly, and based on our best educated guess, this may not be easy tweaks. I will have to take this to our planning backlog.
Bug 1879701 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
According to the discussion with Masayuki, the root cause here is that we don't support mouse on mobile formally/by default. We agreed with makoto-san’s comment 5; ideally we should handle this on Gecko. We need thorough audits and tests to support this properly, and based on our best educated guess, this may not be easy tweaks. I will have to take this to our planning backlog. In the meanwhile, I know that Makoto-san has more recent experiences in handling ui events on mobile. Please feel free to chime in to point us where the gecko change may be or correct me. Thanks!
According to the discussion with Masayuki, the root cause here is that we don't support mouse input on mobile formally/by default. We agreed with makoto-san’s comment 5; ideally we should handle this on Gecko. We need thorough audits and tests to support the mouse input properly, and based on our best educated guess, this may not be easy tweaks. We don't yet have a nice picture of the entry points in our code that we need to touch. I will have to take this to our planning backlog. In the meanwhile, I know that Makoto-san has more recent experiences in handling ui events on mobile. Please feel free to chime in to point us where the gecko change may be or correct me. Thanks!
According to the discussion with Masayuki, the root cause here is that we don't support mouse input on mobile formally/by default. We agreed with makoto-san’s comment 5; ideally we should handle this on Gecko. We need thorough audits and tests to support the mouse input properly, and based on our best educated guess, this may not be easy tweaks. I will have to take this to our planning backlog. In the meanwhile, I know that Makoto-san has more recent experiences in handling ui events on mobile. Please feel free to chime in to point us where the gecko change may be or correct me. Thanks!
According to the discussion with Masayuki, the root cause here is that we don't support mouse input on mobile formally/by default. We agreed with makoto-san’s comment 5; ideally we should handle this on Gecko. We need thorough audits and tests to support the mouse input properly, and based on our best educated guess, this may not be easy tweaks. I will have to take this to our planning backlog. In the meanwhile, I know that Makoto-san has more recent experiences in handling ui events on mobile. Please feel free to chime in to point us where the gecko change may be (looks like [this](https://bugzilla.mozilla.org/show_bug.cgi?id=1805341#c16)?) or correct me. Thanks!