Closed
Bug 333834
Opened 19 years ago
Closed 18 years ago
Contents of noscript tag do not render after a refresh
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: safemailnet-orbis, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
480 bytes,
application/zip
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
1. Assume a website with 2 pages called pageone.htm and pagetwo.htm
2. Assume the site uses JavaScript
3. Assume JavaScript has been disabled in Firefox
4. pageone.htm has the following meta tag
<meta http-equiv="Refresh" content="3; url=http://sitename.dom/pagetwo.htm"/>
5. pagetwo.htm has the following noscript tag
<noscript>
This site requires Scripting to be turned ON
Please click <a href="jsenable.htm">here</a> to resolve this issue.
</noscript>
Reproducible: Always
Steps to Reproduce:
Test as follows:
1. Go to pagetwo.htm directly. (See Actual Results)
2. Go to pageone.htm. Wait 2 seconds. (See Actual Results)
Actual Results:
Results as per steps above
1. noscript tag renders correctly
2. pagetwo.htm opens but noscript tag does not render.
Expected Results:
1. Pass. Result as expected
2. Fail. pagetwo.htm should open and contents of noscript tag should render
Above sequence works as expected in IE 6.x and Opera 8.x
Any existing website that uses a "Refresh" followed by a noscript will not render the contents of the noscript tag
Comment 1•19 years ago
|
||
Could you attach an example or show an url that shows the bug?
Testcase.
Reporter, this .zip file contains two files. Please check they faithfully match what you describe.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/2006101023 Firefox/2.0
WFM. Although my testcase may not accurately depict the problem.
Comment 4•18 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Your testcase seems fine to me, Toby. This works for me in a Firefox 2.0.0.3 build as well as on current trunk.
->WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•