gecko-dev/layout/reftests/w3c-css/submitted
Scott Johnson dc45ee09d2 Bug 743402, Part 6: Add unit tests for functionality of bug 743402. [r=roc] 2013-07-25 10:34:38 -05:00
..
conditional3 Bug 814566 - Allow invalid syntax (with balanced parentheses) inside @supports conditions. (v1.1.1) r=dbaron 2012-12-23 13:30:55 +11:00
css21 Bug 883676 - Implement 'page-break-inside:avoid' also for the case where the block reflow is COMPLETE but does not fit in the available height. r=roc 2013-07-13 13:18:17 +00:00
flexbox Add DOCTYPE declaration to test. No bug. No review. 2013-06-16 10:41:37 -07:00
multicol3 Bug 743402, Part 6: Add unit tests for functionality of bug 743402. [r=roc] 2013-07-25 10:34:38 -05:00
references
values3 Bug 879494. Remove bug685516 annotations from reftests, they are not needed anymore. r=khuey 2013-06-05 00:18:54 -05:00
README
reftest.list Bug 880137 part 1: Create reftest directory for flexbox in w3c-css folder. rs=dbaron 2013-06-06 20:37:09 -07:00
test-template-001.xht

README

W3C CSS Test Suite Submission Directory
---------------------------------------

Put tests here that are to be submitted to the official W3C CSS test
suites at http://test.csswg.org/. This directory will be sync'ed
automatically with the contributors/mozilla/ directory in the CSSWG
repository. The master copy is Mozilla's; make edits here, not there.

Tests submitted here must conform to the CSSWG test format:
  http://wiki.csswg.org/test/format
The extra metadata is there to connect tests to their respective specs
and to help reviewers and people trying to debug their implementations
understand and analyze the tests. (These are not write-only regression
tests.)

TEST FILENAMES MUST BE GLOBALLY UNIQUE across the entire CSSWG test repo,
so don't rely on directory names as context.

The W3C format uses <link> tags for connecting reftests to their
references and generates reftest.list from a build process. Until we
set up a build process here, you need to link up the reftest both ways.

Because W3C sometimes needs to allow multiple correct renderings for
a particular case, a test linked to a reference must match ANY of them,
not all of them. To require a test to match all references, chain the
references to each other. If (a discrete number of) multiple renderings
are conformant, make a reftest comparison for each of them, and mark
all but the one we support as 'fails' in the reftest.list.

You can copy the test-template-001.xht and references/test-template-001.xht
files in this directory as a starting point

Submitted tests are tracked in Shepherd: http://test.csswg.org/shepherd/

Some things cannot be reftested; if another format is necessary to test
a particular feature, contact public-css-testsuite@w3.org and/or ask
the layout peers for help.

Legal Stuff
-----------

The following license grant applies to contributions to this directory
(unless copyright is owned by a W3C Member, in which case the Membership
agreement applies):

  The Contributor hereby grants to the W3C, a perpetual, non-exclusive,
  royalty-free, world-wide right and license under any Contributor
  copyrights in this contribution to copy, publish, use, and modify the
  contribution and to distribute the contribution under a BSD License or one
  with more restrictive terms, as well as a right and license of the same
  scope to any derivative works prepared by the W3C and based on, or
  incorporating all or part of the contribution. The Contributor further
  agrees that any derivative works of this contribution prepared by the W3C
  shall be solely owned by the W3C.

  The Contributor states, to the best of her/his knowledge, that she/he,
  or the company she/he represents, has all rights necessary to contribute
  the Materials.

  W3C will retain attribution of initial authorship to the Contributor. The
  W3C makes no a-priori commitment to support or distribute contributions.

  THE CONTRIBUTION IS PROVIDED AS IS, AND CONTRIBUTORS MAKE NO REPRESENTATIONS OR
  WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF
  MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE;
  THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE. CONTRIBUTORS
  MAKE NO REPRESENTATIONS, EXPRESS OR IMPLIED, THAT THE CONTRIBUTION OR THE USE
  THEREOF INDICATES CONFORMANCE TO A SPECIFICATION; CONTRIBUTIONS ARE PROVIDED
  ONLY TO HELP REACHING INTEROPERABILITY.