@ nataliyaf: Thanks for filing the issue, request you to please differentiate the expected and the current output. This will help us to triage the issue further. Also can you please let us know on which OS the issue is being observed.

Thanks.!

@ranjitkan@chromium.org OS: Windows 7, Windows 10 
For the expected vs actual result please see http://www.geocities.jp/yasu0796/gpf/280528/ : screenshot marked M50 is expected, the one parked M51 is actual (this looks like regression). As stated in the bug the font should be rendered sharply, instead it is blurry. 

Attached is sample flash file (.fla) that reproduces the issue submitted by forum user and screenshot of settings used while creating: anti-aliasing is set to "use device font"  

Deleted: [H28.05.31]fonttest.fla 5.0 KB

[H28.05.31]fonttest.fla 5.0 KB Download

Deleted: [H28.05.31] Flash デバイスフォントの指定.png 23.5 KB

	[H28.05.31] Flash デバイスフォントの指定.png 23.5 KB View Download

Thank you for providing more feedback. Adding requester "ranjitkan@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

Thanks for the details provided, able to reproduce the issue and is a regression broken in M51 only on Windows. below are the bisect details for the same:

Bisect Info:
============
51.0.2670.0 - Good build
51.0.2671.0 - Bad build

Change log: https://chromium.googlesource.com/chromium/src/+log/4020b942e7d03a0ecf916922566099a78be6cb4b..a85ab8e4d88a1e32a0db232cfd946533dd49ef16

Suspecting #379595 could be the possible culprit

@fgorski : request you to please take a look into it, please help us to reassign if not with respect to your change.

Change URL: https://chromium.googlesource.com/chromium/src/+/a85ab8e4d88a1e32a0db232cfd946533dd49ef16
Review URL: https://codereview.chromium.org/1753573005

eae@, could this be your https://chromium.googlesource.com/chromium/src/+/e3fe85330f1fbad6cb02cd0c5ceb09498e50f349 as well?

 Issue 618113  has been merged into this issue.

This looks like the opposite of 615375.

Just saw this bug. This cannot be related to my code as it only affected Android.

There are a few days off from the bisect range, but this could be r379189. This changes fallback font in Blink, so:
a. If the flash file does not specify Japanese font, and
b. If the flash player asks Blink for the fallback font
this is possibility.

I don't know how flash player picks fonts at this moment, but first of all, I'd like to understand symptoms better.

I'm looking at screenshots in the comment yasu0796 made on 29th May:
https://productforums.google.com/d/msg/chrome-ja/Y7hB5h_HR2U/X_ob9GI9AAAJ

I can see the last line is rendered in different fonts, but neither look blurry to me, rather, juggy. And to me, 51 looks better.

Is this (the last line) the difference people is talking about? And people prefer 50 in this screenshot?

Searched for pages talking about fonts in Chrome in recent month, here's my understanding:
a. Fallback font was changed to Meiryo.
b. M51 does not anti-alias Meiryo in one instance.
c. When Flash does not specify Japanese font, it falls back to Meiryo in M51.
d. All fonts (all Japanese fonts?) stopped doing anti-alias in Flash.

a is an intentional change done in r379189. I found a few negative feedback, but given the impact, I think this is generally positive.

b is unclear; the reported person tweaked chrome:flags to turn off material design, which fixed the problem, then he can no longer reproduce even he turned material design back on. Something went wrong, but not reproducible.

c looks like an unintended side-effect of a.

d looks like a separate bug, maybe r379589, maybe something else.

It looks to me that, while c has some compatibility concerns, d is more issue to users.

Am I in sync?

Talked with Nataliya offline, so the largest complaints is:

d. All fonts (or all Japanese fonts? We'll confirm tomorrow) stopped doing anti-alias in Flash.

I'm not sure if/how r379589 could affect Flash rendering, and how "Use Device fonts" option in Anti-alias setting in the Flash file can affect rendering. It looks like there are Flash documents saying "When Use Device Fonts is selected: No antialias or smoothing is applied to the device font":
http://www.adobepress.com/articles/article.asp?p=433756&seqNum=5

I'll try to find Flash experts once we figure out this is only for Japanese fonts or not.

Also making this public after talking with Nataliya.

Screenshot with non-JP fonts, reproduces on non-JP fonts as well

Deleted: With non JP fonts.PNG 56.8 KB

	With non JP fonts.PNG 56.8 KB View Download

Deleted: Plus non-jp fonts (1).fla 5.2 KB

Plus non-jp fonts (1).fla 5.2 KB Download

Deleted: Plus non-jp fonts (1).html 1.2 KB

Plus non-jp fonts (1).html 1.2 KB View Download

Deleted: Plus non-jp fonts (1).swf 1.2 KB

Plus non-jp fonts (1).swf 1.2 KB Download

Moving this nonessential bug to the next milestone.

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

Nataliya, would you be able to verify this?  Issue 615375  is still open but the fix has landed in Canary, one says it's fixed and another not yet.

After update to 54.0.2840.71m, lack of anti-aliased came again.

I think this bug reverted.

#18: the additional fix in comment 29 of  issue 615375  is for 55, could you mind to confirm beta channel?

I confirmed that this bug has not occurred at 55.0.2883.28 beta.

I hope 55 will come soon. Thanks.