Bug 9068 - [S60] Continue button does not work on www.lufthansa.com
Summary: [S60] Continue button does not work on www.lufthansa.com
Status: CLOSED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 312.x
Hardware: S60 Hardware S60 3rd edition
: P1 Normal
Assignee: Nobody
URL: http://www.lufthansa.com
Keywords: PlatformOnly
Depends on: 9116 9189
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-23 12:13 PDT by Krishna
Modified: 2011-03-21 11:52 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Krishna 2006-05-23 12:13:06 PDT
Steps to Reproduce:
1. Load the url
2. In the "From" field enter "FRA", in the "To" field enter "LHR". Choose some date in the future and activate the "Search" button
3. Activate the "Continue" button.
Expected result:
The next page is displayed.
Actual result:
Nothing happens and remains in the same page.
Comment 1 David Carson 2006-05-23 14:29:16 PDT
Can not reproduce on TOT. Safari does seem to hang for about a  minute when you click on the Continue button, but the new page does appear. On the phone this 1 minute could feel easily like 10mins.
Comment 2 David Kilzer (:ddkilzer) 2006-05-23 14:59:28 PDT
(In reply to comment #1)
> Can not reproduce on TOT. Safari does seem to hang for about a  minute when you
> click on the Continue button, but the new page does appear. On the phone this 1
> minute could feel easily like 10mins.

This sounds like it may be a performance bug.  Does CPU usage spike when the button is clicked?  If so, you may want to change the sense of this bug to be a performance bug, or open a new bug to look into the performance (assuming it's not a general problem with the Internet like DNS resolution slowness, dropped packets, or a slow server).
Comment 3 David Carson 2006-05-23 15:19:49 PDT
> This sounds like it may be a performance bug.  Does CPU usage spike when the
> button is clicked?  If so, you may want to change the sense of this bug to be a
> performance bug, or open a new bug to look into the performance (assuming it's
> not a general problem with the Internet like DNS resolution slowness, dropped
> packets, or a slow server).
> 
Seeing that it is faster now, I am guessing that it was a general internet problem. CPU did not seem to spike more that usual.
Comment 4 Krishna 2006-05-30 07:59:28 PDT
When clicking on the Search button (as specified in the above step 2) I received an error: 'Reindeer: unable to perform operation' on the S60 3.0 sdk emulator.
Comment 5 Krishna 2006-05-30 10:29:41 PDT
TSW Error ID: PKAI-6GWNMV
Comment 6 David Carson 2006-06-02 07:53:03 PDT
'Search' not working is the same problem as 9065. The POST operation is returning a -20 error (KErrCorrupt) from the HTTP stack.
Comment 7 David Carson 2006-06-02 08:02:14 PDT
Change dependant bug
Comment 8 David Carson 2006-06-04 18:37:26 PDT
After applying a patch to fix POST bug, the results page does not fully load. There is a post that occurs while the results page is loading, and it returns a content-length of zero, ie:
----
POST /pl/Lufthansa/wds/Override.action HTTP/1.1
[snip]
Server: Netscape-Enterprise/6.0
Date: Mon, 05 Jun 2006 01:15:02 GMT
Content-length: 0
Cache-control: private
----
Whereas FF responds with deflated content. the only difference that I can find is that the Browser is not sending a UAHeader. Adding that has a dependent bug.
Comment 9 Darin Adler 2006-06-29 08:25:58 PDT
Adding S60 prefix to P1 bugs that are S60 platform-only.
Comment 10 Bradley Morrison 2008-04-09 11:31:51 PDT
Bulk update of s60 bugs - tagging and closing.
Comment 11 Bradley Morrison 2008-04-09 11:39:32 PDT
Bulk closing of all s60 platform bugs. 

Sorry for the noise!
Comment 12 Joel Parks 2011-03-21 11:52:11 PDT
re-purposing InTSW keyword for use by QtWebkit team