Only delay/wait for managed storage once on browser extension startup

[twschiller]

Only delay/wait for managed storage once on browser extension startup

[fungairino]

An example of a place where this latency is impacting the app:

pixiebrix-extension/src/telemetry/performance.ts

Line 51 in c50ddca

const baseUrl = await getBaseURL();

Because it takes 4.5 seconds to check for the service url, the datadog rum library isnt initialized fast enough to cover the initial API calls to the service.

[fregante]

What's in the managed storage? Can it always just be initialized later? i.e. just open the defaults/localStorage first and then update them once the managed storage is received, via hook if it affects a react app.

I don't know the ratio of users on/off managed storage, but this negatively affects users who are not on it (1s-4s if managed; full 4.5s if not managed)

[twschiller]

What's in the managed storage? Can it always just be initialized later?

See keys here:

pixiebrix-extension/static/managedStorageSchema.json

Line 4 in 22bc0cc

"managedOrganizationId": {

Unfortunately, we need managed storage because it's used to enforce branding and restrictions. I think the adjustment described in the implementation approaches will solve most of the problem. There will still be a 4.5s delay on initial startup, but that's generally not noticeable anyway because: 1) on install from CWS, it's unclear when the download finished vs. when the extension starts up, 2) on fresh browser profile startup there's generally other tabs/extensions popping up

The long-term solution will be: w3c/webextensions#547