If a page result from a POST and have some scripts inside, it's impossible to debug it because the debugger reload the page (not very good) without the form data (wrong...) So you obtain an error page or not the same script that you want to debug. (See in Mozilla build 2002072204 and previous)
I'm not sure the real problem (that venkman reloads the source) will get fixed anytime soon, but you can work around the problem with the "pretty print" option. With pretty print enabled, you can debug functions without having access to the actual source text. See <http://www.hacksrus.com/~ginda/venkman/faq/venkman-faq.html#2.13>.
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's impossible to get the real source that was used in the general case for all sorts of complicated reasons. If the cache does still have a copy of the source for a URL, we may be able to load that, but I don't know if there would be any way to guarantee it was generated from the same POSTDATA (I doubt we could determine the POSTDATA that the user cared about).
OS: Linux → All
Hardware: PC → All
view source can do it...
View Source knows which session history entry it's dealing with, and hence has the associated postdata and/or cache entry; the debugger only sees a list of URIs for loaded scripts/pages. That's where the problem is.
I think that the best way to work around the problem is, if possible, to detach the script in an independant js file declared with property 'src=' of tag <script>. No problem to debug these js components.
You need to log in before you can comment on or make changes to this bug.