Closed Bug 2051798 Opened 2 months ago Closed 1 month ago

Browser takes a couple of seconds before showing up after Felt disappeared

Categories

(Enterprise Products :: Firefox, task)

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gerard-majax, Unassigned)

References

(Blocks 1 open bug)

Details

It is to be noted that after bug 2049134 lands, encryption mechanism means the browser may take a couple of seconds (~5s according to my measurements on debug build on a beefy HX370 laptop) after Felt's window is hidden, before showing up.

This may provide a weird UX. From profiling, this is unfortunately on purpose because of the 800k iterations of PBKDF2 to ensure security. Assuming there is no option to make those iterations faster, and assuming we want to stick to 800k iterations, it's likely we would like some interstitial screen in Felt after login is successfull and before the browser is visible.

Right now the call to hide FELT window is https://searchfox.org/enterprise-main/rev/8939fd0f0e3e194c9fb8a34735bdf8f77396fc0c/toolkit/components/felt/content/FeltProcessParent.sys.mjs#458-462 at the beginning of the Firefox startup. We may want to move that later in the chain, like e.g., when we do Services.felt.sendReady() ?

This would warrant UX requirement, as well.

We may want to wait a bit on QA's feedback when they assert the encryption feature to weight opinions on whether this is required or not.

on debug build

Can we check on an opt build? 500ms vs 5s is a different ballpark and change how serious this is.

Flags: needinfo?(lissyx+mozillians)

yes, i just lack time to verify on opt, that's why since QA is going to exercize it soon ... :)

Flags: needinfo?(lissyx+mozillians)

QA could not confirm a real issue here, so let's close

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.