My team is currently working on having the layout tests ported to linux, to ease our future tasks on completing current efforts to make webkit available for linux.
We have a big issue, which is that free type does not render text the same way as OSX does. The expected results do not match.
We tried to hack freetype to make this work, but no obvious solution revealed. We started today a thread there to see if they have a solution.
Here is an example of the diff we get :
- RenderTable {TABLE} at (0,18) size 88x52 [bgcolor=#FFA500] [border: (1px outset #808080)]
- RenderTableSection {TBODY} at (1,1) size 86x50
- RenderTableRow {TR} at (0,2) size 86x22
- RenderTableCell {TD} at (2,14) size 24x22 [border: (1px inset #808080)] [r=0 c=0 rs=2 cs=1]
- RenderText {#text} at (2,2) size 20x18
- text run at (2,2) width 20: "X1"
- RenderTableCell {TD} at (28,2) size 27x22 [border: (1px inset #808080)] [r=0 c=1 rs=1 cs=1]
- RenderText {#text} at (2,2) size 20x18
- text run at (2,2) width 20: "X2"
- RenderTableRow {TR} at (0,26) size 86x22
- RenderTableCell {TD} at (28,26) size 27x22 [border: (1px inset #808080)] [r=1 c=1 rs=2 cs=1]
+ RenderTable {TABLE} at (0,18) size 87x52 [bgcolor=#FFA500] [border: (1px outset #808080)]
+ RenderTableSection {TBODY} at (1,1) size 85x50
+ RenderTableRow {TR} at (0,2) size 85x22
+ RenderTableCell {TD} at (2,14) size 23x22 [border: (1px inset #808080)] [r=0 c=0 rs=2 cs=1]
+ RenderText {#text} at (2,2) size 19x18
+ text run at (2,2) width 19: "X1"
+ RenderTableCell {TD} at (27,2) size 27x22 [border: (1px inset #808080)] [r=0 c=1 rs=1 cs=1]
+ RenderText {#text} at (2,2) size 19x18
+ text run at (2,2) width 19: "X2"
+ RenderTableRow {TR} at (0,26) size 85x22
+ RenderTableCell {TD} at (27,26) size 27x22 [border: (1px inset #808080)] [r=1 c=1 rs=2 cs=1]
We imagine a solution which is to drop our goal to fix the problem, and instead generate "linux"-based -expected.txt files and to modify dump render tree to either chose osx or linux -based expected files, depending on the platform we are testing on.
This solution has a major drawback, which is that it will force the community to maintain two version of expected files for every single test.
Before starting to work in this direction, I'd appreciate some feedback on the feeling about this solution, and may be, fortunately, others ideas on how to remove this roadblock.
Best regards
--
Jean-Charles Verdié
Origyn Web Browser for Embedded Systems Team
CTO
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
