@Nikerabbit, please update your install to master at HEAD. If you still see issues then, you're welcome to comment on T8755 (the font has been rebuilt twice since July 2nd)

The Lato font is causing problems for some people, including me. See https://phabricator.wikimedia.org/T104047#1419642 for example or the screenshot below.

Will keep open in case of issues.

In T8549#124461, @fanis wrote:

@chad I hadn't upgraded, partly due to this. I'll do that soon and get back to you. Appreciate the quick responses.

While I agree that making the browser window narrower is a good work around for things like Phriction and Maniphest, it does get annoying when using Diffusion/Differential/Audit, to review code diffs. In those cases, you kind of need the horizontal space to be able to read the code easily. That means I would have to constantly resize my browser window when switching apps/context in Phabricator.

In T8549#122040, @avivey wrote:

I wouldn't say i'm "significantly opposed" to width-limited/centered content, but I don't like the notion. I want to be able to set the width of the content to whatever I want, and the browser window lets me do that on the fly.
Philosophically, deciding that I only get 800 pixels or whatever makes your (The designer's) life easier, at the expense of limiting the user's choices, and that something I dislike.

It just hit my server. Excellent final result, @chad and @epriestley! Very clean. Thanks again for taking my suggestions seriously - I have my server running on dark high contrast, and it is much easier to read than the early draft. Bravo!

Good news is swapping out to Google's hosted Lato font fixes the issue in my sandbox, but unclear why. At least it seems fixable today. Also found D13555 in the process.

@cspeckmim see T8755

Not all font packs have resolved the line height issues in some browsers.

On Firefox 39.0 on OSX (Yosemite) the Actions button on Phriction page looks like the icon is mis-aligned:

This looks WONDERFUL!!! My colleagues will feel very happy tomorrow when they see the new interface.

With full lato font and all that, this looks great on my install.. so:

This is now merged to master.

Vast majority of work is here complete.

@chad I hadn't upgraded, partly due to this. I'll do that soon and get back to you. Appreciate the quick responses.

In T8549#124445, @fanis wrote:

In T8549#124258, @chad wrote:

We definitely don't test Phabricator out to 150% size. Are people using this on a day to day basis? Is this a regression?

We also include natively a larger font in Display > Accessibility.

Although on Chrome it seems like it needs to get to 150% to appear, on Firefox I'm seeing this at 110%, the first zoom step.

In T8549#124258, @chad wrote:

We definitely don't test Phabricator out to 150% size. Are people using this on a day to day basis? Is this a regression?

We also include natively a larger font in Display > Accessibility.

The negative space on the left side at 150% does seem awkward; I'm still seeing that. I'm using phabricator at 100%, but I've used it at 110% in the past to reduce the eye strain of reading small fonts (especially code.)

I was seeing my specific problem by tweaking viewport width, not by zooming, and that problem is already fixed on this install.

We definitely don't test Phabricator out to 150% size. Are people using this on a day to day basis? Is this a regression?

In T8549#121394, @20after4 wrote:

When I scale the text size up a bit, I get a weird left margin of blank space next to the page content:

This happens in both Firefox and Chrome on ubuntu. It takes two steps of ctrl-plus in Firefox, but it takes 3 (150%) in Chrome.

Adding clear: left; to the #phabricator-standard-page-body element fixes it. Apparently something in the header (which is float:left) is slightly extending outside of the bounds of the header and pushing the page body over.

Edit: Sorry, didn't notice that @staticshock already posted the same issue. Hopefully this is still helpful as I am pretty sure that I have isolated the cause/solution. It wasn't at all obvious at first.

Oki thank for answer @chad

@tycho.tatitscheff if your install does heavily use a prototype that regressed in the redesign, it will be attended to shortly after we land to master. We're just not seeking these issues out.

In T8549#123918, @ftdysa wrote:

Chrome Version 43.0.2357.130 (64-bit) (Linux). I've tried clearing cache and it didn't resolve it.

Chrome Version 43.0.2357.130 (64-bit) (Linux). I've tried clearing cache and it didn't resolve it.

We’re not able to take bug reports on Prototype applications. You should assume that these issues will be resolved before they leave prototype phase, as most older prototypes like Ponder use old UI elements and will naturally resolve when modernized.

@chad i know it is a prototype but as it matter css design it could affect other part that are not prototype no ? Shall i not report in this thread a visual bug i see in prototype app ?

The Spaces select has not yet been designed, and looks equally bad in either master or redesign. It will be resolved with T8449 somewhat sooner-ish.

Ponder is a Prototype Application.

In Phonder the "comment link" is out of the screen:

It looks like the icons in some (maybe all font-awesomey) dropdowns are vertically misaligned.

Additionally, the font family of the preview seems to differ from the rendered result.

@chad: I'm not sure if this has been mentioned before but it seems title tags (<h1>, <h2>, ...) render differently in the preview. Compare these screenshots from Phriction: