Don't let the parent class's weird implementation run when the
widget is focused through other code paths (e.g. clicking on
the non-input part of it).
We still need to fix the behavior when you click in the
input twice (the first click shows the popup and the second
click hides it), but this is much better already.
Related to I21b8cff4048 in oojs-ui.
Bug: T149452
Change-Id: I08743c64ea32feace757e2a8626df2f5310cfbc9