Closed
Bug 118562
Opened 23 years ago
Closed 23 years ago
"View Page Source" fails to show source of CURRENT page
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: turnerjw2, Assigned: asa)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17-21mdk i686)
BuildID: 20011120
"View Page Source" appears to cache somewhere -- Always works the
1st time invoked, but if continuing in a CGI app which generates
HTML output, invoking "View Page Source" on SUBSEQUENT CGI-generated
pages, displays earlier (cached?) html when it should display the
html for the current page. I am a CGI developer and this is critical
to me -- I love Mozilla, but am forced to use Netscape when debugging
my CGI outputs :( (this has always worked in Netscape, but has yet
to work for me in either of the 2 versions of Mozilla I've tried).
Reproducible: Always
Steps to Reproduce:
1. Invoke a CGI script
2. do a "View Page Source".
3. Submit the CGI script (generate next page)
4. do a "View Page Source".
The html source will probably be the 1st page viewed rather
than the current one. If not, repeat steps 3 and 4 a couple of
times.
Actual Results: The html source will probably be the 1st page viewed
rather
than the current one. If not, repeat steps 3 and 4 a couple of
times.
Expected Results: I get the HTML source from the 1st page on which I did a
"View Page Source". It does not matter whether I do it from
the View menu or right-click. I am not using frames.
I should always view the latest HTML generated by the most
recent invocation of the CGI script. Works in Netscape.
If for any reason, you can't reproduce this, email me and I'll
create a simple Perl CGI/test case for you.
Jim Turner
turnerjw2@netscape.net
Comment 1•23 years ago
|
||
*** This bug has been marked as a duplicate of 55583 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•