You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The screen of my current computer is small, and so, contrary to 2 months ago, I use chrome with its windows maximized. I had not used TF's saved tabs utils now, using instead chrome's ability to start "where I left off" and bookmarked folders.
What I have noticed is that TF opens saved tabs in a window that is nor maximized, neither at the default "restored" size. TF opens the window not maximized, but with its borders streched to the outmost limits of the screen. If I open a new window from a "restored" window, and then use TF to open saved tabs, the new window open with the correct "restored" dimensions.
Edit: You have to open a new maximized window from a maximized window to enable this behaviour.
It's logical, TF remembers the dimensions of the last opened window. Except that TF doesn't see that this is a maximized window. Or is it a chrome problem?
The text was updated successfully, but these errors were encountered:
The screen of my current computer is small, and so, contrary to 2 months ago, I use chrome with its windows maximized. I had not used TF's saved tabs utils now, using instead chrome's ability to start "where I left off" and bookmarked folders.
What I have noticed is that TF opens saved tabs in a window that is nor maximized, neither at the default "restored" size. TF opens the window not maximized, but with its borders streched to the outmost limits of the screen. If I open a new window from a "restored" window, and then use TF to open saved tabs, the new window open with the correct "restored" dimensions.
Edit: You have to open a new maximized window from a maximized window to enable this behaviour.
It's logical, TF remembers the dimensions of the last opened window. Except that TF doesn't see that this is a maximized window. Or is it a chrome problem?
The text was updated successfully, but these errors were encountered: