Failure to restore size/position of TF window

[cxw42]

(reported to me)
Browser:

Google Chrome	138.0.7204.168 (Official Build) (64-bit) 
Revision	3e8d82e86e9f508e88ed406c2a24657a6c691d30-refs/branch-heads/7204@{#2081}
OS	Linux
JavaScript	V8 13.8.258.29
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/[138.0.0.0](http://138.0.0.0/) Safari/537.36
Command Line	/usr/bin/google-chrome-stable --flag-switches-begin --disable-smooth-scrolling --flag-switches-end --ozone-platform-hint=auto --ozone-platform=wayland --site-per-process

Error:

Uncaught TypeError: Error in invocation of windows.get(integer windowId, optional windows.QueryOptions queryOptions, function callback): No matching signature.
at eventOnResize (main_tl.js:2904:1)

[cxw42]

I am not able to repro on Chromium 138.0.7204.157 (Official Build) snap (64-bit) . Maybe Chrome-specific?

[cxw42]

I am also not able to repro on Chrome google-chrome-stable/now 138.0.7204.183-1. I wonder if it was a bug in 138.0.7204.168.

[CS-cwhite]

I am still experiencing this

Google Chrome	138.0.7204.183 (Official Build) (64-bit) 
Revision	e90faf484ddbc033fc9bf337621761d3dd5c5289-refs/branch-heads/7204@{#2435}
OS	Linux
JavaScript	V8 13.8.258.30
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36
Command Line	/usr/bin/google-chrome-stable --flag-switches-begin --disable-smooth-scrolling --flag-switches-end --ozone-platform-hint=auto --ozone-platform=wayland --site-per-process
Executable Path	/opt/google/chrome/google-chrome
Profile Path	/home/cwhite/.config/google-chrome/Default

Ubuntu 22.04.5 LTS

google-chrome-stable/stable,now 138.0.7204.183-1 amd64 [installed]

[CS-cwhite]

As of Chrome 140.0.7339.127 (Official Build) (64-bit) , size is being saved but position is not. Initialization step 7 says:

Object
  Got saved location: 
    tabfern-window-location: {height: 502, left: 0, top: 0, width: 629, winState: 'normal'}

I am having issues with other popups always being at the upper-left corner, so I think this might be Google's issue.