When posting a comment to a topic on Digg.com, you can enter the comment but when it comes to submitting the comment, nothing happens. The comment section greys out as if something is happening. Digg.com advises that comments can take up to 60 sec to post but waiting several minutes shows nothing happens. Reloading the topic page also reveals the post not reaching digg.com. The browser itself remains normal and responsive. This was duplicated on the 523.12.9 official Windows 3.0.4 build, and also with the WebKit-r27953 Nov 22nd build. Let me know if you need clarification on anything (and happy post Thanksgiving ;-). Cheers, Ben
Just to let you know, also confirmed in Mac OS X 10.4.11, Safari 3.0.4 523.12 and also in the OS X WebKit r28024 nightly.
Any errors or warnings written to the console or the JavaScript Console?
(In reply to comment #2) > Any errors or warnings written to the console or the JavaScript Console? > I'm afraid not. JavaScript console is clean as a whistle, as is the console.log (and system.log for that matter)
I created a test digg (but please don't digg it!): http://digg.com/apple/REGRESSION_Comments_do_not_get_posted_to_digg_com
This doesn't work with Safari 2.0.4 (419.3) with original WebKit on Mac OS X 10.4.11 (8S165). I strongly suspect a server-side issue, but don't have any data to prove it.
(In reply to comment #5) > I strongly suspect a server-side issue, but don't have any data to prove it. Using Wireshark to watch TCP/IP packets, clicking "Submit Comment" does nothing on Safari/WebKit, e.g., no Ajax request gets sent at all, so it's not a network/server-side issue (per se).
<rdar://problem/5619294>
Well whatever it was, it appears Digg have fixed the root cause on their site now - I just posted a comment successfully using the 523.12 release on 10.4.11 (In reply to comment #6) > (In reply to comment #5) > > I strongly suspect a server-side issue, but don't have any data to prove it. > > Using Wireshark to watch TCP/IP packets, clicking "Submit Comment" does nothing > on Safari/WebKit, e.g., no Ajax request gets sent at all, so it's not a > network/server-side issue (per se). >
Thanks, Ben!