At 6:46 Uhr -0700 20.06.2008, Stuart Morgan wrote:
>On Jun 20, 2008, at 3:40 AM, Hauke Fath wrote:
>
>> (3) Trunk removed the dialog to temporarily or permanently accept a
>> server certificate and grew
>> <http://www.spg.tu-darmstadt.de/~hf/camino/ssl-cert-botch/cert-error.tiff
>> >
>> instead, which refers the user to "advanced encryption settings" as a
>> way out. They do not exist on Camino.
>
>The Mozilla core made that change. We didn't control the decision, the
>timing, or the wording they used on the error page.
I understand that. Still, there is Bug 402459, opened six months ago.
How hard can it be to see the whole picture, and make sure that
functionality is not lost?
>> Comments, insights?
>
>That's a blocker for shipping 2.0a1, and I've been working on it as I
>have time.
The Camino bug 383988 doesn't block anything, or am I misreading bugzilla?
>What more are you looking for beyond it being the highest
>priority bug for us to fix before we can ship an alpha?
That's good to hear. Still, these targets can be moved, and have been
in the past...
>We have a distinction between releases and nightly development builds
>for a reason;
As a long-time user of Mozillas, and other open source software, I am
aware of that distinction.
>if you find missing or broken functionality
>unacceptable, you should be using a stable release, which doesn't have
>this problem.
I collected the information from bugzilla because I figured that
there were a lot of loose ends, and the whole picture - Camino being
unusable with custom root certificates because of a combination of
bugs - might not be perceived.
If that meant stepping on your toes, I apologize.
hauke
--
The ASCII Ribbon Campaign Hauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
Respect for open standards Ruf +49-6151-16-3281
_______________________________________________
Camino mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/camino
