<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: Microsoft Windows [Version 10.0.19041.329]
PowerToys version: v0.19.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones"><pre class="notranslate"><code class="notranslate">Windows build number: Microsoft Windows [Version 10.0.19041.329]
PowerToys version: v0.19.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto">Drag the toolbar in windows so that it runs across the top of the screen (Apple style) :-D</p>
<p dir="auto">Set up your custom zone areas and save them</p>
<p dir="auto">Try Shift dragging a window and you will see the zones have shifted up to the top of the screen, leaving the height of your original toolbar below and causing all of your snapped window tops to sit behind the windows toolbar.</p>
<p dir="auto">This just started happening as of the latest version. Oddly, when defining the zones they are appropriately placed.</p>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">Zones should stay where they are defined, not align to the top edge of the screen behind the toolbar.</p>
<h1 dir="auto">Actual behavior</h1>

<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/58667283/86519498-f2bd6f80-be00-11ea-8eb2-880b7af37833.jpg"><img src="https://user-images.githubusercontent.com/58667283/86519498-f2bd6f80-be00-11ea-8eb2-880b7af37833.jpg" alt="Annotation 2020-07-04 141416" style="max-width: 100%;"></a></p>
<p dir="auto">Here you see they are properly placed.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/58667283/86519503-fd780480-be00-11ea-8989-6b2e72375e86.jpg"><img src="https://user-images.githubusercontent.com/58667283/86519503-fd780480-be00-11ea-8989-6b2e72375e86.jpg" alt="Annotation 2020-07-04 141420" style="max-width: 100%;"></a><br>
Holding shift gives you these translated regions.</p>
<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: 10.0.18363.900
PowerToys version: 0.19.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones
Monitor(s): 2 side-by-side 4K monitors (one set to display scaling 100% and the other to 125%)"><pre class="notranslate"><code class="notranslate">Windows build number: 10.0.18363.900
PowerToys version: 0.19.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones
Monitor(s): 2 side-by-side 4K monitors (one set to display scaling 100% and the other to 125%)
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<ul dir="auto">
<li>Set Windows taskbar location to <em>Top</em></li>
<li>Snap a window to a FancyZone (2 priority grid zones in my case)</li>
</ul>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">The window should snap to the <em>full-height</em> of the FancyZone <em>below</em>  the task bar</p>
<h1 dir="auto">Actual behavior</h1>
<ul dir="auto">
<li>The window snaps <em>behind</em> the task bar (as shown with the green arrows)</li>
<li>The window leaves a <em>gap</em> underneath each window (as shown with the red arrows), which exposes the desktop background underneath</li>
</ul>
<h1 dir="auto">Screenshots</h1>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/25905330/86352863-c110a100-bc66-11ea-95ff-f5a876357ef6.png"><img src="https://user-images.githubusercontent.com/25905330/86352863-c110a100-bc66-11ea-95ff-f5a876357ef6.png" alt="image" style="max-width: 100%;"></a></p>