- From: L. David Baron <dbaron@dbaron.org>
- Date: Fri, 2 Aug 2013 17:26:48 -0700
- To: Rebecca Hauck <rhauck@adobe.com>
- Cc: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On Friday 2013-08-02 16:57 -0700, Rebecca Hauck wrote:
> We have this documented on the CSSWG wiki [1] and I'm not sure if or how it's actually used. I see 35 tests in the suite that have it [2]. I understand theoretically what it's used for, but it seems the missing piece of information here is that an external harness running automated reftests would need to know about it to honor it, correct? In porting this to the new W3C test documentation suite, I'd like make this complete or remove it if it's irrelevant.
The harness would need to look for class="reftest-wait" (or a class
attribute containing reftest-wait) on the root element before taking
a screenshot. If reftest-wait is present, the screenshot is delayed
until the attribute is removed.
-David
--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla https://www.mozilla.org/ 𝄂
Before I built a wall I'd ask to know
What I was walling in or walling out,
And to whom I was like to give offense.
- Robert Frost, Mending Wall (1914)
Received on Saturday, 3 August 2013 00:27:19 UTC