Closed Bug 110131 Opened 23 years ago Closed 23 years ago

URL never finishes loading/redirects...

Categories

(Tech Evangelism Graveyard :: English US, defect, P1)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 100247

People

(Reporter: DebugWeyers, Assigned: darin.moz)

References

()

Details

(Whiteboard: [bugscape 10984])

From Bugzilla Helper:
BuildID:    20011019

The above url is generated by a form submission on the united airlines 
website.  For whatever reason, it silently fails using NS6 and the user never 
gets past a temporary progress screen.

Reproducible: Always
Steps to Reproduce:
1.Paste the url above into the url bar
2.load page


Actual Results:  "Please wait while we retrieve the information" message is 
displayed with accompanying graphic.  The browser status bar indicates "done" 
and a solid blue progress bar is displayed.  Web page remains in this state 
indefinitely.

Expected Results:  Same initial results.  After a few seconds, a "Create 
itinerary" page is displayed (using MSIE 5.5).
The browser sniffing code looks suspect - probably a bug for United to fix.
It checks for layers and document.all to detect Netscape/IE
Over to Tech Evangelism.
Status: UNCONFIRMED → NEW
Component: Networking → English: US
Ever confirmed: true
Product: Browser → Tech Evangelism
Target Milestone: --- → Dec
Version: other → unspecified
adding topembed and edt0.9.4 based on bugscape bug 10984. Thanks. 
Keywords: edt0.9.4, topembed
Removed edt094 and topembed since no code change is happening, but is a priority
embedding issue.
Keywords: edt0.9.4, topembed
Priority: -- → P1
Whiteboard: [bugscape 10984]
darin
Assignee: neeti → darin
jst: we already have a bug on this... do you know what happened to that bug? 
can you dupe this one?  thx!
Yeah...

*** This bug has been marked as a duplicate of 100247 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
QA Contact: benc → zach
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.