Closed ghost closed 6 years ago
One WE I had collided with NeatURL. Unfortunatelly I don't remember which one (obviously it was not very important one and easy to ditch). Disable all addons except NeatURL and test again. Enable half of them and test again. ... ... etc., I know that you know what I mean. :)
Cheers
Thanks @crssi ... yep, I know what you mean :=) i'm still trying to find the culprit in the soft way before considering as a last resort the hard way, the halves by halves way.
I'm not sure the culprit is that of an extension's incompatibility. At this time I'm checklisting Firefox settings, many of which I've tweaked. But it may be simply another extension getting on its way. That's why I started this thread with the idea any similar experience could be shared to help me on this issue.
Thanks!
@mazesy Which addons do you have installed? Could you give me a complete list?
Hi @Smile4ever , detailed .htm list available at https://mon-partage.fr/f/tucsiEDw/ Fast list as follows:
Awesome RSS Bookmark search plus 2 Bookmarklets context menu Clear Storage Button ClearURLs Close All Tabs Button Close Tab Context Menu ContextSearch web-ext Lite Cookie AutoDelete Copy page title and url Decentraleyes Feedbro Foxy Gestures Fullscreen Maps HistoryBlock HTTPS Everywhere In-Site Bookmark In-Site History IP finder mozlz4-edit Page Saver WE Redirector Right Links WE Scroll Up Folder ScrollAnywhere Search Engines Helper SiteDelta Watch Skip Redirect Smart Referer Stylus Switch To Previous Active Tab Tab Mix WebExtension uBlock Origin Viewhance Violentmonkey window.opener be gone
The last one, window.opener be gone, is not on AMO, installed from here. That one at least is not the culprit.
Thanks. My opinion (which is why I hesitate to proceed with a systematic testing of all extensions) is that the culprit is rather in my Firefox settings. I may be wrong of course.
Is it not simpler to just disable all addons, except NeatURL, and you would get an answer in a minute? If still doesn't work the its the prefs.
If it is the pref the I would try as first privacy.firstparty.isolate
set to false.
If it is the pref the I would try as first privacy.firstparty.isolate set to false.
I've tried setting it to false, didn't change anything.
So here's what I've just tested: a new totally clean profile, which included:
1- Copying back all FF system add-ons to their default location (Program Files\Mozilla Firefox\browser\features) because I run Firefox free of all system add-ons (removed from their folder). 2- Removed autoconfig files and Policy templates (both Firefox-wide) 3- Reset system default dns (I use dnscrypt-proxy with blocklists)
From there, started Firefox from Firefox Profile Manager with the new profile, went over to AMO to install Neat URL and guess what : same issue as described above.
This is weird, one step beyond, the twilight zone.
EDIT : the only element which is not Firefox-native because removed is this: When I install Firefox, Windows Firewall shows two Firefox rules which I remove (required I believe for WeRTC which I disable):
This is the only exception to a 100% normal Firefox install in the scheme of the above dummy new profile I created above. But I cannot imagine its relationship to my issue...
@mazesy Could you follow these steps and answer the questions marked in bold?
Test scenario 1
Test scenario 2
Also let me know what happens in test scenario 1 and test scenario 2.
Do you see the Neat URL icon in your browser toolbar?
@Smile4ever many thanks for committing yourself to this issue I had opened. Given the fact I am apparently the only user who experiences the issue (no one else here confirmed) I presume it's all in an area between the extension, the browser and maybe even my WIn7 configuration.
From there on, I have to decline your detailed testing procedures as I really don't have the time for Test (2) and that I'm really not looking forwards to installing Firefox Nightly over Firefox 60 stable. I'd have to reinstall FF60, paste back backed-up FF60 profile ... I could do it but frankly, another time maybe.
It's odd that no one but me seems to have experienced this issue. This contributes to my laziness of not carrying on -- now anyway -- your detailed tests.
Moreover I'm far from being a techie. Maybe a skilled user could devote himself but it wouldn't have any sense without my issue here described, experienced.
Thanks again :=)
I'll close the issue since I opened it and am not carrying it on.
You can install Nightly alongside FF 60, it doesn't replace it.
Feel free to reopen in case you want to continue testing.
Feel free to reopen in case you want to continue testing.
Got it, thanks @Smile4ever
Neat URL (all versions, latest 4.1.3 included) / Firefox 60.0.1 (x64) / Windows 7 (x64)
It's obviously not the extension's issue since so many users run it flawlessly. But here totally impossible to get it doing its job. I have 37 extensions, no problem; I run the ClearUrls extension: no issue.
Mystery. This explains my thread : hoping to get a hint on what the culprit can possibly be. I'd prefer to switch from ClearUrls to Neat URL because of its ability to have my own filters added.
As it is now, Neat URL gets installed, options are correctly registered by Firefox ... but on the ground: nothing works, urls when applicable are left untouched. First test is always Google and Neat URL's filters (many of which apply to Google) are simply not applied, the url resulting from a quest is untouched and Neat URL's badge doesn't appear of course.
Help, advice appreciated - Thanks.