Am Donnerstag, 27. Oktober 2016 17:04:27 UTC+2 schrieb Boris Zbarsky: > On 10/27/16 10:57 AM, Benjamin Smedberg wrote: > > And also it's very unlikely that a modal prompt is a good UI solution from > > within the network stack. > > Oh, that's a good point. NSS code has a tendency to run on random > threads from the socket threadpool, and the > "@mozilla.org/embedcomp/prompt-service;1" component is very much > mainthread-only, since it's implemented in JS. So unless you've tested > this in a debug build and it's assertion-free there, I would be _very_ > worried about code that uses that component from inside NSS. > > -Boris
Now I understand your worries about the threads. By now I cannot say if the nss module is running in content or ui process, the concept of separation between content and ui in fw are new for me. Where or how can I check for that? What would be your recommended solution for showing a dialog in nss module? I know that fw is reacting on certificate selection or even loading a nss module with a dialog, but I couldn`t find out how it is implemented. Anyhow our customer wants an error dialog in case of a failure. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
