Thanks for the report! can you upgrade chrome to latest version 51.0.2704.81 and see if the issue exists? 

Hi, tried with the latest 51.0.2704.81 and the problem persists. I had wondered if it could be related to the bounding box of glyphs in different fonts (e.g. something specific to verdana). However, I have updated the link with another box which uses verdana instead and it still renders the text 'off'. Presume this is to do with half-pixels being rounded in the wrong area?

Thank you for providing more feedback. Adding requester "rsgavara@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Our rendering (at least on linux) is identical with firefox. Could you provide a screenshot showing the behavior you consider to be correct and incorrect?

Thanks!

Here is a grab from Nexus 5: Android v5 with Chrome running 40.0.2214.89 (filename chrome_40_A510.jpeg)

Also a grab from Samsung Galaxy: Android 4.4.2 with Chrome running 51.0.2704.81 (filename chrome_51_A442.jpeg

Also a grab from iPhone 6S: iOS9 running Safari (filename safari_ios9.png)

And finally a grab from Mac running desktop Chrome Version 51.0.2704.103 (filename chrome_51_desktop.png)

To be clear, both iOS and desktop Chrome render correctly, there is an equal distribution of space at the top and bottom of the glyph. Both Android screenshots render incorrectly, with either too much space above or below the glyphs.

Remember, top glyph is system default font, second is verdana.

Deleted: chrome_51_A442.jpeg 3.3 MB

	chrome_51_A442.jpeg 3.3 MB View Download

Deleted: safari_ios9.png 41.9 KB

	safari_ios9.png 41.9 KB View Download

Deleted: chrome_40_A510.jpeg 2.5 MB

	chrome_40_A510.jpeg 2.5 MB View Download

Deleted: chrome_51_desktop.png 62.3 KB

	chrome_51_desktop.png 62.3 KB View Download

Thank you for providing more feedback. Adding requester "eae@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Over to Android team for further triage.

Is there any way of tracking this in Android team land?

Sorry, I'm not sure how this ended up in my hands. I don't really work on fonts. Maybe someone from the layout team has a better idea?

Hi,

So is someone looking at this now? Is there any place other than here I can check progress?

Thanks, Ben

Reproducible on 53 on Android, the baseline position seems to be off by just a little, possible font metrics or flexbox issue.

Just to chime in and say it happens regardless of the display mechanism used (e.g. inline-block/flex/inline-flex) and therefore seems more likely to be related to font metrics rather than flexbox.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

+kojii
Let's try to make sure we fix this in NG.

This is by design unfortunately, due to the way CSS defines the baseline poitision, how each browser computes font metrics, and how fonts are built.

I'm discussing with W3C to make what you want possible. The discussion is slow but I think it started making progress recently. Thank you for your patience.