Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New issue 19938 by silenturbanfox: Chrome does not respect constraints placed on it by tiling WMs (Awesome) http://code.google.com/p/chromium/issues/detail?id=19938 Chrome Version : 3.0.198.1-r23116 OS + version : Ubuntu Linux 9.10 (Karmic) CPU architecture (32-bit / 64-bit): 32 bit window manager : Awesome 3.3 (http://awesome.naquadah.org/) URLs (if applicable) : N/A Behavior in Firefox 3.x (if applicable): Behaves as expected. Behavior in Chrome for Windows (optional): N/A What steps will reproduce the problem? 1. Use a tiling layout mode in Awesome 2. Launch a couple of other applications (terminals, for instance) 3. Launch Chrome What is the expected result? Expected result is that Chrome will be resized by the window manager as appropriate and put into the tiling layout. It should behave this way when "Use system title bar and borders" is enabled, but should be free to do as it wishes when this is not enabled. What happens instead? Chrome is placed into "floating" mode by Awesome, bypassing the layout. I cannot toggle this floating state, indicating Chrome is somehow ignoring/overriding client resizes. In my case, this means that Chrome fills the entire screen, hiding all the windows in the tiled layer unless I explicity raise them again. Please provide any additional information below. Attach a screenshot and backtrace if possible. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
