No subject

take one of the following approaches:

(1) put font (and thus platform) dependent test cases in non-platform test
directory, then add entries to Skipped for other platforms; this seems the
current approach with many platform/font dependent tests, especially
related to I18N features;
(2) put font (and thus platform) dependent test cases in platform test
directory, possibly ending up with separate tests per platform;
(3) what would be nice is to not generate rendering dump from DRT but
instead use script only; since I'm testing line-breaking logic, what would
do nicely is a set of internal styles available via getComputedStyle() on a
block element:

   - -webkit-line-count - numeric value indicating number of formatted
   lines produced from rendering a block
   - -webkit-line-chars-1 through -N, which returns the chars of line N as
   formatted when rendering a block

That is, with these properties, I could use script to determine which line
breaks occurred and where. I don't care about geometries or pixels in these
particular tests, just whether breaks occur in specific contexts.

Any recommendations on whether to pursue one of (1) or (2) above, or try
the more ambitious (but more platform independent) third approach?

I suppose I could start with (1) or (2) and then pursue (3) as a subsequent
task.

Regards,
Glenn

--bcaec5016135721b7804c8df1a03
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

What is the recommended approach to test cases when one needs to use a CJK =
font that covers the test data? I could use DRT text results as expected bu=
t given lack of common font across platforms, that doesn't seem to be e=
ffective.<div>

<br></div><div>From my somewhat limited (i.e., newbie) exposure to WK, I ga=
ther one can take one of the following approaches:</div><div><br></div><div=
>(1) put font (and thus platform) dependent test cases in non-platform test=
 directory, then add entries to Skipped for other platforms; this seems the=
 current approach with many platform/font dependent tests, especially relat=
ed to I18N features;</div>

<div>(2) put=C2=A0font (and thus platform) dependent test cases in platform=
 test directory, possibly ending up with separate tests per platform;</div>=
<div>(3) what would be nice is to not generate rendering dump from DRT but =
instead use script only; since I&#39;m testing line-breaking logic, what wo=
uld do nicely is a set of internal styles available via getComputedStyle() =
on a block element:</div>

<div><ul><li>-webkit-line-count - numeric value indicating number of format=
ted lines produced from rendering a block</li><li>-webkit-line-chars-1 thro=
ugh -N, which returns the chars of line N as formatted when rendering a blo=
ck</li>

</ul><div>That is, with these properties, I could use script to determine w=
hich line breaks occurred and where. I don&#39;t care about geometries or p=
ixels in these particular tests, just whether breaks occur in specific cont=
exts.</div>

<div><br></div><div>Any recommendations on whether to pursue one of (1) or =
(2) above, or try the more ambitious (but more platform independent) third =
approach?</div></div><div><br></div><div>I suppose I could start with (1) o=
r (2) and then pursue (3) as a subsequent task.</div>

<div><br></div><div>Regards,</div><div>Glenn</div><div><br></div>

--bcaec5016135721b7804c8df1a03--