WebVC should not to expect to be a singleton - it should perform normal instance based setup and tear down.

To be clear, the VC shouldn't be a singleton, but the UIWebView probably should. As long as we all agree to only have one UIWebView on screen, we should restrict the app to one to limit resources (as webviews are very resource intensive).

https://github.com/luugiathuy/GTScrollNavigationBar for auto-hiding & such

In T101285#1342006, @BGerstle-WMF wrote:

WebVC should not to expect to be a singleton - it should perform normal instance based setup and tear down.

To be clear, the VC shouldn't be a singleton, but the UIWebView probably should. As long as we all agree to only have one UIWebView on screen, we should restrict the app to one to limit resources (as webviews are very resource intensive).

I don’t think that is necessary to make the web view a singleton while making the view controller disposable. That seems to add some complexity. We can just make sure we don’t present the web view controller more than one at a time in the navigation stack. (The same way we don’t present more than one settings view controller at a time).

Sure, just so long as we only have one webview.