Hi folks,
I`ve developed a nss module for firefox in c/c++. In case of an error in my
module I want to show a simple error dialog.
This is want I do, the code was tested and working:
```
void ac_firefox_show_alert_dlg(const char* title, const char* text) {
const NS_ConvertASCIItoUTF16 w
Am Donnerstag, 27. Oktober 2016 10:19:44 UTC+2 schrieb Tobias Wolf:
> Hi folks,
>
> I`ve developed a nss module for firefox in c/c++. In case of an error in my
> module I want to show a simple error dialog.
>
> This is want I do, the code was tested and working:
>
> ```
> void ac_firefox_show_a
Replying to myself since nobody thought it worthwhile to reply and have
an open, honest discussion on this ML about this.
Parts of the gonk widget have already been removed; so the decision to
do it was taken was not communicated publicly. Or maybe it was never up
for discussion. I don't know whic
>
> What I think would be helpful if Mozilla does go with this plan, is that,
> first, Mozilla sets a definite end date up front for ESR 52 and, second,
> that Mozilla has puts out the message as to what and why this is happening.
> Setting an end date for support will give everyone a timeline to w
On 10/27/16 4:19 AM, Tobias Wolf wrote:
No I found out that the dialog wasn`t working in latest firefox 46.0.2 version. The call
to ```do_GetService("@mozilla.org/embedcomp/prompt-service;1")``` returns NULL.
Is this with e10s enabled? If so, is the code running in the content
process or the
Please don't use binary XPCOM. Support for binary XPCOM is being removed.
And also it's very unlikely that a modal prompt is a good UI solution from
within the network stack.
--BDS
On Thu, Oct 27, 2016 at 4:19 AM, Tobias Wolf wrote:
> Hi folks,
>
> I`ve developed a nss module for firefox in c/c
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-ser
Hey all,
Just FYI, I've landed a refactoring of how we suspend our timers in:
https://bugzilla.mozilla.org/show_bug.cgi?id=1303167
The short story is that there should be very minimal observable
difference. The main changes you might see are:
1) Previously we shifted timers during things lik
Hey Ben,
On 10/27/16 10:08 AM, Ben Kelly wrote:
The short story is that there should be very minimal observable
difference.
How do these changes compare with other browsers behavior (for the
web-observable effects)? Do you have any idea?
--
Mike Taylor
Web Compat, Mozilla
__
On Thu, Oct 27, 2016 at 1:26 PM, Mike Taylor wrote:
> On 10/27/16 10:08 AM, Ben Kelly wrote:
>
>> The short story is that there should be very minimal observable
>> difference.
>>
>
> How do these changes compare with other browsers behavior (for the
> web-observable effects)? Do you have any ide
On 10/27/16 12:48 PM, Ben Kelly wrote:
On Thu, Oct 27, 2016 at 1:26 PM, Mike Taylor mailto:mi...@mozilla.com>> wrote:
On 10/27/16 10:08 AM, Ben Kelly wrote:
The short story is that there should be very minimal observable
difference.
How do these changes compare with ot
11 matches
Mail list logo
