Bug 96055

Summary: Frameless app windows are non-draggable until the regions are updated
Product: WebKit Reporter: Junmin Zhu <junmin.zhu>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: ap, jianli, simon.fraser
Priority: P1    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: All   
Attachments:
Description Flags
patch for updating the draggable region when it's NULL if it's inside "WIDGET_REGION" jianli: review-

Junmin Zhu
Reported 2012-09-06 19:14:55 PDT
To repro (on Windows): - create a window with chrome.app.window.create('window.html', {frame:'none'}). - try to drag or resize the window. It doesn't work, but if you add a -webkit-widget-region property in the inspector, the window becomes draggable (and resizable). Original Bug from chromium: http://code.google.com/p/chromium/issues/detail?id=145175
Attachments
patch for updating the draggable region when it's NULL if it's inside "WIDGET_REGION" (793 bytes, patch)
2012-09-06 19:19 PDT, Junmin Zhu 		jianli: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Junmin Zhu
Comment 1 2012-09-06 19:19:10 PDT
Created attachment 162652 [details] patch for updating the draggable region when it's NULL if it's inside "WIDGET_REGION" Force to update the draggable region even it's NULL, if it's inside "WIDGET_REGION".
Jian Li
Comment 2 2012-09-06 23:00:33 PDT
Comment on attachment 162652 [details] patch for updating the draggable region when it's NULL if it's inside "WIDGET_REGION" We're going to change the default behavior to non-draggable. This issue will go away.
Alexey Proskuryakov
Comment 3 2012-09-07 10:13:22 PDT
Why does Chromium use dashboardRegionsChanged? That's clearly a Dashboard only thing. If it's now used for more than Dashboard, the function should be renamed.
Jian Li
Comment 4 2012-10-16 14:46:53 PDT
This is not longer a problem since now by default the frameless window is not draggable. Also, now Chromium is not using dashboardRegionsChanged.
Note You need to log in before you can comment on or make changes to this bug.