User Agent: Mozilla/5.0 (X11; Linux i686; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 Build ID: 20160118183504 Steps to reproduce: In Seamonkey 2.40, preferences, privacy & security, I checked the Warn me when know tracking activities were detected checkbox. Actual results: No warnings are being issued when I visit web pages which when in earlier version Seamonkey 2.39, did indicate that elements in the page were trying to track and were being blocked. Expected results: A warning below the navigation toolbar is to warn about elements in the page that are meant to track and that those elements are being blocked. A request as to whether I wish to continue to block, not block, or ignore is presented. That is what Seamonkey 2.39 did with most of the pages I visit.

Site(s) to check against? https://wiki.mozilla.org/Security/Tracking_protection says its based on Safe Browsing, which is currently not working in SeaMonkey.

Hi, I never used the tracking protection feature. I checked with 2.45a1 (current trunk) and it seems to work there. Is the notification bar in the picture what's missing in 2.40? Could you look in the error console in Ctrl+Shift+J if you see error or warnings from list manager? It's likely caused by changes in the mozilla code which were fixed in bug 920951 due for 2.44. FRG

Here is an example of an entry in the error console for Seamonkey 2.39. No such Warning in Seamonkey 2.40 error console for the same page loaded. Timestamp: 04/03/2016 09:42:26 AM Warning: The resource at "http://platform.linkedin.com/in.js" was blocked because tracking protection is enabled. Source File: http://www.zamst.us/product/a2-dx.1.html Line: 0(In reply to Frank-Rainer Grahl from comment #2) > Created attachment 8737600 [details] > Clipboard.jpg > > Hi, > > I never used the tracking protection feature. I checked with 2.45a1 (current > trunk) and it seems to work there. Is the notification bar in the picture > what's missing in 2.40? > > Could you look in the error console in Ctrl+Shift+J if you see error or > warnings from list manager? > > It's likely caused by changes in the mozilla code which were fixed in bug > 920951 due for 2.44. > > FRG

see above comment 3

Apologies, unable to clear "needinfo request".

Ok I tried with the url and got the blocking bar and a log entry. So this obviously works in 2.45a1. I asked for approval to uplift the changes in bug 920951 to the current release which is 2.42 and which is hopefully out soon. I think this is all what is needed to make it work again. If you need the feature urgently you can put the changes in yourself. These are only preferences which could be added or changed using about:config. It should also work if you put all lines with a +pref in you userprofile pref.js file. +++ schnipp +++ Timestamp: 4/3/2016 7:22:14 PM Warning: The resource at "http://platform.linkedin.com/in.js" was blocked because tracking protection is enabled. Source File: http://www.zamst.us/ Line: 0

Here are the additional preferences for pref.js in your user profile. Seamonkey must not be running when you edit the file and you should make a backup first. Didn't try this.

Typo it's prefs.js not pref.js. You can find the file easily when you enter about:support and click on the profile folder icon in Windows. You are on linux so it's in in your home folder I think under .mozilla. Please remove the user_pref("urlclassifier.downloadAllowTable", "goog-downloadwhite-digest256"); on linux but I doubt it's used there anyway. FRG

(In reply to Frank-Rainer Grahl from comment #8) > Typo it's prefs.js not pref.js. You can find the file easily when you enter > about:support and click on the profile folder icon in Windows. You are on > linux so it's in in your home folder I think under .mozilla. > > Please remove the user_pref("urlclassifier.downloadAllowTable", > "goog-downloadwhite-digest256"); > > on linux but I doubt it's used there anyway. > > FRG None of those addresses exist in .mozilla/"profile"/prefs.js user_pref lines. "urlclassifier.downloadAllowTable" does not exist, "goog-downloadwhite-digest256" does not exist, "prefs.js.appends.txt" does not exist. None of the above exists in about:config either. Please download both versions Seamonkey 2.39 and 2.40 into linux O/S and find the problem in 2.40. I am not a programmer, but am willing to try an appropriate fix. However, I posted the bug so that it could be fixed in the official release. It would seem important where browser's think they are being warned, yet they are not. Obviously, anyone never having seen the warning drop down while browsing in Seamonkey 2.39 because they jumped directly to 2.40, where the security feature is not working, would not know that that is supposed to happen. So, likely no concerns, bugs, would be filed.

>> None of those addresses exist in .mozilla/"profile"/prefs.js user_pref lines. >> "urlclassifier.downloadAllowTable" does not exist, "goog-downloadwhite-digest256" >> does not exist, "prefs.js.appends.txt" does not exist. >> None of the above exists in about:config either. I know. The content of prefs.js.appends.txt does need to be added into prefs.js. Please try this first and see if it fixes the problem. >> Please download both versions Seamonkey 2.39 and 2.40 into linux O/S and find the >> problem in 2.40. It's futile. This is likely not a Linux issue. The Mozilla backend changed. The list manager which fetches the tracking and safebrowsing lists did change a lot. I thought it broke earlier but might just be in Firefox 43 which Seamonkey 2.40 is based on. Please check your web console if you see error messages. You can also back up your profile and test the pre beta 2.44 which contains the lists fix: https://archive.mozilla.org/pub/seamonkey/nightly/2016/04/2016-04-03-01-30-01-comm-aurora/

I installed 2.40 into an XP vm and exactly what I thought whould happen did. >> Zeitstempel: 03.04.2016 23:27:29 >> Fehler: TypeError: provider is undefined >> Quelldatei: resource://gre/modules/SafeBrowsing.jsm >> Zeile: 83 The lists couldn't be updated. Please try the pref fix and let me know if it fixes it so that we could mark this bug as a duplicate. It is very very very unlikely that 2.40 will be rereleased with the fix for bug 920951 in. ewong is trying hard the get the next release out of the door.

(In reply to Frank-Rainer Grahl from comment #10) > >> None of those addresses exist in .mozilla/"profile"/prefs.js user_pref lines. > >> "urlclassifier.downloadAllowTable" does not exist, "goog-downloadwhite-digest256" > >> does not exist, "prefs.js.appends.txt" does not exist. > >> None of the above exists in about:config either. > > I know. The content of prefs.js.appends.txt does need to be added into > prefs.js. Please try this first and see if it fixes the problem. > > >> Please download both versions Seamonkey 2.39 and 2.40 into linux O/S and find the > >> problem in 2.40. > > It's futile. This is likely not a Linux issue. The Mozilla backend changed. > The list manager which fetches the tracking and safebrowsing lists did > change a lot. I thought it broke earlier but might just be in Firefox 43 > which Seamonkey 2.40 is based on. Please check your web console if you see > error messages. > > You can also back up your profile and test the pre beta 2.44 which contains > the lists fix: > https://archive.mozilla.org/pub/seamonkey/nightly/2016/04/2016-04-03-01-30- > 01-comm-aurora/ I added "prefs.js.appends.txt" to the appropriate line, assuming alphabetical order. Although, not being a programmer, I don't know whether it mattered. I then rebooted and launched Seamonkey 2.40. I open about:config and see my new line with the toggle to "true". I wonder if that is what you instructed me to do. There was no visible change at the browsing level of Seamonkey 2.40, still no warnings nor indication of blocked items in the "error console".

No you need to add the actual content of the "prefs.js.appends.txt" to prefs.js not a marker/link to the txt file. about:config should then show all the preferences which are in that file.

(In reply to Frank-Rainer Grahl from comment #13) > No you need to add the actual content of the "prefs.js.appends.txt" to > prefs.js not a marker/link to the txt file. about:config should then show > all the preferences which are in that file. I appreciate your time here. I don't know how to add content of "prefs.js.appends.txt" when the file does not seem to exist anywhere in the system. It was not to be found in the "prefs.js" file. So where is it and it's contents? It was not in the about:config file either before I manually made the entry in the "prefs.js".

>> I don't know how to add content of "prefs.js.appends.txt" when the file does not seem to exist anywhere in the system. << No the file doesn't because this is just the fragment I uploaded here into this bug: https://bug1260457.bmoattachments.org/attachment.cgi?id=8737618 It is a text file. Please add all the user_pref lines in it to your prefs.js file in your mozilla profile directory. Just use copy/paste and your favorite text editor. Or send me you prefs.js file via email and I will fix it up. Shouldn't contain any confidential information.

(In reply to Frank-Rainer Grahl from comment #15) > >> > I don't know how to add content of "prefs.js.appends.txt" when the file does > not seem to exist anywhere in the system. > << > > No the file doesn't because this is just the fragment I uploaded here into > this bug: > > https://bug1260457.bmoattachments.org/attachment.cgi?id=8737618 > > It is a text file. Please add all the user_pref lines in it to your prefs.js > file in your mozilla profile directory. Just use copy/paste and your > favorite text editor. > > Or send me you prefs.js file via email and I will fix it up. Shouldn't > contain any confidential information. I copied the file. Then I made a copy of "prefs.js" and moved it to another directory and renamed it. Then I opened the original "prefs.js" and pasted those new lines at the bottom of the existing entries. Then I saved and rebooted. Then I opened a terminal and changed to the seamonkey directory and launched in safemode. I tried a couple of sites and the warning banner did not appear. Then I exited and launched again, but not in safemode, tried a couple of sites and still no action. There were some errors listed in the error console (sorry didn't save), but did not regard 'blocking'. I have reverted back to the original "prefs.js". As you mention, not being a programmer, it probably isn't very safe practice for me to download and insert individual commands that I can't understand. I will continue with Seamonkey 2.39 until a newer revision is released. I hope the team is able to figure out where it went wrong.

I tried it myself just to be sure that I do not tell others gobblygock... - Installed plain 2.40 in my Kubuntu 14.04 x86 VM under opt/seamonkey. - Started it and set tracking protection + safebrowsing options. - No tracking bar appeared. - Closed Seamonkey (this is important. Seamonkey will overwrite the prefs.js file upon exit!) - copied the lines from the append.txt into prefs.js using Kate. - restarted and tried it again. - tracking protection worked like a charm. This is clearly a duplicate of bug 920951 so I will just close it. Sorry.