
Crashes should be sent automatically to Mozilla anyway.

Last time I reported bug to Mozilla it took 5 years to fix it. I do real work with this browser so it needs to work. I do not want to be a beta tester just to disable tracking features like Pocket. If this is really a case I bit pisses as I like my browser stable but configurable. What I read from review replies the about:config is reserved only for "power users" what means nighlies in Android case. This would not be a problem if about:config would be accessible as I would just re-disable it from there.

I mean that I had disabled domain autocomplete from settings but new update decides that I want this feature back.
