Closed
Bug 305668
Opened 20 years ago
Closed 17 years ago
uscourts.gov - page immediately after login does not display fill in form in second frame
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pablito, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
page immediately after login does not display fill in form for case information.
the page appears to be in two frames. This is PACER for the Northern District
of California
Reproducible: Always
Steps to Reproduce:
1.logging in with name and password
2.
3.
Actual Results:
displayed the fill in form for case information.
Note: Very similar PACER page for the Central District of California
immediately after
https://pacer.login.uscourts.gov/cgi-bin/login.pl?court_id=candc displays
correctly in Firefox. Problem is probably in the cgi script used on the
Northern District.
Expected Results:
note: there is a difficulty in Firefox testing this as you need an ID and
password to log in
pacer service center email address is pacer@psc.uscourts.gov
Updated•20 years ago
|
Summary: page immediately after login does not display fill in form in second frame → uscourts.gov - page immediately after login does not display fill in form in second frame
| Reporter | ||
Comment 1•20 years ago
|
||
wrong url given for central district's pacer login. should be
https://pacer.login.uscourts.gov/cgi-bin/login.pl?court_id=cacdc
Updated•20 years ago
|
Comment 2•17 years ago
|
||
Their manual (I'm not setting up a login that I'm going to have to pay for) says:
"Web Browser - The current release of PACER was written as a web application
compatible with Netscape 4.x and above or Internet Explorer 5.x and above. However, it
is recommended to use the most recent version of any browser. Mozilla and Firefox are
also compatible with PACER."
That seems to imply that this *should* work, at least.
Paul, is it still broken? Can you explain what the problem appears to be that makes you believe this is a TE bug?
Comment 3•17 years ago
|
||
One month is quite long enough to have waited for a response. INCOMPLETE unless someone can answer comment 2.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•