Ideas for how to implement:

- Add a screen offset to the bounds information coming from the window server.
- Make it so that each root's bounds are in screen space.

This de facto works, even if it's slightly accidental.

With ash as it is, all layers in the window manager are the size of the screen, therefore the parent of an individual window will be in screen coordinates.

Explicit support per the original report is probably needed to make this work in the multi-display case, but we aren't tackling that this quarter. Tossing this back.

I believe this is only an issue for clients that are embedded in non-top-level windows, which don't come up that often. I'm going to remove this as a blocker for 660994.

+sadrul and fady as this may be more important to mus in renderer.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Un-cc-ing me from all bugs on my final day.

Deprecating Proj-Mustash-Mus-WS in favor of component Internals>Services>WindowService.