I see what's happened here. So... The change that we made in Bug 1645571 was to fix a glitchy behaviour that was ultimately caused by Windows trying (and intermittently failing) to resize our window a bunch of times on our behalf without us asking for it, causing the touch keyboard to flicker and disappear (leaving the touch user without a way to type). Unfortunately, it appears that we were actually *relying* on Windows to resize our window for us instead of doing it ourselves, and now that we've "opted out" of that glitchy behaviour, we need to do *something* about it ourselves. That could be resizing our Window (which is what Windows mostly tried to do previously), or (as :saschanaz suggested) we could try to resize the scrollable area. Either way though, I think either solution will take more time than we have, and I agree that the number of people that would be affected and annoyed by the original bug pales in comparison to the number of people that will now be affected and annoyed by this. I suggest we back it out and we can figure out what to do later. 😪
Bug 1907766 Comment 19 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I see what's happened here. So... The change that we made in Bug 1645571 was to fix a glitchy behaviour that was ultimately caused by Windows trying (and intermittently failing) to resize our window a bunch of times on our behalf without us asking for it, causing the touch keyboard to flicker and disappear (leaving the touch user without a way to type). Unfortunately, it appears that we were actually *relying* on Windows to resize our window for us instead of doing it ourselves, and now that we've "opted out" of that glitchy behaviour, we need to do *something* about it ourselves. That could be resizing our window (which is what Windows mostly tried to do previously), or (as :saschanaz suggested) we could try to resize the scrollable area. Either way though, I think either solution will take more time than we have, and I agree that the number of people that would be affected and annoyed by the original bug pales in comparison to the number of people that will now be affected and annoyed by this. I suggest we back it out and we can figure out what to do later. 😪