Bug 100546

Summary: [css3-text] Provide pixel results for text decoration style layout tests
Product: WebKit Reporter: Bruno Abinader (history only) <bruno.abinader>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: bfulgham, lamarque, rakuco
Priority: P2 Keywords: DoNotImportToRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://dev.w3.org/csswg/css-text-decor-3/#text-decoration-style-property
Bug Depends on: 92868, 93507, 93509, 94110, 94111, 94112, 94114, 96408, 104682    
Bug Blocks: 58491    

Bruno Abinader (history only)
Reported 2012-10-26 11:29:40 PDT
The following layout tests have pixel results missing: fast/css3-text/css3-text-decoration/text-decoration-style.html fast/css3-text/css3-text-decoration/repaint/repaint-text-decoration-style.html These tests are part of the CSS3 Text Decoration layout tests. These tests are disabled by default, and their WebKit code implementation is safeguarded by CSS3_TEXT feature flag. This bug requires code fix/implementation from others to be properly fixed (see "depends on" section for details).
Attachments
Raphael Kubo da Costa (:rakuco)
Comment 1 2012-10-31 08:41:05 PDT
Quick question: when I try to run the layout tests for the EFL port with support for pixel tests enabled, pixel results for the tests you mentioned in the bug description are always generated, but I have no idea if they are correct (they probably aren't). Are the results in the future going to be stored in these cross-platform directories just like the case for fast/css3-text/css3-text-decoration/repaint/repaint-text-decoration-line.html already is? In the case of EFL and GTK, is bug 94110 the only one blocking these tests from generating meaningful results?
Lamarque V. Souza
Comment 2 2012-10-31 09:03:02 PDT
Hi Raphael, Bruno asked me to answer both your questions with 'yes'. Bruno lives in Manaus, which is in a power outage right now and the link to the Internet in the city is down too, so he will not be able to answer your question for the time being.
Note You need to log in before you can comment on or make changes to this bug.