A workaround for Bug 36939....

A workaround for Bug 36939.
This change just adds a boundary check to prevent |minimize_button_offset| from exceeding the frame width and to mitigate its pain. (This is not a real fix since the frame width is not equal to the offset to the minimize button of Windows. Nevertheless, it may be a good idea that a whole tab strip is always rendered inside of its parent frame.)

BUG=36939
TEST=run chrome on Win7 PC whose DPI is 144, open 20 tabs, and verify we can see a '+' (newtab) button.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=71933

[Ben Goodger (Google), 2011-01-19 15:23:36]

Good enough. The only difference is potentially a few pixels for shadow. LGTM.