User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150511103818 Steps to reproduce: Search random item on eBay Actual results: Listings showed without thumbnails Expected results: Listings showed with thumbnails until privacy.trackingprotection.enabled reset from true to false and then back to true. Firefox 38.0.5 on Ubuntu 14.04 x64.
Bad wording on expected results. I'd expect the listing to be showed with thumbnails but this doesn't happen until tracking protection has been set. It's been like this for 2-3 months so I'm guessing something screwed up through the Firefox upgrades.
Could you give the URL of the webpage showing up the issue?
Mozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101 Firefox/42.0 cannot reproduce with URL > Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) You should update to Fx 42 or 38.4 ESR, no?
It is probably the interaction between HTTPS anywhere and tracking protection. http://www.ebay.ca/sch/i.html?_odkw=things+and+stuff&_osacat=0&_from=R40&_trksid=m570.l1313&_nkw=things+and+stuff&_sacat=0 The resource at "https://securethumbs.ebay.com/images/g/OvsAAOSwqu9U0TrO/s-l225.jpg" was blocked because tracking protection is enabled.[Learn More] That said white listing "securethumbs.ebay.com" should be fine.
You nailed it - it's the interaction between the two. I tested with either TP or HTTPS(e) turned on - it works fine. The moment you have both on you are screwed. Should I file a bug against HTTPS Everywhere or? Where and how do you suggest whitelisting this domain? I disabled tracking protection for the whole eBay domain which does the job but it's far from a perfect solution.
They already have a bug for this https://github.com/EFForg/https-everywhere/issues/1325 They closed it as a Firefox bug
OK, but does Mozilla team accept it as a Firefox bug or it's one of those situations where things do not get fixed cause developers can't agree who screwed up :)? Please elaborate on the whitelisting suggestion, I didn't figure where or how to do this.
I'm guessing tracking protection is supposed to work by blocking things without the same base domain. And for me http://www.ebay.CA/ is clearly different from https://securethumbs.ebay.COM/. So I bet this will be closed as WONTFIX since tracking protection is working as it should. And HTTPS anywhere is working as it should by rewriting everything to https servers, which happen to be on different domains. Mozilla would have to add or tell us where to find the exception list so we could exempt domains from triggering the protection.
In case this helps: With HTTPS-Everywhere activated, ebay.com works but ebay.co.uk does not.