We'll schedule a task for identifying in CSS 1/2.1 folders which tests should be replaced by picture-based ones, and which could not. For the latter, we'll try to think about workarounds to propose.
Have you an accurate placeholder to suggest for these thoughts? I was not sure whether bugzilla or wiki would be better....
For others tests folders, I think that if the proposed plan fits WebKit community's interest, we should file bugs about replacing Tables, Fast and Traversal by image-based tests, and also bugs about exploring the parts we haven't done yet (plugin, svg, http, editing)...
Let me know what you think,
Regards
Jean-Charles
On 9/1/06, Darin Adler <[EMAIL PROTECTED]> wrote:
On Sep 1, 2006, at 1:38 AM, Jean-Charles VERDIE wrote:
> It would surely be the best plan, but I'm not sure that it will be
> possible (in a measurable human-based time). May be the fastest way
> of having the tests more cross-platform is to split them into three
> categories:
> 1- those which already are cross-platform.
> 2- those which are not cross-platform, but which do not need a
> font. E.g. comparing 2 cells of a table. We could replace the texts
> by pictures with a specific size. The test would not be self-
> documented any more, but we can solve this by a 2-windows solution,
> one with the explanation, and one with the actual test.
> 3.1- those which are not cross-platform, but which need a font.
> Some can be addressed by replacing DumpRenderTree by DumpAsText.
> 3.2 - ...But other tests in this third will hardly need a font,
> e.g. css manipulation or font replacement.
>
> For this latest part, I don't imagine a solution right now. May be
> some can be addressed by your proposal #4 But one question is: how
> much of these tests remain? if we address 1- to 3.1 ? IMHO here is
> the list :
> - DOM: already x-platform
> - plugins / svg / http / editing: we've not started looking at them
> - Tables, fast, traversal: all should be replaceable by images
> - CSS 1, 2.1: here is the list of our problems :) There are 362
> tests in these folders, but may be only 30% of them are belonging
> to the problematic category so something like a big hundred of
> tests would need to be re-thinked...
Sounds good. If you would like to start doing some work in this area,
please let us know about your specific ideas.
Maybe for your (2) above we could make tests where certain parts of
the page wouldn't dump. That way the test could be self documenting
but the part that dumps wouldn't be affected by the text.
-- Darin
--
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
