As of recently, when I first open my browser, form fields do not work for me - they're either invisible, or they're there but I can't type in them. For instance, I don't see the login fields when I visit 2p2.
For me to make them work, I have to do the following two things in no particular order:
1. Disable (and if I want, immediately re-enable) either the extension "No Resource URI Leak" or the extension "CanvasBlocker".
2. Enter my master password for unlocking my saved passwords.
I don't doubt that those extensions can break sites, but what's weird to me is that I don't have to leave them disabled to un-break form fields (so are they breaking them to begin with or not?). I have my homepage set to about
:addons#extensions, so when I open up my browser I just click Disable then Enable for one of those two extensions. Then if I go to 2p2 (whose login I have saved in FF), I don't see the login fields, but FF prompts me to enter my master pw. When I do that and refresh the page, the login fields are there. Alternatively, if I enter the master pw first and visit 2p2, I see no login fields until I disable/re-enable one of the aforementioned extensions and click refresh. If I do both of those things before visiting 2p2, the login fields are there right away without a refresh.
Also, why should entering/not my master pw affect it? I'm not just talking about login fields, but for instance the search field at Amazon. If I haven't entered my master pw, I can't type anything into Amazon's search.
I had the same set of extensions in the last FF version, and I was using a master pw then too. This issue started happening right around when I upgraded to 50.
At first I thought maybe to truly re-enable these extensions requires a restart, but that's not the case, because I checked on sites like
this one, and the extensions do what they're supposed to when I reenable sans restart. So I don't know what clicking Disable then Reenable does to suddenly make form fields work.
Can anyone think of a good explanation for all of this? My workaround is very easy, but perhaps I should report this to Mozilla nonetheless.