Closed
Bug 849948
Opened 11 years ago
Closed 7 years ago
New third party cookie policy breaks registration on dayonecenter.com
Categories
(Core :: Networking: Cookies, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: wesj, Assigned: amchung)
References
()
Details
(Whiteboard: [necko-backlog])
My wife brought this up to me and we diagnosed it, but since there's been a call to find regressions from the new cookie policy, I want to report it. dayonecenter.com uses a third party site, embedded in their main site to handle their reservations. Somewhere along the way, something depends on having third party cookies turned on for the two to talk to one another. When they don't, it fails. STR: 1.) Open http://dayonecenter.com/classes/calendar/san_francisco 2.) Click on a non-full event 3.) Click the Register now link Results: User gets a message from the page: Session terminated. Please re-login. Possible Issues * Your browser has been inactive and your session has timed-out * Session cookies are not enabled in your browser * The web address you are using is incorrect Expected: The registration page appears. My wife had no idea what to do and just switched browsers. We should at the very least provide some UI to the user when we're blocking these things.
Reporter | ||
Updated•11 years ago
|
Comment 1•11 years ago
|
||
I'm not sure if UI for this is really possible; 3rd-party cookies are used so broadly that it would basically be a persistent indicator, and then people just become blind to it. I'd want some heuristic for being able to tell if a blocked cookie was useful or not (and I've no idea how that could be done). OTOH, I see comments now and then from people responding positively to the "Firefox prevented this site from opening 19,295 pop-up windows" notification bar, so maybe there some value in exposing that.
Comment 2•11 years ago
|
||
I just had a similar experience purchasing movie tickets from cineplex.com, one of the largest Canadian theatre chains. The Cineplex site clearly identified that cookies were not enabled, but of course it was third-party cookies that were required for an embedded payment system.
Updated•8 years ago
|
Whiteboard: [necko-backlog]
Comment 4•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 5•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Assignee | ||
Comment 6•7 years ago
|
||
The website server not found, so I set this bug to invalid and close this bug.
Assignee: nobody → amchung
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•