Bug 34642 - [Qt] Form buttons do not appear in page view: piperlime.com
Summary: [Qt] Form buttons do not appear in page view: piperlime.com
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Major
Assignee: Vishwanathan Krishnamoorthy
URL:
Keywords: Qt
Depends on: 35792
Blocks: 35784
  Show dependency treegraph
 
Reported: 2010-02-05 04:35 PST by nokiabugz
Modified: 2010-07-01 11:05 PDT (History)
11 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nokiabugz 2010-02-05 04:35:45 PST
STEPS TO REPRODUCE:
1. Load piperlime.com
2. Select "Sign in" or "Account" link 
3. Verify forms in steps 1 and 2
ACTUAL RESULTS:

Home page view
"Checkout" button is missing that suppose to be next to "0 items in your bag" link in top right corner
"Sign in" page view:
"Returning customers" div has missing "Sign in" and "Cancel" buttons 
"New customers" div has missing "Register" and "Cancel" buttons
"Account" page view
"Account settings" div has missing "Create an account" button
EXPECTED RESULTS:
Buttons should be rendered on the page

NOTE:
Same observed using Anomaly 4.6.1
Comment 1 Tor Arne Vestbø 2010-03-05 09:09:03 PST
Please follow the QtWebKit bug reporting guidelines when reporting bugs.

See http://trac.webkit.org/wiki/QtWebKitBugs

Specifically:

  - The 'QtWebKit' component should be used for bugs/features in the QtWebKit API layer, not to signify that the bug is specific to the Qt port of WebKit

    http://trac.webkit.org/wiki/QtWebKitBugs#Component

  - Priority is set by developers when scheduling and triaging tasks, please leave this at the default priority.

    http://trac.webkit.org/wiki/QtWebKitBugs#Priority

  - Choose a descriptive summary/title for the bug and prefix the summary with "[Qt]" if the bug only applies to the Qt-port.

    https://trac.webkit.org/wiki/QtWebKitBugs#Summary
Comment 2 Kent Hansen 2010-03-10 07:37:28 PST
Couldn't reproduce the missing buttons (Linux, r55658, Qt 4.6-ish), but the size and rendering of the input fields seems wrong (fields are really narrow, text spills outside).
Comment 3 Tor Arne Vestbø 2010-03-16 04:18:14 PDT
Can't reproduce i trunk (week10) on Windows 7 with Qt 4.6.2
Comment 4 Benjamin Poulain 2010-03-16 07:50:05 PDT
I can reproduce the problem on Symbian with Qt 4.7 trunk. No buttons are displayed.
Comment 5 Timothy Lu 2010-03-29 12:47:21 PDT
Moved to Browser team for further investigation.
Comment 6 Jukka Jokiniva 2010-06-10 03:57:06 PDT
Just tried Qt4.6.3 + QtWebKit2.0 on N97 and seems to work ok.
Comment 7 Benjamin Poulain 2010-06-10 05:49:48 PDT
(In reply to comment #6)
> Just tried Qt4.6.3 + QtWebKit2.0 on N97 and seems to work ok.

Closing then.
Comment 8 Hao Lu 2010-06-17 14:17:49 PDT
Inga Shpolberg added a comment - 17/Jun/10 04:33 PM 
able to reproduce the issue above with N97 build 36406 and qt 4.6.3 and webkit 2.0 version 67 from june 16
Comment 9 Jukka Jokiniva 2010-06-17 22:59:51 PDT
I have received information that this bug occurs with QGraphicsWebView but not with QWEbView
Comment 10 Simon Hausmann 2010-06-18 14:41:47 PDT
I have vague memories of discussing a similar issue long time ago. Janne, do you remember this?

If I recall correctly this was a problem in the S60 style.
Comment 11 Janne Koskinen 2010-06-29 05:17:51 PDT
(In reply to comment #10)
> I have vague memories of discussing a similar issue long time ago. Janne, do you remember this?
> 
> If I recall correctly this was a problem in the S60 style.

I looked at the code and don't think we have had this one reported yet.
We did have issue of doing css styling of form elements e.g. buttons. The elements became invisible when CSS was applied. Actually now that I think of it that might be still broken.
Comment 12 Kenneth Rohde Christiansen 2010-06-29 05:27:26 PDT
Luiz, can you please have a look at this?
Comment 13 Viatcheslav Ostapenko 2010-07-01 10:42:30 PDT
It's not a bug. It's quite _special_ web page design.
The bug reproducible, if phone gets RAM exhausted.

The problem here, in big gif image (886px × 2,060px), which takes too much ram.
https://secure-piperlime.gap.com//content/0000/331/295/universal_button_sprite.gif
File itself is not very big (94,180 bytes), but when it get's unpacked, it takes about 8mb of RAM.
If the phone has enough RAM, problem is not reproducible.