This issue is reproducible on latest play store builds stable , beta and dev channel

@dominickn, could you please take a look at this issue or reassign it to correct dev.

 Issue 674961  has been merged into this issue.

I'm seeing this problem on Nexus 6.
Let me update the Arch-X label.

This was fixed in https://crrev.com/2554813003, which will be in Chrome 57.

The workaround for now is to set "display": "standalone" in your manifest (rather than "display": "fullscreen"). Both will look the same for now since fullscreen falls back to standalone. We haven't actually implemented proper fullscreen (i.e. no top and bottom status bars).

Prior to the fix, we weren't preserving the orientation value if you set fullscreen instead of standalone. In Chrome 52, the "fullscreen" value was changed in place to "standalone" (so the orientation value would be remembered); however, by Chrome 54, we stopped the in-place replacement and stored "fullscreen" explicitly (in preparation for implementing fullscreen launching). That is what triggered this bug.

Thanks.

Also I'm excited to hear that you have a plan to improve fullscreen mode, probably supporting Android's Immersive Full-Screen Mode? It would be important for cardboard VR-ish apps.

Yes, the plan is to have "display": "fullscreen" launch into Android's immersive fullscreen. I had a work-in-progress a little while ago, but it wasn't quite working right (focusing an input field brought up the keyboard, which brought back the title bars, and then the bars wouldn't go away again once the keyboard was dismissed).

is it available behind a flag, or local patch only?
also, if there is a bug for tracking its progress, I love to star it.

"display": "fullscreen" support is tracked in crbug.com/581522. No uploaded progress as of yet, but we're hoping to get to this (and "display": "minimal-ui") early next year.