Bug 115437

Summary: [GTK] Reftests failing after the subpixel layout was turned on
Product: WebKit Reporter: Zan Dobersek <zan>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: abucur, bugs-noreply, chavarria1991, jfernandez, psaavedra, rego, WebkitBugTracker, zimmermann
Priority: P2 Keywords: Gtk, LayoutTestFailure, Regression
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 124234    
Bug Blocks:    

Zan Dobersek
Reported 2013-04-30 12:19:22 PDT
How the tables have turned ... Here's the list of the reference tests that are failing after the subpixel layout was enabled on the GTK port: css3/flexbox/auto-margins.html fast/css/sticky/sticky-writing-mode-vertical-lr.html fast/exclusions/shape-inside/shape-inside-percentage.html fast/regions/region-content-flown-into-region.html fast/regions/webkit-flow-inlines-inside-regions-bounds-vertical.html fast/regions/webkit-flow-inlines-inside-regions-bounds.html Of course, the failures should be investigated.
Attachments
Manuel Rego Casasnovas
Comment 1 2013-10-23 01:12:18 PDT
(In reply to comment #0) > fast/regions/region-content-flown-into-region.html The tests flagged in bug #122511 have a very similar issue to the previous one.
Marcos Chavarría Teijeiro (irc: chavaone)
Comment 2 2015-02-20 03:33:12 PST
css3/flexbox/auto-margins.html is passing since r178063 which updates the test expectations. I will remove this bug from TestExpectations file.
Nikolas Zimmermann
Comment 3 2019-11-27 04:17:07 PST
According to https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29/builds/11947/steps/layout-test/logs/stdio fast/text/complex-initial-advance.html seems to pass. Will update expectations.
Pablo Saavedra
Comment 4 2020-01-10 14:20:54 PST
It is fixed because the expectations was updated in r250884 (2019-Oct) The https://webkit.org/b/206079 removes the expectation in GTK+ from platform/gtk/TestExpectations for related to this defect.
Note You need to log in before you can comment on or make changes to this bug.