New updates are added at the bottom of this story…….
The original story (published April 2, 2022) reads as follows:
Google Chrome is one of the most popular web browsers in the world. It is available for desktop computers and mobile devices.
From time to time, Google Chrome receives new updates with new features, improvements, and fixes for issues in previous versions.
Recently, Google Chrome received its stable v100 update. However, it seems that the update also brought some issues that negatively affect the user experience.
According to several reports, the Google Chrome v100 update is causing an issue with tabs not auto-maximizing or snapping to full size when moved to create a new window (1, 2, and 3).
Google Chrome tabs are not automatically maximized when swiping to turn them into windows
Normally, Google Chrome lets you drag a tab to the center of the screen (or to a second screen) to turn it into a new window. In this case, the new window is automatically maximized.
However, this behavior seems to have changed after the latest v100 update. Now Google Chrome tabs are not automatically maximized when you drag them to a new Chrome window.
Instead of being maximized, dragged tabs stay in the middle of the screen and will only become a new maximized window if you drag it directly to the top of the screen.
Sliding tab for observation
When I dragged a chrome tab to another screen, I could drag it anywhere on the screen and it automatically filled the screen. But now when I drag it, it just stays where I drag it, then I have to drag it up the screen to make it bigger. How can I change it to autofill the screen? Thank you!
source
Dragging a tab to create a new window no longer automatically maximizes it
If I had two tabs open, before Chrome 100 I could drag a tab to the center of the screen to create a new window that would automatically maximize itself. Now the tab freezes where I dropped it, in a smaller window.
How can I modify it?
source
There is no official recognition yet
There is still no official acknowledgment of this from Google. Therefore, it is unknown if the new behavior is the expected behavior after an update or if it is a problem.
There is also no workaround to fix the issue on Google Chrome v100. For now, the only thing you can do is revert to the previous version of the browser.
We’ll update this story as new relevant details become available.
First update (April 16)
4:20 p.m. (Indochina time): One of the affected users suggested a chrome extension that fixes this problem. So this can be a potential fix for users to try until the developers fix it.
PiunikaWeb began as a technology investigative journalism website with a primary focus on ‘hack’ or ‘exclusive’ news. In no time, our stories were picked up by Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors and many more. Want to know more about us? Head here.