Comment #13 on issue 6961 by b...@chromium.org: Double Clicking top left doesn't close Chrome http://code.google.com/p/chromium/issues/detail?id=6961
Here's what I've figured out so far: double clicking typically works in Windows apps because the system menu region of the caption area is a special kind of Windows menu bar. When you double click on a menu in a menu bar, if that menu's associated popup has a menuitem set as "default" that item's action is performed automatically. In the case of the system menu, this item is SC_CLOSE. However, we open the item manually using TrackPopupMenu because we have a custom frame and apparently returning HTSYSMENU for that region when handling WM_NCHITTEST is not enough to get windows to show the system menu for us. This is frustrating. When you call TrackPopupMenu it turns out the sequence of messages sent to your app is dramatically different to the messages sent to an app when it's a regular system menu. And since we don't have that built in menu bar handling since we have a custom frame, the double click handling is broken. Other features like being able to click down and drag into the system menu also don't work. What we need is a way to be able to tell the windows system menu for the window to run, at a specific position, but _not_ using TrackPopupMenu. I'm not sure how to do this. -- 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 -~----------~----~----~----~------~----~------~--~---
