This isn't a limitation in chrome itself, which means chrome rendering has better performance for these specific operations (animations mostly).

Personally I think the chrome rendering path should always be used, and apps which want to draw under/over web content will have to deal with a frame or two of delay.

Basically, FB's engineering replaced it with a full chromium based webview and explained the reasons android webview sucks ass.