The following TC's do not work as expected on ChromeOS ARM with FP 26.0.0.110 M59. Adding the comment here because it is likely related to the bug filed.

http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PrintJobAPI_LargeMovie/PrintJobAPI_50Frames.html
http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PrintJobAPI_Masks/PrintAPI_TextMask.html
http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PrintJobAPI_Alpha/PrintAPI_PrintAlphaYes.html
http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PrintJobAPI_PrintArea/target_printArea.html
http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PrintJobAPI_PrintArea/LongFrame_H.html
http://ats.macromedia.com/Players/ATS/ATS9AS3/Shipping/html/Printing/PopupWindow/PrintPopUp.html

I tried it on my Pixelbook running on m64, and it has the same problem as described here.
It works fine on Chrome 65 browser running on Debian.

The link I used for the test:
http://apptest.mpluss.no/canvas/test/MPLUSS_TEST/chrometest/chrometest.html 
The Flash "PRINT" button didn't generate any even in messages on Chorme OS.

Could you take a look ihf@?

Thank you Eric for a repro case! Unfortunately it is pretty far down my priority list at the moment.

I Norway there are a lot of schools that have bought Chromebooks. All Flash-based worksheet applications are now become unavaliable. This causes a great deal of frustration on a daily bases. So, please give priority to the fixing of this bug!

We are all working hard on replacing the Flash content with HTML5, but until all this is in place, we ought to make sure that our customers will not be the ones to suffer.

I am representing five of the Norwegian schools, suffering with a lot of patience. Please do something to fix this problem - We really do not need any reason to think negative about our choice: going Google (both Works and G-Suite) - going for Chromebooks
Kind regards,
Eva

Using the page in comment #5 I bisected this to between image 9453.0.0 (good) and 9457.0.0 (bad). This gives Chrome 59.0.3065.0 (good) and Chrome 59.0.3068.1 (bad).
https://chromium.googlesource.com/chromium/src/+/a9afc02163b48dbb93c9a343630096b8f45aec71

Several printer changes. The one that sticks out is "Enable Native CUPS printing on Chrome OS."
https://chromium.googlesource.com/chromium/src/+/a9afc02163b48dbb93c9a343630096b8f45aec71

Toggling this in about:flags indeed toggles the behavior.

How is flash supposed to be calling into the printing stack?  Is this a possible bug in the pepper plugin?

No, it is not. I did try with the newest Flash on M58 CrOS image and it worked as expected.

Thanks.  I'll look into it and see what might be happening.

 Issue 757944  has been merged into this issue.

Flash uses PPAPI to print. It uses both PPB_Printing and PPP_Printing.

Customer asks if we have any update about this.

Also per #9 it might be related to "--enable-native-cups" switch, but looks like no corresponding flag available in chrome OS for that to try as workaround, right?

--disable-native-cups got removed in r488695 about ~10 months ago. If someone still has Chrome 59 on their ChromeOS device, they may be able to flip that flag.

Hi team, just checking if there are any new updates? Thank you.

I work at a school in Haderslev, Denmark, and both students and teachers now have Chromebooks and we have the same bug problems, which is hugely annoying. It should have been fixed for a long time. When does something happen????????

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.