It turns out TouchSelectionController::OnSelectionEmpty(true) is being called shortly (milliseconds) after TouchSelectionController::WillHandleTapEvent() where the value of selection_empty_ is being checked.
Setting selection_empty_ to true doesn’t trigger an update of the insertion handle, I wonder whether that should be considered a bug in chromium. Couldn’t find any open issue in the chromium bug tracker for that.
It turns out TouchSelectionC ontroller: :OnSelectionEmp ty(true) is being called shortly (milliseconds) after TouchSelectionC ontroller: :WillHandleTapE vent() where the value of selection_empty_ is being checked.
Setting selection_empty_ to true doesn’t trigger an update of the insertion handle, I wonder whether that should be considered a bug in chromium. Couldn’t find any open issue in the chromium bug tracker for that.