Content served as "application/vnd.wap.xhtml+xml" won’t render
Bug #1289020 reported by
Bill Filler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Confirmed
|
Low
|
Unassigned | ||
webbrowser-app |
Invalid
|
Undecided
|
Unassigned |
Bug Description
latest from phablet-team/ppa on Nexus 4:
-try to load facebook.com or m.facebook.com
- the url field shows full orange, with crossed-circle icon
- the page never loads and is never displayed
Could be because of UA string?
To post a comment you must log in.
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: