Fix a painting bug which occurred due to the change which reduces the size of the fullscreen chrome…

Fix a painting bug which occurred due to the change which reduces the size of the fullscreen chrome window by 1 px on activation loss.

Merging to M50

We reduce the size of fullscreen windows by 1px to ensure that maximized windows on the same thread don't draw over the
taskbar. This change caused a painting problem as the compositor was not aware of the changed size. This causes the compositor
to not paint correctly when the fullscreen window is activated as the window size did not change.

Setting the compositor size correctly to the window bounds size fixes this problem. The other bug I found was when the
fullscreen window is activated, we inform the delegate about the changed client size which in turn makes it across to the
webcontents. We don't want the webcontents to get notified about these size changes. Fixed by setting the flag background_fullscreen_hack_
to false after the SetBoundsInternal call.

BUG=595666
TBR=sky

Review URL: https://codereview.chromium.org/1819633002

Cr-Commit-Position: refs/heads/master@{#382429}
(cherry picked from commit 9f060d4be347cda7aa7c0fb2a43afafbbd64e70c)

Conflicts:
	ui/views/win/hwnd_message_handler.cc

Committed: https://chromium.googlesource.com/chromium/src/+/eb3477b1f3603bcc6eede00f1ce76370f3534c56

[ananta, 2016-03-23 00:09:22]

Description was changed from

==========
Fix a painting bug which occurred due to the change which reduces the size of
the fullscreen chrome window by 1 px on activation loss.

Merging to M50

We reduce the size of fullscreen windows by 1px to ensure that maximized windows
on the same thread don't draw over the
taskbar. This change caused a painting problem as the compositor was not aware
of the changed size. This causes the compositor
to not paint correctly when the fullscreen window is activated as the window
size did not change.

Setting the compositor size correctly to the window bounds size fixes this
problem. The other bug I found was when the
fullscreen window is activated, we inform the delegate about the changed client
size which in turn makes it across to the
webcontents. We don't want the webcontents to get notified about these size
changes. Fixed by setting the flag background_fullscreen_hack_
to false after the SetBoundsInternal call.

BUG=595666

Review URL: https://codereview.chromium.org/1819633002

Cr-Commit-Position: refs/heads/master@{#382429}
(cherry picked from commit 9f060d4be347cda7aa7c0fb2a43afafbbd64e70c)

Conflicts:
	ui/views/win/hwnd_message_handler.cc
==========

to

==========
Fix a painting bug which occurred due to the change which reduces the size of
the fullscreen chrome window by 1 px on activation loss.

Merging to M50

We reduce the size of fullscreen windows by 1px to ensure that maximized windows
on the same thread don't draw over the
taskbar. This change caused a painting problem as the compositor was not aware
of the changed size. This causes the compositor
to not paint correctly when the fullscreen window is activated as the window
size did not change.

Setting the compositor size correctly to the window bounds size fixes this
problem. The other bug I found was when the
fullscreen window is activated, we inform the delegate about the changed client
size which in turn makes it across to the
webcontents. We don't want the webcontents to get notified about these size
changes. Fixed by setting the flag background_fullscreen_hack_
to false after the SetBoundsInternal call.

BUG=595666
TBR=sky

Review URL: https://codereview.chromium.org/1819633002

Cr-Commit-Position: refs/heads/master@{#382429}
(cherry picked from commit 9f060d4be347cda7aa7c0fb2a43afafbbd64e70c)

Conflicts:
	ui/views/win/hwnd_message_handler.cc
==========

[ananta, 2016-03-23 00:09:35]

ananta@chromium.org changed reviewers:
+ sky@chromium.org

[ananta, 2016-03-23 00:49:28]

Description was changed from

==========
Fix a painting bug which occurred due to the change which reduces the size of
the fullscreen chrome window by 1 px on activation loss.

Merging to M50

We reduce the size of fullscreen windows by 1px to ensure that maximized windows
on the same thread don't draw over the
taskbar. This change caused a painting problem as the compositor was not aware
of the changed size. This causes the compositor
to not paint correctly when the fullscreen window is activated as the window
size did not change.

Setting the compositor size correctly to the window bounds size fixes this
problem. The other bug I found was when the
fullscreen window is activated, we inform the delegate about the changed client
size which in turn makes it across to the
webcontents. We don't want the webcontents to get notified about these size
changes. Fixed by setting the flag background_fullscreen_hack_
to false after the SetBoundsInternal call.

BUG=595666
TBR=sky

Review URL: https://codereview.chromium.org/1819633002

Cr-Commit-Position: refs/heads/master@{#382429}
(cherry picked from commit 9f060d4be347cda7aa7c0fb2a43afafbbd64e70c)

Conflicts:
	ui/views/win/hwnd_message_handler.cc
==========

to

==========
Fix a painting bug which occurred due to the change which reduces the size of
the fullscreen chrome window by 1 px on activation loss.

Merging to M50

We reduce the size of fullscreen windows by 1px to ensure that maximized windows
on the same thread don't draw over the
taskbar. This change caused a painting problem as the compositor was not aware
of the changed size. This causes the compositor
to not paint correctly when the fullscreen window is activated as the window
size did not change.

Setting the compositor size correctly to the window bounds size fixes this
problem. The other bug I found was when the
fullscreen window is activated, we inform the delegate about the changed client
size which in turn makes it across to the
webcontents. We don't want the webcontents to get notified about these size
changes. Fixed by setting the flag background_fullscreen_hack_
to false after the SetBoundsInternal call.

BUG=595666
TBR=sky

Review URL: https://codereview.chromium.org/1819633002

Cr-Commit-Position: refs/heads/master@{#382429}
(cherry picked from commit 9f060d4be347cda7aa7c0fb2a43afafbbd64e70c)

Conflicts:
	ui/views/win/hwnd_message_handler.cc

Committed:
https://chromium.googlesource.com/chromium/src/+/eb3477b1f3603bcc6eede00f1ce7...
==========

[ananta, 2016-03-23 00:49:30]

Committed patchset #1 (id:1) manually as
eb3477b1f3603bcc6eede00f1ce76370f3534c56 (presubmit successful).