Created attachment 8657566 [details] Keep until.pdf User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0 Build ID: 20150826023504 Steps to reproduce: Set <Options/Privacy/History/Use Custom Settings For History/Keep Until: ask me every time> and Favorites components in the GUI disappear from Craigslist. Both the stars to the left of the individual items as well as the Favorites count in the banner at the top of the frame. Selecting <Keep until: they expire> restores this part of the GUI display. Actual results: As above. Expected results: No part of the GUI should disappear when cookies controls are modified.
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
I observe the same problem on any site built on wix.com . Under Options->Privacy->Keep Until: If I select "they expire" or "until I close Firefox" then the site loads. If I select "ask me every time" the site fails to load and never asks for cookie permission. (In this case if fails due to cross-domain storage, which succeeds when the cookies can be set)
Confirmed same problem exists as far back as 38.0.5
Problem exists as far back as 10.0.12esr. (Site will not load at all with 3.6.28 regardless of settings) STEPS TO REPRODUCE: Create new, "clean" profile Go to "Tools -> Options -> Privacy" Change "Firefox Will:" to "use custom settings for history" Change "Keep until:" to "ask me every time" Attempt to load http://inlandms.wix.com/evgconvention (Site will not load. Console says "SecurityError: the operation is insecure") Change "Keep until:" to any other value, such as "they expire". Reload the site. (site loads successfully)
Thank you all for such detailed steps to reproduce. I am able to reproduce this on FireFox 42.0 on Windows 8.1. I will mark this bug as new and pass it up to the developers.
Status: UNCONFIRMED → NEW
Component: Untriaged → Networking: Cookies
Ever confirmed: true
Product: Firefox → Core
ask me everytime has been removed
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.