It seems to be due to the UA string indeed. Testing on my desktop, with the default UA string (which gets a "Tablet" token, that’s a separate bug in itself), facebook.com renders correctly. If I hardcode the form factor token to "Mobile", I’m seeing the issue described here.
Here’s some interesting information I’m getting on the console when this happens:
[0307/100830:ERROR:power_save_blocker_ozone.cc(29)] Not implemented reached in content::PowerSaveBlockerImpl::PowerSaveBlockerImpl(content::PowerSaveBlocker::PowerSaveBlockerType, const string&)
[0307/100830:ERROR:power_save_blocker_ozone.cc(32)] Not implemented reached in virtual content::PowerSaveBlockerImpl::~PowerSaveBlockerImpl()
It seems to be due to the UA string indeed. Testing on my desktop, with the default UA string (which gets a "Tablet" token, that’s a separate bug in itself), facebook.com renders correctly. If I hardcode the form factor token to "Mobile", I’m seeing the issue described here.
Here’s some interesting information I’m getting on the console when this happens:
[0307/100830: ERROR:power_ save_blocker_ ozone.cc( 29)] Not implemented reached in content: :PowerSaveBlock erImpl: :PowerSaveBlock erImpl( content: :PowerSaveBlock er::PowerSaveBl ockerType, const string&) ERROR:power_ save_blocker_ ozone.cc( 32)] Not implemented reached in virtual content: :PowerSaveBlock erImpl: :~PowerSaveBloc kerImpl( )
[0307/100830: