Bug 43928

Summary:	Simple Konqueror Patch - Fixes broken javascript cookies test in 3.2.0 (Including Washington Post)
Product:	Gentoo Linux	Reporter:	MrZaius <cragos>
Component:	[OLD] KDE	Assignee:	Gentoo KDE team <kde>
Status:	RESOLVED UPSTREAM
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://bugs.kde.org/show_bug.cgi?id=72941
Whiteboard:
Package list:		Runtime testing required:	---

Description MrZaius 2004-03-06 17:23:08 UTC

KDE bug 72941 prevents the Washington Post and several other sites that use javascript to test whether or not the browser is accepting cookies from loading.  The included patch fixes html_documentimpl.cpp in konqueror.

Reproducible: Always
Steps to Reproduce:
Either use testcase in linked bug report, or:
1. Go to washingtonpost.com in konqueror
2. Follow link to an article, or away from the first or front page
3. Attempt to fill out and submit required survey

Actual Results:  
The washingtonpost.com test will generate a mistaken "your browser does not accept cookies" error, 
or some such nonsense.  It happens regardless of security settings, and even with 
washingtonpost.com and www.washingtonpost.com both set to allow all cookies in Konqueror's 
options window.

Comment 1 Caleb Tennis (RETIRED) gentoo-dev

2004-03-09 19:00:42 UTC

Seems to be fixed in 3.2.1

Comment 2 Caleb Tennis (RETIRED) gentoo-dev

2004-03-09 19:00:52 UTC

Seems to be fixed in 3.2.1

Comment 3 Philip Webb 2004-03-15 13:03:00 UTC

3.2.1 shows me the same behaviour as 3.2.0 ,
ie even when i enable all cookies & restart Konqueror,
WP continues to send a note "please enable cookies".
Mozilla-Firefox has the same problem.

Comment 4 MrZaius 2004-03-15 16:22:21 UTC

The bug does indeed persist in 3.2.1.  Checked cookie settings, and they're still set as permissive as possible, but to no end.

Comment 5 Caleb Tennis (RETIRED) gentoo-dev

2004-04-26 19:07:57 UTC

Can you let the bugs.kde.org people know, so that they know the bug persists?

Comment 6 Caleb Tennis (RETIRED) gentoo-dev

2004-05-18 16:36:13 UTC

The claim shows that the bug is fixed upstream.  If that's not the case, you need to notify the kde developers so it truly gets fixed - closing as upstream.