[sugar] Preparing for the feature freeze

[Marco Pesenti Gritti]

We probably found a way to just hook up the firefox dialogs, there are
some missing bits but it will probably be easier than writing our own
certificate manager.

You can try it out manually btw by opening this url in a *separate*
browser instance:

chrome://pippki/content/exceptionDialog.xul

Marco

On Thu, Jun 5, 2008 at 10:20 AM, Marco Pesenti Gritti
<mpgritti at gmail.com> wrote:
> There is a good chance that this is not be possible without patching
> xulrunner, which would make me **really** nervous. What you are
> describing is the old firefox UI, and I *think* they took out the
> hooks to do that in xulrunner 1.9.
>
> Michael, is the target for this feature only G1G1?
>
> I think Peru run into this for web mail but I'm not convinced that
> providing UI to bypass certificates is the right solution there. Kids
> will be confused, especially if we provide a firefox 3.0 like UI
> (which seem intentionally designed to make it difficult to accept a
> custom/invalid certificate).
>
> Marco
>
> On Thu, Jun 5, 2008 at 7:12 AM, Eben Eliason <eben.eliason at gmail.com> wrote:
>> On Thu, Jun 5, 2008 at 12:36 AM, Michael Stone <michael at laptop.org> wrote:
>>> On Tue, Jun 03, 2008 at 11:03:44AM +0200, Marco Pesenti Gritti wrote:
>>>> * Browser bookmarks and autocompletion. - priority 3
>>>
>>> I'd really like to see some progress on #542/#5534 (deal with
>>> non-standard SSL certificate authorities). This is going to become a
>>> bigger and bigger stumbling block the longer we wait. Surely we could
>>> manage some sort of 'accept this cert' button? (Keep in mind the
>>> possibility of another G1G1 coming our way in the foreseeable future.)
>>
>> I think that a non-modal alert (akin to those used for downloads)
>> would suffice.  Toss up buttons for "view" "cancel" and "accept", with
>> the first of these presenting a modal alert with the detailed
>> certificate information, and we'd be set.
>>
>> - Eben
>>
>