You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to investigate if there are any benefits to waiting 1000 ms before showing the decrypted page. For example, it might help with loading the iframe in the background, improving the perceived performance since it might have loaded in the background instead of being shown as a white page to users.
If we don't get any benetfits from the delay, removing it would improve UX.
By removing the success status message, we could also delete some parts of the decrypt template:
success helper
some tailwind classes won't be used anymore
The unlocked icon won't be used anymore and can be removed
If we don't swap between icons, the code toggling .hidden for icons could be removed too.
All in all, this would save about 4 kb from the decrypt template.
The text was updated successfully, but these errors were encountered:
Greenheart
changed the title
Consider removing the timeout after sucessful decryption to improve UX
Consider removing the timeout after successful decryption to improve UX
Apr 27, 2021
We need to investigate if there are any benefits to waiting 1000 ms before showing the decrypted page. For example, it might help with loading the iframe in the background, improving the perceived performance since it might have loaded in the background instead of being shown as a white page to users.
If we don't get any benetfits from the delay, removing it would improve UX.
By removing the success status message, we could also delete some parts of the decrypt template:
.hidden
for icons could be removed too.All in all, this would save about 4 kb from the decrypt template.
The text was updated successfully, but these errors were encountered: