Closed Bug 285326 Opened 20 years ago Closed 19 years ago

SCRIPT tag outside of HTML tag section loaded only on refresh

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: whiplash, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

The URL specified has a <SCRIPT></SCRIPT> section that resides above the opening
<HTML> tag (something which I suspect is invalid).  However, the problem arises
that when that URL is entered into the Address bar, that <SCRIPT> section
doesn't appear - but if you then refresh the page, it shows up (and thus the
JavaScript popup is displayed, assuming that www.e-rewards.com is in your
Allowed list, or you have popup blocking disabled).

I suspect that the site is in error - but Firefox's behaviour should be
consistent, yes?

Reproducible: Always

Steps to Reproduce:
1. Paste http://www.e-rewards.com/pro2/7313/pbt_content.asp into the Address
bar, and hit return.
2. View the source code.
3. The <HTML> tag will be the first thing displayed.
4. Close the "view source" window and refresh the browser.
5. View the source code.
6. There will now be a <SCRIPT></SCRIPT> section before the <HTML> tag.



Expected Results:  
Page source should be the same regardless of how the page was loaded.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050227
Firefox/1.0+

FWIW, both times I saw source that looked identical to the URL downloaded with
curl.

See Bug 55583 "view-source should show original page source (use cached source)"
(Look at Bug 55583 Comment 32 for example, which I think deals with what you
are talking about), and I suggest that view-source sometimes does one thing,
and sometimes another.

Bug 40867 "Need means to reuse/reload current page without refetching from 
server" e.g. Bug 40867 Comment 48 .

I can't be more specific as I am not seeing the problem, I will just
add that there are a couple of other reports also lengthy and overlapping,
which may deal with the problem you have seen. You might want to search
Bugzilla and perhaps suggest some additions to the main Mozilla 
documentation, so that at least the observed behaviour matches the
documented behaviour

Good luck.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.