After the virtual keyboard is shown/hidden, the geometrychange event gets dispatched. It contains info about the VK’s size.
I have received reports from frameworks like Ionic that they would like to know these values upfront, before the VK is actually shown, so that they can prepare things in the UI – such as FABs or the like – before the keyboard gets shown.
A beforegeometrychange would solve this, reporting boundingRect of the VK that is about to be shown.
After the virtual keyboard is shown/hidden, the
geometrychangeevent gets dispatched. It contains info about the VK’s size.I have received reports from frameworks like Ionic that they would like to know these values upfront, before the VK is actually shown, so that they can prepare things in the UI – such as FABs or the like – before the keyboard gets shown.
A
beforegeometrychangewould solve this, reportingboundingRectof the VK that is about to be shown.