Re: [css-writing-modes-3] text-orientation-script-r-001 , text-orientation-script-u-001

On Tue, Apr 28, 2015 at 4:06 PM, Koji Ishii <kojiishi@gmail.com> wrote:

> On Tue, Apr 28, 2015 at 3:13 AM, Gérard Talbot <css21testsuite@gtalbot.org
> > wrote:
>
>> Koji,
>>
>> 1-
>> I have tried text-orientation-script-r-001 test and my system went
>> unresponsive (intensively very busy) during 15 seconds or so. Your
>> text-orientation-script-* tests are definitely amazing and intriguing ...
>> but that text-orientation-script-r-001 test is processing thousands of
>> characters.
>>
>> text-orientation-script-u-001 is probably even more system-demanding as
>> it processes more characters! I have not tried to load that test on my
>> little, modest system ...
>>
>
> Yeah, I know. It looks like it varies by browsers, so I'll test a bit more
> and consider splitting further.
>

Split up to 4096 code points per file. Gecko unfortunately returns a whole
block to Range.getBoundingClientRect()[1], which this test relies on, and
is probably the reason why it's slow for this test.

I'll file a bug, and see further splits are needed after it's fixed.

[1]
https://developer.mozilla.org/en-US/docs/Web/API/range/getBoundingClientRect

/koji

Received on Tuesday, 28 April 2015 16:03:01 UTC