a) any process can change the background image. changing the background image is done by drawing pixels to the root-window, any process can do that. and .. to your surprise .. one can do that without detecting the change. and furthermore: how should the window-manager react on the change? obviously the end-user has called a program which set the background, from fluxbox' point of view there is no difference between fbsetbg or nautilus in regards to if they change the background pixels. even IF "the app" (wine or something else) does not write their background pixels to the root-window but to another window in front of the root-window which is NOT handling events (so fluxbox would receive the right-click in that case): we have no means to detect the changes in the pixels belonging to that window.
b) the chrome-argument didn't try to explain the change of background window but addressed the issue that right-clicks are handled by the app covering the area where the end-user clicks with her mouse. if you as the end-user launch any app with maximal coverage of the monitor than you can not right-click the root-window which is what would trigger the RootMenu. you are not considerung right-clicking a regular xterm or a regular sized chrome or a regular sized xyz and not getting the RootMenu a "bug" either, do you? if you launch apps in "fullscreen", this is what you get.
c) fluxbox does not generate the menu used in ubuntu/debian, it is generated by their own mechanism. you can fill a bugreport towards that end, if you like. some other menu-generators are using the .desktop files: fluxbox does not control the content of these .desktop files either, the launch arguments are inside. if you change the general launch arguments there: a regular gnome-user will be very disappointed, i can promise you that.
again: i do not see how fluxbox can handle the things you think are "bugs": fullscreen-apps (no matter on what desktop-layer) will complaint if the right-clicks are not coming through. background-setters would be pissed when fluxbox would reset the background (if fluxbox would be able to reliable detect such changes).
do not think i do not see the problem you have (experience wise), but there is nothing i as the currently active fluxbox maintainer might do about it.
a) any process can change the background image. changing the background image is done by drawing pixels to the root-window, any process can do that. and .. to your surprise .. one can do that without detecting the change. and furthermore: how should the window-manager react on the change? obviously the end-user has called a program which set the background, from fluxbox' point of view there is no difference between fbsetbg or nautilus in regards to if they change the background pixels. even IF "the app" (wine or something else) does not write their background pixels to the root-window but to another window in front of the root-window which is NOT handling events (so fluxbox would receive the right-click in that case): we have no means to detect the changes in the pixels belonging to that window.
b) the chrome-argument didn't try to explain the change of background window but addressed the issue that right-clicks are handled by the app covering the area where the end-user clicks with her mouse. if you as the end-user launch any app with maximal coverage of the monitor than you can not right-click the root-window which is what would trigger the RootMenu. you are not considerung right-clicking a regular xterm or a regular sized chrome or a regular sized xyz and not getting the RootMenu a "bug" either, do you? if you launch apps in "fullscreen", this is what you get.
c) fluxbox does not generate the menu used in ubuntu/debian, it is generated by their own mechanism. you can fill a bugreport towards that end, if you like. some other menu-generators are using the .desktop files: fluxbox does not control the content of these .desktop files either, the launch arguments are inside. if you change the general launch arguments there: a regular gnome-user will be very disappointed, i can promise you that.
again: i do not see how fluxbox can handle the things you think are "bugs": fullscreen-apps (no matter on what desktop-layer) will complaint if the right-clicks are not coming through. background-setters would be pissed when fluxbox would reset the background (if fluxbox would be able to reliable detect such changes).
do not think i do not see the problem you have (experience wise), but there is nothing i as the currently active fluxbox maintainer might do about it.