Open ara4n opened 7 years ago
Yes it should, but that will mean asynchronous decryption of events, which will probably mean hooks up to the react layer.
now the whole API is async thanks to indexeddb, does this become easier? Or have we even got it for free?
Since this has become the blocker issue for #26231 (which is a paying-customer facing usability regression), I'd like to understand what the status of this issue is, and whether we are "close" in temporal terms.
@marcusmueller I'm afraid it's unlikely to be a priority within the next few weeks.
Now, I understand that weeks are short. I feel like I'm touting my own horn here a bit hard, but if this change does not end up being a priority at some point in the medium future, that'd be a bit sad:
We have a significant UX regression, which was brought by the necessity of being safe around rust-sdk-crypto not being concurrency-safe, and the plan would be neither to fundamentally change rust-sdk nor element-web to actually work around this fact, but live with the regression that users can no longer use the same session in multiple tabs.
It's 7+ months later and this is still an issue. In my use case, I am NOT using E2E because encryption in my org is against policy. Is there a way I can have multiple tabs (rooms) open at the same time since E2E is disabled? #26231 links here.
We shouldn't be locking up the UI when encrypting/decrypting E2E; shouldn't this be in a bg worker?