Closed
Bug 144161
Opened 24 years ago
Closed 24 years ago
No longer accumulate points at iWon
Categories
(Core :: Networking: Cookies, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.0
People
(Reporter: bugzilla, Assigned: morse)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0+)
Gecko/20020512
BuildID: 20020512
I've been using iWon for a long time. It accumulates points for you based on
viewing certain pages. It's all done with JavaScript.
Recent builds don't accumulate points for anything other than the initial visit.
The older build of Mozilla I use at home does, so I doubt it's a change at
their end.
This will be hard to test without having an account there.
Reproducible: Always
Steps to Reproduce:
1. Go to iwon.com and get an account.
2. Visit the page as a registered user. You'll accumulate 5 points.
3. Click on a news article. You should get 5 more points, but you won't.
4. Click back to return to the main page. You should get 5 more points, but you
don't.
5. Open another browser window and go to iwon.com. You'll get 5 points, but
won't get any more in that window.
Actual Results: Any browser window only accumulates 5 points.
Expected Results: Each window should score points as indicated on the links.
It worked until a few weeks ago. I believe it worked in 1.0RC1.
Comment 1•24 years ago
|
||
Browser, not engine. Sounds like it might be a cookies issue.
Reassigning to Cookies component for further triage -
Assignee: rogerl → morse
Component: JavaScript Engine → Cookies
QA Contact: pschwartau → tever
| Assignee | ||
Comment 2•24 years ago
|
||
Is your cookie acceptance pref set to originating-server-only? If so, try
changing that to accept-all and let me know if that makes a difference.
Comment 3•24 years ago
|
||
Compare bug 139072,
"Cookie policy changed between beta and RC1"
That was also filed by a user of http://www.iwon.com/
| Assignee | ||
Comment 4•24 years ago
|
||
Although the symptoms are different, the patch just posted to bug 137079 will
probably fix this bug as well. Can someone who can reproduce this bug please
apply that patch and see if it takes care of this problem.
| Assignee | ||
Updated•24 years ago
|
Keywords: mozilla1.0,
nsbeta1
Target Milestone: --- → mozilla1.0
| Reporter | ||
Comment 5•24 years ago
|
||
Seems to be corrected in 2002051503 build.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 6•24 years ago
|
||
Not fixed on branch
Status: RESOLVED → UNCONFIRMED
Depends on: 137079
Keywords: mozilla1.0,
nsbeta1
Resolution: FIXED → ---
| Assignee | ||
Comment 7•24 years ago
|
||
Being marked fixed since the patch for 137079 is checked in on trunk. However
it is not yet fixed on the branch.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•24 years ago
|
Keywords: fixed1.0.0
You need to log in
before you can comment on or make changes to this bug.
Description
•