Not just that, but in an earlier release code was shipped to set the pref for us... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		bzbarsky on Sept 3, 2019 \| parent \| context \| favorite \| on: Firefox 69.0 Released Not just that, but in an earlier release code was shipped to set the pref for users who already had the file, so that anyone who already had one of these files would not observe any behavior regressions. And yes, file I/O was the issue.

kg on Sept 3, 2019 | [–]

Yeah, I checked and it was automatically enabled for me, so no regression.

grey_earthling on Sept 4, 2019 | [–]

Thank you for doing this!

bzbarsky on Sept 4, 2019 | [–]

I can't claim credit for it; I hadn't even realized it had happened until I dug a little bit into the history while reading this thread. All I knew was that my userChrome.css was still working fine... ;)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact