hi,
anonym wrote (03 May 2013 13:37:39 GMT) :
>>>> intigeri wrote:
>>>>> I had a quick look, and it seems that some (36) of the prefs we set in
>>>>> /etc/iceweasel/pref/iceweasel.js are not applied. I haven't checked if
>>>>> this is a regression against current devel or stable branches.
>>>>>
>>>>> I think we should just move all of our iceweasel.js prefs to
>>>>> user_pref() set in /etc/iceweasel/profile/user.js, and be done with
>>>>> it. It should work. Only drawback is that it makes it harder for users
>>>>> to change their config, but IMHO this is rather a feature than a bug.
>>>>>
>>>>> If nobody objects, I'll do that, quickly test it, and merge for RC1
>>>>> early tomorrow.
>>>
>>>> I don't object. I guess this means I'm not gonna do the merge then.
>>>> Well, I'll be around here pretty early tomorrow as well and help out
>>>> with tests and review.
> .. and no fix was found for this, but it's not worse then the current
> state of devel, so I have merged the feature/torbrowser git branch (and
> the accompanying APT suite) into devel.
The idea is to ship 0.18~rc1 with this regression documented as a know
issue, and I (or someone else) will work on a fix before final 0.18.
Volunteers, please come talk to me, as I've already tried quite some
potential solutions.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
