tree 903d2e5f8ba3f0677184a79052fbc1066760d4ec
parent 49f85cfd00a86de0c98c73b935696d1054903904
author Dave Tharp <dtharp@codeaurora.org> 1436562651 -0700
committer jrizzoli <joey@cyanogenmoditalia.it> 1440760546 +0200

[MDM] Refactor of restriction initialization

Original design of the MDM Restriction subclasses was
lazily initialized singletons. This worked fine for restrictions
that only altered UI elements, but in cases where the UI element
hadn't been constructed yet (so it didnt call getInstance() for
the MDM restriction), MDM messages were being lost.

The cure for this is to forget about the lazy initialization
design, and simply initialize the All the MDM subclass singletons
at browser init time (after the engine has been initialized).

Change-Id: Ibe31bd2d11df550dd0176a6a74958db250fd93bd