a Quick Reply and Edit issue

Nothing has changed here on the server side, so it must be something closer to you, ie. your own browser and/or security software, or something at your ISP.

If you read through the recent threads in this section and the Test Forum section, you'll see a common theme since the vBulletin 3.5 upgrade a few days ago... Quick Reply & "Quick Edit" (that's what they call the new in-line post editor feature) are not working for a few people. Most have been resolved, and there is a commonality among the solutions...

Quick Reply and Quick Edit are complex Javascript functions. Quick Reply was rewitten since vBulletin 3.0, but both are subject to issues when the client system (or caching servers) either maintain an out of date copy of the Javascripts, or filter the HTTP datastream in such a way that it interferes with you getting the right and full Javascript into your browser.

Many people have found that fully clearing their browser cache and restarting their browser will fix the problem if it is a local caching issue. Some people are using web filter software, like Proxomitron or some software firewalls, scripting filter packages, and perhaps even AV with HTTP filters enabled, and they find that bypassing / excluding the filters for this site fixes the problem, and they get the full Javascript in their browser which then works properly.

I'm sure some people will be effected by their ISP or company's caching servers, where those servers have locked in an old copy of some of the Javascripts and they can't draw the new version yet. (Perhaps a browser based "Ctrl F5" might help them. I don't know.) And though we haven't seen it yet, I'm sure some issues will be related to cookie settings. Some of the control variables for these new editors are being passed in cookie variable values, I believe.

That file is present and fine on the server, and is unchanged since we installed 3.5. Actually, if it weren't, then no one could use these functions. That file is shared by all users of the site. Since all that file does is download to people's PCs and run as a local script, if it were missing on of it's key functions, everyone would see the error. When it doesn't work for some people, but does for everyone else... there's nothing wrong on this end.

I don't know which of these issues are at the root of exactly what you are seeing, but, stepping carefully through browser settings, cache & cookies settings, all proxy / filtering software configs, and so on is likely to be where you'll find the answer.