Closed Bug 297559 Opened 20 years ago Closed 14 years ago

restaurantactivityreport.com - invalid markup (submitting form info results in blank page)

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: laura, Unassigned)

References

()

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; Alexa Toolbar)
Build Identifier: 

the page http://www.restaurantactivityreport.com/subscription1.htm goes to a 
blank page after you hit submit. This should go to this page: 
http://www.restaurantactivityreport.com/subscription2.php

Form not processing

Reproducible: Always

Steps to Reproduce:
1.go to http://www.restaurantactivityreport.com/subscription1.htm
2.fill out form
3.hit submit

Actual Results:  
you get a blank page and it says it's Done.  

Expected Results:  
continued to the second page of the form submittal
This is a problem with the site. It uses invalid markup to advance to the next
page. The fact that it works in IE isn't something web masters should rely on
when designing pages.
Assignee: nobody → english-us
Status: UNCONFIRMED → NEW
Component: Form Manager → English US
Ever confirmed: true
OS: Windows XP → All
Product: Firefox → Tech Evangelism
QA Contact: form.manager → english-us
Hardware: PC → All
Summary: after hitting submit on form page is blank-POSTDATA error upon hitting refresh → restaurantactivityreport.com - invalid markup (submitting form info results in blank page)
INCOMPLETE due to lack of activity since the end of 2009.

If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself.

Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.