Bug 34723

Summary: There is no test text "Filler Text" in "Parsing unexpected end of string" test page.
Product: WebKit Reporter: sangeetha.sugavanam
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: robert
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
test case none

sangeetha.sugavanam
Reported 2010-02-08 13:22:09 PST
Use case: Parsing unexpected end of string Step to reproduce: 1.Open QtLauncher. 2.Unzip contents of the zip file. 3.Open the html page using QtLauncher. 3.Tap the link "Parsing unexpected end of string". 4.Check the page. Actual outcome: There is no test text "Filler Text" dispayed . Expected outcome: There should be a test text "Filler Text" displayed and it should be green. This error can be reproduced on safari 4.0.4(531.21.10).
Attachments
test case (44.30 KB, application/x-zip-compressed)
2010-02-08 13:22 PST, sangeetha.sugavanam
no flags
sangeetha.sugavanam
Comment 1 2010-02-08 13:22:40 PST
Created attachment 48360 [details] test case
Tor Arne Vestbø
Comment 2 2010-03-10 06:31:21 PST
Please follow the QtWebKit bug reporting guidelines when reporting bugs. See http://trac.webkit.org/wiki/QtWebKitBugs Specifically: - The 'QtWebKit' component should only be used for bugs/features in the public QtWebKit API layer, not to signify that the bug is specific to the Qt port of WebKit http://trac.webkit.org/wiki/QtWebKitBugs#Component - Add the keyword 'Qt' to signal that it's a Qt-related bug http://trac.webkit.org/wiki/QtWebKitBugs#Keywords
Robert Hogan
Comment 3 2010-03-10 13:19:34 PST
Test link is: http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/eof-003.htm Webcore CSS bug. Fails on Chromium and QtLauncher too.
sangeetha.sugavanam
Comment 4 2011-03-02 11:12:41 PST
This bug occurs because of syntax error in the test case from the w3.org link. Should i send the fix to the test case for the w3.org link?
Robert Hogan
Comment 5 2012-02-13 14:17:05 PST
*** This bug has been marked as a duplicate of bug 78538 ***
Note You need to log in before you can comment on or make changes to this bug.