Given the screenshot you showed, I think you should get 10 px, not 8.

I agree this still isn't a whole lot of room.  The design assumption is that people will grab to the side of the tabs, and the new design ensures there will always be at least 50 px of horizontal space between the new tab button and the caption buttons.  This sort of horizontal affordance is the only affordance provided by e.g. Edge/Firefox (though Firefox supplies it at both ends), as their tabs go to the top of the titlebar.  In user testing, most users tried to drag from beside the tabs rather than above, lending credence to the idea that this kind of affordance is sufficient.

Personally, I'm sympathetic; I'm a drag-from-above person, and even 10 px is a reasonably small target to hit, although Windows typically gives only 8 px affordances for resizing (and they used to be 4 px years ago).  I'd like this to be taller, but I lost the battle on this one.

Working as intended -> WontFix

It's definitely 8px, and on 69, the active tab only has 4px between the top of the tab handle and the window resize hit target.

You're right about other browsers. I think the MD refresh makes the problem more insidious because you can't tell what the extent of the tab handle is, for inactive tabs, until you're already hovering your mouse over it.

Thanks for the rationale and WAI note.

Attached is a diagram of how the hit targets should be working.  The top (bluish) region is resize, and is 5 px high.  The next (brownish) region is drag, and is 10 px high.  The window drag area should extens into the background tab top until it leaves 1 px of gap between it and the top of the separator line we draw between background tabs.

Deleted: drag.png 3.1 KB

	drag.png 3.1 KB View Download

That's accurate on M69.

On M70, the brownish region is 8px high. The visual top of the tabs is actually 4px lower, but the window drag area starts exactly above the top of the tabs, instead of starting 6px below by the separator line. So M70's drag hit target for inactive tabs is 2px smaller.

Just clarifying to verify that 8px is WAI :-)

This is all on a Windows 10 desktop with no flags and no touchscreen.

Try again on today's canary.  I think you're describing behavior that was present for day or two, buggily :)

Doh!

> >dir "%LOCALAPPDATA%\Google\Chrome SxS\Application"
> 08/21/2018  02:43 PM    <DIR>          70.0.3529.3

well played.