at least the WCAP provider may currently trigger warning dialogs when
getting its session (e.g. an insecure connection, login prompt...). Due
to the fact that all calendar instances / providers are called very
early on startup (I assume by the alarm service), this happens even
before the app window is present.
IMO this should be improved: at least the app window should be present
before calling on providers, so the user has some context where those
dialogs come from...
What do you think?
regards,
-Daniel
Agreed. This is also a problem with our authentication prompts, as we
pass them "null" rather than a parent window to spawn from. I was seeing
issues during CalConnect where the auth prompt was up before the app
window, but was hidden behind it, so you had no idea what was keeping
stuff frozen unless you cycled through the windows.
-lilmatt
I think dialogs without an application in the background should only be
shown, if the application start-up was impossible and the warning shows
the reason why this happens.
I had those warnings from the WCAP provider on my screen yesterday.
Every n minutes I got a new one, even when the last one still was on my
screen. So when I came back from a meeting, I had around 10 warning
dialogs on the screen. I think this happened because I use the
hibernating feature of my Operating System. I will check this on Monday.
Regards,
Frank
Daniel Boelzle schrieb:
another problem I am facing is that an automatic proxy configuration
file specified in TB's connection settings seems to be evaluated too
late on startup. IMO another reason to trigger the providers later in
the startup process.
regards,
-Daniel
Could this be the cause for / caused by
https://bugzilla.mozilla.org/show_bug.cgi?id=338527 ?
/Stefan