Did this regress recently?

Nvm - we don't seem to be overriding onConfigurationChanged in our webview shell activity:
https://cs.chromium.org/search/?q=onconfigurationchanged+file:%5Esrc/android_webview/test/shell/src/org/chromium/android_webview/shell/+package:%5Echromium$&type=cs

Alek, is there a specific reason we need this functionality?

gsennton@ 

66.0.3331.0 - good build 
66.0.3332.0 - bad build 

We can't do per CL bisect as it's happening on Samsung devices but this is the range where it's been broken = https://chromium.googlesource.com/chromium/src/+log/66.0.3331.0..66.0.3332.0?pretty=fuller&n=10000 
suspect CL: https://chromium.googlesource.com/chromium/src/+/ff0799d2f65c78efd3e0bd8f642b3b79ad04f86c


It's a regression, and we used to have a release blocker on M55 last time it didn't work, that's the reason we need this functionality  

It's probably this one: https://chromium-review.googlesource.com/850699

assigning to timvolodine@ who is a reviewer in WebView to take a look.

Remove RVG and assigning to owner of CL https://chromium-review.googlesource.com/850699

any updates on this bug? 

The assigned owner "mikhail.pozdnyakov@intel.com" is not able to receive e-mails, please re-triage.

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

This is a better URL to test on mobile:
http://fiddle.jshell.net/0hpxgr91/1/show/

Note this is the *device* orientation API, not the screen rotation thing, so nothing to do with onConfigurationChanged.

Although I don't know what's broken. I tried 67.0.3376.0 on a samsung s7, and it works just fine in webview shell.