Always explicitly set border widths on manage
When a window becomes managed, explicitly set the current border width
to the default instead of relying on the default value of -1 to apply
the correct value.
Now that there are two different kinds of default borders, a border
width value of -1 is ambiguous. This can lead to different border widths
effectively being applied when the container changes from tiling to
floating, which is surprising behavior.
This commit extends behavior introduced in this commit to normal
borders:
7afe9cc78b
Explicitly set current border width when BS_PIXEL
fixes #1304
This commit is contained in:
committed by
Michael Stapelberg
parent
c2ccfc7e60
commit
6bf7f8ef78
@ -454,11 +454,8 @@ void manage_window(xcb_window_t window, xcb_get_window_attributes_cookie_t cooki
|
||||
floating_enable(nc, automatic_border);
|
||||
}
|
||||
|
||||
if (nc->border_style == BS_PIXEL) {
|
||||
/* if the border style is BS_PIXEL, explicitly set the border width of
|
||||
* the new container */
|
||||
nc->current_border_width = (want_floating ? config.default_floating_border_width : config.default_border_width);
|
||||
}
|
||||
/* explicitly set the border width to the default */
|
||||
nc->current_border_width = (want_floating ? config.default_floating_border_width : config.default_border_width);
|
||||
|
||||
/* to avoid getting an UnmapNotify event due to reparenting, we temporarily
|
||||
* declare no interest in any state change event of this window */
|
||||
|
Reference in New Issue
Block a user