262119 - Problem Entering Comments under TypeKey

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[Lola Lee]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Mnenhy/0.6.0.104
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Mnenhy/0.6.0.104

Occassionally I will try to enter a comment, click submit, and get an error
message saying that I'm not signed in.  

Reproducible: Sometimes
Steps to Reproduce:
1. Click on a comments link
2. Click on sign in link which takes you to www.typekey.com, enter your uid/pwd
3. Automatically sends you back to comments view with comments text box
4. Enter text, click on post

Actual Results:  
I get this error message:

Comment Submission Error

Your comment submission failed for the following reasons:

Registration is required.

Thanks for signing in, . Now you can comment. (sign out)

(If you haven't left a comment here before, you may need to be approved by the
site owner before your comment will appear. Until then, it won't appear on the
entry. Thanks for waiting.)

URL:
Remember me? Yes No

Comments: (You may use HTML tags for style)
You are not signed in. You need to be registered to comment on this site. Sign in

Expected Results:  
It should have returned me back to the blog post with comments displaying under
it, with my comment appended at the end.

Comment 1

[Phil Ringnalda (:philor)]

The multiple conflicting messages ("thanks for signing in, you are not signed
in") sound like a template error on the site. The browser's only role in TypeKey
is to accept cookies and return them to the server: it does all the deciding
about what to tell you and whether to allow you to comment. As long as you have
JavaScript enabled, and are accepting cookies, and submit the comment before
your signin expires, the opportunities for failure are pretty much all on the
server side.

I'm marking this INVALID because there's nothing we can really do to solve a
"sometimes it doesn't work on someone else's server" problem, but if you want to
run the Live HTTP Headers extension while you comment, so you can catch Firefox
not sending a cookie when it should, don't hesitate to reopen it (though you'll
want to be careful about what you disclose with a copy/paste of the headers).