- From: snianu <notifications@github.com>
- Date: Thu, 04 Mar 2021 12:18:54 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 4 March 2021 20:19:06 UTC
@cynthia Could you please let us know if the above answers address your concerns or not? This is currently blocking spec review & shipping in Chromium as based on the outcome of this discussion it may lead to significant changes in the API structure/code. We had this discussion at the TPAC meeting and we came to a consensus that `VisualViewport `is not the right place to fire `geometrychange `event caused by virtual keyboard `show/hide`. One of the reasons is with `overlaysContent `flag set, the VK doesn't change the `VisualViewport `i.e. the keyboard is overlaid on top of the content and doesn't "`resize`" or change the `VisualViewport `in any way. These discussions were buried in the show/hide policy thread which was opened separately. The discussions about `VisualViewport `APIs start from [here](https://github.com/w3ctag/design-reviews/issues/498#issuecomment-643391856). The MoM of the TPAC breakout session discussion is [here ](https://www.w3.org/2020/10/30-editing-minutes.html) Thank you for all the feedback so far! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/507#issuecomment-790911853
Received on Thursday, 4 March 2021 20:19:06 UTC