Last modified: 2014-02-12 23:53:03 UTC
I don't think the results of shouldDisplayMobileView can change during a request. It would be helpful if it were cached/memoized so other extensions could call it without performance concerns. This basically just means that before returning, it stores the result in the instance (which is supposed to be used as a singleton), and uses it when called (if available).
https://gerrit.wikimedia.org/r/39617
Looks good!
This will likely go into production during our next deployment on 12/26
Great, now I can fix bug 43255 worry-free.