On Mon, Jul 12, 2010 at 7:49 PM, Maciej Stachowiak <m...@apple.com> wrote: > > I think it's fine to enable MathML soon, as long as we make sure of the > following: > > 1) Using a MathML-enabled build shouldn't cause stability problems or > functional or performance regressions when browsing ordinary non-MathML > content.
Some of tis is testable by passing all our test cases, right? Or did you have something else in mind? Do we have anything that measures "performance" for regressions? I suspect that the performance on MathML with complicated row structures isn't going to be good at the moment. There are two many multiple rendering passes for operator and content stretching and that can probably be optimized. On the other hand, it seems to do quite well on "reasonable" MathML. > 2) We should try to do some fuzz testing to verify that MathML doesn't create > security risks. > > #2 can happen after we enable MathML, but should probably happen before > anyone ships it. What is involved in (2) ? I'm happy to try to beat on the code to make sure it works well enough for people to feel comfortable turning it on. -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics _______________________________________________ webkit-dev mailing list firstname.lastname@example.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev