--- Comment #85 from Ariel Constenla-Haile <> ---
(In reply to Arrigo Marchiori from comment #84)
> Hello,
> it looks like that this fix was not included in release 4.1.3? Could you
> please explain why?

Mainly because fixes from trunk are applied to the release branch only on
demand, by requesting release blocker status.

Concerning this bug, IMO it has been hijacked by different bugs, the original
one being a MacOSX report; it seems that we have no confirmation from any Mac
user that their problem was caused by an absolute path in Mozilla's

You are receiving this mail because:
You are the assignee for the issue.

Reply via email to