(In reply to comment #151)
> Actually, that is not reasonable. Mozilla can't be expected to ensure complete
> functionality of thousands of 3rd party extensions. In this case, the
> Delicious extension developers need to be made aware of the issue so they can
> fix the bug on their end.
I completely agree with you. It's impossible do correct communities addon's, but I think that Mozilla can try to make architectural modifications in Firefox to protect against these problems.
The fact is: addon developpers are going to make errors. It's natural. But I think that it's unacceptable that Firefox crash because of these errors. Can you understand me?
(In reply to comment #151)
> Actually, that is not reasonable. Mozilla can't be expected to ensure complete
> functionality of thousands of 3rd party extensions. In this case, the
> Delicious extension developers need to be made aware of the issue so they can
> fix the bug on their end.
I completely agree with you. It's impossible do correct communities addon's, but I think that Mozilla can try to make architectural modifications in Firefox to protect against these problems.
The fact is: addon developpers are going to make errors. It's natural. But I think that it's unacceptable that Firefox crash because of these errors. Can you understand me?
Thank for you answer.