5

1

Sometimes it just sits there with that yellow "Submitting..." note at the top of the page.

However, if I click on the List link, or search for the case number again, the changes have gone through.

Is there something I have done to my server that does this? I saw this other question Browser hangs, no page is displayed (Norton/McAfee issue)), but I don't have any of those two installed on my server. I do, however, have AVG Free 8.5 on the server, and ESET NOD32 4.0 locally, if that matters.

Does anyone else see this problem with Google Chrome as their browser?

I'm on Google Chrome 3.0.195.33.


<rant>

I understand that there has to be some barriers in a system for new users, but for me to have to go hunting for appropriate tags for a question, when the tags "chrome submit hang" should be fine is just silly. In lieu with your policy of not having fields mandatory in FogBugz, in order to ensure that there are few barriers to get the data into the system, instead of only having good data, but less of it, perhaps that should be changed or looked into?

I had to go with the "error" tag because that was basically the only one I found that came remotely close to what my problem is, so if anyone could please edit the tags on this question so they make sense, that would be nice.

</rant>

flag
Your rant is a point well-taken. This was a design decision made by the StackOverflow team, not us. I'll be talking to the StackExchange lead about this. – Rich Armstrong Nov 20 2009 at 14:44
Also, FWIW, we have not seen reports of the same error with Chrome. I'm on the exact same version as you and am a heavy, heavy user, and have no issues. – Rich Armstrong Nov 20 2009 at 15:09
@Rich Armstrong - currently experiencing these issues with Chrome 14.0.835.94. – Peter Aug 17 at 11:16
Me too on the Chrome Dev channel. Curiously no problems on the Canary builds. Weird. I suspect something in the browser cache. Firefox & (ick) IE work fine on the same machine. – CADbloke Sep 1 at 9:21

1 Answer

1

I'm using the same version of Chrome and have not had any issues at all. Are you seeing the problem with other browsers too? If not, might be worth clearing out your browser cache and see if it makes any difference.

If you are seeing the same problem in other browsers, then I'd start looking for something on the server side.

link|flag
Have not seen it with IE, have tried clearing cache, and also tried developer edition, version 4.something. – Lasse V. Karlsen Nov 20 2009 at 13:12
On the surface at least it sure sounds like a client side issue. Are you seeing any page errors being reported? Running any custom FB plugins that include JavaScript? – Ken Morse Nov 20 2009 at 13:57
The problem has gone away with newer chrome versions apparently. – Lasse V. Karlsen Mar 11 2010 at 17:28
I'm currently having these very same issues. Using Chrome 14.0.835.94. – Peter Aug 17 at 11:15
1 
I was also having this issue on Chrome 14.0.835.109 (Mac OS X 10.7.1) and was able to fix it by closing Chrome and removing the .localstorage file for our FogBugz domain in ~/Library/Application\ Support/Google/Chrome/Default/Local\ Storage/ After removing that file, I opened up Chrome and re-tried updating a case in FogBugz, and everything works fine. You could also probably use "Tools -> Clear Browsing Data", but I didn't want to clear the browsing data for all sites. – Josh Varner Aug 24 at 6:30
show 3 more comments

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.