summaryrefslogtreecommitdiffstats
path: root/url/url_parse.h
diff options
context:
space:
mode:
authordharcourt@chromium.org <dharcourt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-23 06:58:36 +0000
committerdharcourt@chromium.org <dharcourt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-23 06:58:36 +0000
commitbf911527b7e20eecef2f24ab3bfe05b723f585c1 (patch)
treeb7c7f09673d3edef6b6499e481b578dda0983511 /url/url_parse.h
parent66fca5bc1081633039dc13a35f302affb4ed7ea7 (diff)
downloadchromium_src-bf911527b7e20eecef2f24ab3bfe05b723f585c1.zip
chromium_src-bf911527b7e20eecef2f24ab3bfe05b723f585c1.tar.gz
chromium_src-bf911527b7e20eecef2f24ab3bfe05b723f585c1.tar.bz2
Fixed app window size updates for app reloads on Mac OS.
Chrome application windows were sometimes being resized incorrectly on Mac OS after application reloads. This happened for windows whose size was the maximum allowed and whose maximum size was changed by the reload. This did not occur for the same changes on Chrome OS or Linux. The source of the problem was that NativeAppWindowCocoa incorrectly assumed a window was maximized simply because its size was equal to its maximum size (this is the logic in the NSWindow isZoomed method which NativeAppWindowCocoa used). When that maximum size was then changed, the window was getting resized to the new maximum size when it shouldn't have been. The fix was to have NativeAppWindowCocoa maintain its own state for whether it had been maximized or not. TBR=tapted@chromium.org BUG=161095 Review URL: https://codereview.chromium.org/15648005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201722 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'url/url_parse.h')
0 files changed, 0 insertions, 0 deletions