I remember David maintained it is because wayland doesn't allow set absolute position of a surface. So we create a shell surface with the size of the screen and make it transparent. And then put the content of the app as a sub surface on it.

To get ride of the display size shell surface, we need modify the code in android side.

David and Lloyd, could you please add more detail about it? Thanks.

#2, correct. There are some long term plans for moving Arc to something that is closer to a standard wayland app but not sure what the time line for that is.

The display sized surface at the bottom of each arc app is backed by a 1x1 buffer scaled to the display size and it has alpha=0 so we can probably detect that and limit the size of CompositorFrames based on it.

This is potentially blocking surface sync and viz work. Can we figure out a way to ensure that the CompositorFrame size matches the window size in exo despite ARC++ weirdness? Marking as P1.

I think we already workaround this problem. So it doesn't block surface sync and viz work.

Migrating from Internals>Viz to Internals>Services>Viz.