Windows font rendering has generally gotten worse in Chromium

[njx]

Due to Chromium bug #146407, font rendering has gotten significantly worse on Windows. (Read the discussion in #4554 first -- it clarifies some issues that are muddled in the Chromium bug thread.) We have some workarounds in place, but in general it seems like we should push on getting the Chromium bug fixed.

[njx]

Marking tracking and needs review. We might want to see if we can ping the Chromium team via the usual channels, or see if the TypeKit team is interested in helping us push this.

[pthiess]

@njx medium priority

[JeffryBooher]

FBNC @njx. I wonder if the changes that Peter made are good enough or should we continue to pursue a chromium fix.

[njx]

Reassigning to @peterflynn to assess since he's been most sensitive to the rendering issues on Windows. Peter--please close or comment :)

[peterflynn]

Yeah, it looks good now but only because we've basically stopped using "SourceSansPro-Light" (@font-weight-light) everywhere in the UI. If we ever wanted to use it again, same bug would still exist. @larz0 / @njx you think that's good enough to close this?

[peterflynn]

And actually if you turn on HTML menus or run Brackets in-browser, you can see how ugly our one remaining usage of Light still looks -- the menu bar titles are almost entirely illegible. But we can restyle that too, of course.