| Summary: | Javascript detection of Cookies doesn't work | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Shaya Potter <spotter> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | washingtonpost.com's cookie-testing code | ||
|
Description
Shaya Potter
2004-02-09 21:45:06 UTC
more specific comments.
what hertz is doing is
<script language="JavaScript">
document.cookie="cookieson=yes";
if (document.cookie.indexOf("cookieson=yes") == -1)
{
document.location="/cookiemessage.html";
}
and I get redirected to that page, making the site unusable.
Should be fixed in 3.2 final *** This bug has been marked as a duplicate of 72941 *** Created attachment 6442 [details]
washingtonpost.com's cookie-testing code
I'm suddenly seeing this problem again at washingtonpost.com. I've attached what I believe to be the problem code. |