c41dc33590
When setting the geometry from content for floating windows, the coordinates for borders are normally taken into account. However in the case of a floating fullscreen window, we should not be doing this. Since the content of the container takes the space of the entire output, this causes the calculated borders to neccesarily be outside of the output. This later causes a problem when sending surface entrance events since in a multi-monitor setup, the border coordinates will overlap with another output despite the surface not actually being on that output at all. The fix is to just ignore border coordinates for a floating fullscreen container since fullscreen, of course, does not actually have any borders. Fixes #6080. |
||
|---|---|---|
| .. | ||
| arrange.c | ||
| container.c | ||
| node.c | ||
| output.c | ||
| root.c | ||
| view.c | ||
| workspace.c | ||