<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - MathML: Extra left space for arrows inside <mo>"
href="https://bugs.webkit.org/show_bug.cgi?id=170272#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - MathML: Extra left space for arrows inside <mo>"
href="https://bugs.webkit.org/show_bug.cgi?id=170272">bug 170272</a>
from <span class="vcard"><a class="email" href="mailto:fred.wang@free.fr" title="Frédéric Wang (:fredw) <fred.wang@free.fr>"> <span class="fn">Frédéric Wang (:fredw)</span></a>
</span></b>
<pre>(In reply to Minsheng Liu from <a href="show_bug.cgi?id=170272#c7">comment #7</a>)
<span class="quote">> Thanks for the feedback. I will look at it when I have more time later this
> week.
>
> However, I do have some question regarding the tests, as I am completely new
> to WebKit hacking. Hours ago, I run a WebKit test on my modified build.
> While there were many issues, none of them were related with MathML. I
> expect at least some diffs in MathML tests. Are MathML tests in LayoutTests/
> automated or manual? What is the right way to see whether I have broken
> existing *MathML* code or not?</span >
On which platform do you work?
Tests are executed automatically with the run-webkit-tests (you can restrict execution to Layout/mathml/). Two things to note:
1) It is possible that our test coverage is limited and hence does not detect your changes, that's why we always add new tests when we fix a bug.
2) There are some tests (pixel tests) which compare against an expected render tree (txt file) and visual rendering (PNG image). However, if your code changes visual rendering but to the render tree, the test runner will still consider the test to pass. That's very likely to be the case if you only modify RenderMathMLToken::paint here. That's why it's often better to use reftests or javascript tests.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>