It was a bug in the internal browser framework which prevented certain https pages from being loaded correctly.
We have downgraded back to the older framework, in the latest version (0.9.11.2), and will monitor the framework fixes before upgrading again.
Thanks for the bug reports.