Chrome Version: 70.0.3519.0, but I have seen this repro on much earlier versions.


What steps will reproduce the problem?
(1) Show a context menu on an app icon by long press (the source of the menu must have the RunType SEND_GESTURE_EVENTS_TO_OWNER, so either a launcher or shelf app icon will work).
(2) Without releasing or moving the finger, touch the screen with a second finger.

What is the expected result?
The widget that owned the menu should continue to receive events as normal.

What happens instead?
1. The widget no longer receives GestureEvents, but can receive mouse events. 
2. All further touch (gesture) events arrive to EventHandler as TouchEvents but these events never make it to the view.

Not sure exactly what's going on here. This bug has been around for a while (likely since the birth of SEND_GESTURE_EVENTS_TO_OWNER but we never had repro steps).

This is a P-1 for M-70 because this bug requires the user to kill the widget (app list) then show a new one, but this is not possible with the home launcher, so users will need to reset their devices to make their AppList respond to touch events.

If this is reproduced on the shelf, the shelf becomes unresponsive until the device is reset.

 

Chrome Version: 70.0.3519.0, but I have seen this repro on much earlier versions.


What steps will reproduce the problem?
(1) Show a context menu on an app icon by long press (the source of the menu must have the RunType SEND_GESTURE_EVENTS_TO_OWNER, so either a launcher or shelf app icon will work).
(2) Without releasing or moving the finger, touch the screen with a second finger.

What is the expected result?
The widget that owned the menu should continue to receive events as normal.

What happens instead?
1. The widget no longer receives GestureEvents, but can receive mouse events. 
2. All further touch (gesture) events at event_handler.cc as TouchEvents but these events never make it to the view.

Not sure exactly what's going on here. This bug has been around for a while (likely since the birth of SEND_GESTURE_EVENTS_TO_OWNER but we never had repro steps).

This is a P-1 for M-70 because this bug requires the user to kill the widget (app list) then show a new one, but this is not possible with the home launcher, so users will need to reset their devices to make their AppList respond to touch events.

If this is reproduced on the shelf, the shelf becomes unresponsive until the device is reset.

 

Chrome Version: 70.0.3519.0, but I have seen this repro on much earlier versions.


What steps will reproduce the problem?
(1) Show a context menu on an app icon by long press (the source of the menu must have the RunType SEND_GESTURE_EVENTS_TO_OWNER, so either a launcher or shelf app icon will work).
(2) Without releasing or moving the finger, touch the screen with a second finger.

What is the expected result?
The widget that owned the menu should continue to receive events as normal.

What happens instead?
1. The widget no longer receives GestureEvents, but can receive mouse events. 
2. All further touch (gesture) events at event_handler.cc as TouchEvents but these events never make it to the view.

Not sure exactly what's going on here. This bug has been around for a while (likely since the birth of SEND_GESTURE_EVENTS_TO_OWNER but we never had repro steps).

This is a P-1 for M-70 because this bug requires the user to kill the widget (app list) then show a new one, but this is not possible with the home launcher, so users will need to reset their devices to make their AppList respond to touch events.

If this is reproduced on the shelf, the shelf becomes unresponsive until the device is reset.

 

Chrome Version: 70.0.3519.0, but I have seen this repro on much earlier versions.


What steps will reproduce the problem?
(1) Show a context menu on an app icon by long press (the source of the menu must have the RunType SEND_GESTURE_EVENTS_TO_OWNER, so either a launcher or shelf app icon will work).
(2) Without releasing or moving the finger, touch the screen with a second finger.

What is the expected result?
The widget that owned the menu should continue to receive events as normal.

What happens instead?
1. The widget no longer receives GestureEvents, but can receive mouse events. 
2. All further touch (gesture) events at event_handler.cc as TouchEvents but these events never make it to the view.

Not sure exactly what's going on here. This bug has been around for a while (likely since the birth of SEND_GESTURE_EVENTS_TO_OWNER but we never had repro steps).

This is a P-1 for M-70 because this bug requires the user to kill the widget (app list) then show a new one, but this is not possible with the home launcher, so users will need to log in/out to make their AppList respond to touch events.

If this is reproduced on the shelf, the shelf becomes unresponsive until the device is reset.

 

Chrome Version: 70.0.3519.0, but I have seen this repro on much earlier versions.


What steps will reproduce the problem?
(1) Show a context menu on an app icon by long press (the source of the menu must have the RunType SEND_GESTURE_EVENTS_TO_OWNER, so either a launcher or shelf app icon will work).
(2) Without releasing or moving the finger, touch the screen with a second finger.

What is the expected result?
The widget that owned the menu should continue to receive events as normal.

What happens instead?
1. The widget no longer receives GestureEvents, but can receive mouse events. 
2. All further touch (gesture) events at event_handler.cc as TouchEvents but these events never make it to the view.

Not sure exactly what's going on here. This bug has been around for a while (likely since the birth of SEND_GESTURE_EVENTS_TO_OWNER but we never had repro steps).

This is a P-1 for M-70 because this bug requires the user to kill the widget (app list) then show a new one, but this is not possible with the home launcher, so users will need to log in/out to make their AppList respond to touch events.

If this is reproduced on the shelf, the shelf becomes unresponsive until the user logs in/out.