Currently the FullscreenControlViewTest injects events directly to FullscreenControlHost and the underlying button during the test. This is not very robust as it doesn't verify if the input pipeline and event propagation is working properly.