- From: Rebecca Hauck <rhauck@adobe.com>
- Date: Fri, 2 Aug 2013 17:34:37 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- CC: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Ok, thanks David & GΓ©rard. Although it's implied and sort of obvious, I'll add a sentence to make sure this is clear. On 8/2/13 5:26 PM, "L. David Baron" <dbaron@dbaron.org> wrote: >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:33:15 UTC