diff --git a/DOM-display.html b/DOM-display.html new file mode 100644 index 0000000..6b8359c --- /dev/null +++ b/DOM-display.html @@ -0,0 +1 @@ + HTML 4.01: Attributes test1 test2
test 1 -- block

test 2 -- table
\ No newline at end of file diff --git a/almost-standards-quirk.html b/almost-standards-quirk.html new file mode 100644 index 0000000..e0a462a --- /dev/null +++ b/almost-standards-quirk.html @@ -0,0 +1 @@ + almost-standards test

If both the images in the following table cell have red above or below them, then the page is in "strict" mode. If neither does, then the page is in "quirks" mode. If the first has no red above or below but the second does, then the page is in "almost standards" mode.


The following table has two cells: one cell with br-separated images, and another cell with a single image. If no red is visible around or between these images, the page is using the "quirks"-style line layout. If red appears, it's using "strict"-style layout. IE/* acts as per "quirks" layout in Mozilla.






\ No newline at end of file diff --git a/almost-standards-strict.html b/almost-standards-strict.html new file mode 100644 index 0000000..554243f --- /dev/null +++ b/almost-standards-strict.html @@ -0,0 +1 @@ + almost-standards test

If both the images in the following table cell have red above or below them, then the page is in "strict" mode. If neither does, then the page is in "quirks" mode. If the first has no red above or below but the second does, then the page is in "almost standards" mode.


The following table has two cells: one cell with br-separated images, and another cell with a single image. If no red is visible around or between these images, the page is using the "quirks"-style line layout. If red appears, it's using "strict"-style layout. IE/* acts as per "quirks" layout in Mozilla.






\ No newline at end of file diff --git a/almost-standards.html b/almost-standards.html new file mode 100644 index 0000000..7df6c42 --- /dev/null +++ b/almost-standards.html @@ -0,0 +1 @@ + almost-standards test

If both the images in the following table cell have red above or below them, then the page is in "strict" mode. If neither does, then the page is in "quirks" mode. If the first has no red above or below but the second does, then the page is in "almost standards" mode.


The following table has two cells: one cell with br-separated images, and another cell with a single image. If no red is visible around or between these images, the page is using the "quirks"-style line layout. If red appears, it's using "strict"-style layout. IE/* acts as per "quirks" layout in Mozilla.






\ No newline at end of file diff --git a/alt-style-1.css b/alt-style-1.css new file mode 100644 index 0000000..55b4868 --- /dev/null +++ b/alt-style-1.css @@ -0,0 +1 @@ +body {background: #DDDDFF; color: purple; font-family: serif;} h1 {font: italic 250% sans-serif;} h3 {color: #551155;} p {margin-left: 0.5em; text-indent: 2.5em;} ol, ul {margin-left: 3em;} code {color: magenta; font-family: sans-serif;} a:link {color: #CC66CC; font-weight: bold;} a:visited {color: #993399;} a:hover {color: #DDDDFF; background: #CC66CC;} p.footer {font-size: 75%; text-align: right;} \ No newline at end of file diff --git a/alt-style-2.css b/alt-style-2.css new file mode 100644 index 0000000..37f9a78 --- /dev/null +++ b/alt-style-2.css @@ -0,0 +1 @@ +body {background: #FFE099; color: red; font-family: sans-serif;} h1 {font: small-caps 200% serif; border-bottom: 3px double red; border-top: 1px solid red; padding: 0.2em; background: yellow;} h3 {color: #CC6600; background: #FFCC77; border-left: 1em solid red; padding: 0.1em;} p {margin-left: 2.5em; text-indent: -1.5em;} ol, ul {margin-left: 2em;} ol {list-style-type: upper-roman; color: #990000;} ul {list-style-type: square; color: #CC3333;} code {color: red; font-family: monospace;} a:link {color: #CC9933; font-weight: bold;} a:visited {color: #996600;} a:hover {color: red; background: yellow;} p.footer {font: italic 80% sans-serif; text-align: center; border-top: 1px solid orange;} \ No newline at end of file diff --git a/alt-style-2.html b/alt-style-2.html new file mode 100644 index 0000000..c4ffd2e --- /dev/null +++ b/alt-style-2.html @@ -0,0 +1 @@ + Alternate Stylesheets

Alternate Stylesheets, Part 2

Once you've picked one of the alternate stylesheets for this page, go back to the first page, which links in the same alternate stylesheets. Notice that it starts out with the default stylesheet instead of the alternate that was picked for this page. Even worse, when you come back here odds are you'll be back to the default styles. This is why Javascript-and-cookie-based style pickers are gaining in popularity.

Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

\ No newline at end of file diff --git a/alt-style-3.css b/alt-style-3.css new file mode 100644 index 0000000..b2a2aa9 --- /dev/null +++ b/alt-style-3.css @@ -0,0 +1 @@ +body {background: yellow; color: green; font-family: serif;} h1 {border-width: 2px 0.25em 3px 10px; border-color: purple navy blue cyan; border-style: solid double dashed groove; padding: 0.5em; background: #FF99FF; color: #333333; font-family: monospace;} h3 {color: #CC6600; background: #CCFFCC; border: 1px solid olive; padding: 0.25em;} p {margin-left: 1.5em;} ol, ul {margin-left: 4em;} ol {list-style-type: lower-alpha; font-style: italic; color: maroon;} ul {list-style-type: none;} code {color: fuchsia; font-family: monospace;} a:link {color: blue; font-weight: bold;} a:visited {color: gray; font-style: italic;} a:hover {color: lime; background: purple;} p.footer {text-align: center; margin-top: 5em; color: navy;} \ No newline at end of file diff --git a/alt-style.html b/alt-style.html new file mode 100644 index 0000000..1e9e0e7 --- /dev/null +++ b/alt-style.html @@ -0,0 +1 @@ + Alternate Stylesheets

Alternate Stylesheets

Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

How to Choose an Alternate Stylesheet

This varies by browser. At the moment, only Netscape Navigator 6 supports this natively, so the directions are for that browser. They're pretty simple:

  1. Select the "View" menu.
  2. Select the "Use Stylesheet" submenu
  3. Select the stylesheet you wish to apply to this document.

Note that the titles shown in the "Choose Stylesheet" submenu are specified in the title attribute of the LINK element. Please feel free to examin the source of this document for further information.

For the sake of completeness, I'll include some links which will get different styles in each alternate stylesheet:

Once you've picked one of the alternate stylesheets for this page, go to the next page, which links in the same alternate stylesheets. Notice that it starts out with the default stylesheet instead of the alternate that was picked for this page. Even worse, when you come back here odds are you'll be back to the default styles. This is why Javascript-and-cookie-based style pickers are gaining in popularity.

\ No newline at end of file diff --git a/alt-title-tooltips.html b/alt-title-tooltips.html new file mode 100644 index 0000000..27db53b --- /dev/null +++ b/alt-title-tooltips.html @@ -0,0 +1 @@ + Alt/Title testing

Image with neither title nor alt:

Image with title but not alt:

Image with alt but not title: testing the alt attribute

Image with both title and alt: testing the alt attribute

\ No newline at end of file diff --git a/author-reader-useragent.css b/author-reader-useragent.css new file mode 100644 index 0000000..16a6470 --- /dev/null +++ b/author-reader-useragent.css @@ -0,0 +1,3 @@ +#meyerweb-eric-css-tests li.reader {background: red; + background: repeating-linear-gradient(-45deg,red,red 1em,yellow 1em,yellow 2em);} +#meyerweb-eric-css-tests li.reader.important {background: green !important;} \ No newline at end of file diff --git a/author-reader-useragent.html b/author-reader-useragent.html new file mode 100644 index 0000000..a1ea356 --- /dev/null +++ b/author-reader-useragent.html @@ -0,0 +1,38 @@ + + + + +Author versus user (reader) styles + + + + + +

+Note that the following test will be invalid unless you have a user (reader) style sheet enabled with the following rules: +

+
+#meyerweb-eric-css-tests li.reader {background: red;
+	background: repeating-linear-gradient(-45deg,red,red 1em,yellow 1em,yellow 2em);}
+#meyerweb-eric-css-tests li.reader.important {background: green !important;}
+
+ +
+ +
    +
  1. A user-agent paragraph.

  2. +
  3. Author-reader conflict.

  4. +
  5. Important author-reader conflict.

  6. +
+ + + diff --git a/background-size-specificity.html b/background-size-specificity.html new file mode 100644 index 0000000..86229bb --- /dev/null +++ b/background-size-specificity.html @@ -0,0 +1,33 @@ + + + +background-size specificity + + + + + +
d1: shorthand, then background-size
+
d2: background-size, then shorthand
+ + + diff --git a/bg-position.html b/bg-position.html new file mode 100644 index 0000000..5f7ad3e --- /dev/null +++ b/bg-position.html @@ -0,0 +1 @@ + Untitled
Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.
Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.
\ No newline at end of file diff --git a/border-collapse.html b/border-collapse.html new file mode 100644 index 0000000..1fa4a27 --- /dev/null +++ b/border-collapse.html @@ -0,0 +1,131 @@ + + + +border-collapse + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
#zero
th-c1th-c2th-c3
r1-c1r1-c2r1-c3
r2-c1r2-c2r2-c3
r3-c1r3-c2r3-c3
tf-c1tf-c2tf-c3
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
#one
th-c1th-c2th-c3
r1-c1r1-c2r1-c3
r2-c1r2-c2r2-c3
r3-c1r3-c2r3-c3
tf-c1tf-c2tf-c3
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
#two
th-c1th-c2th-c3
r1-c1r1-c2r1-c3
r2-c1r2-c2r2-c3
r3-c1r3-c2r3-c3
tf-c1tf-c2tf-c3
+ + + + diff --git a/border-spacing.html b/border-spacing.html new file mode 100644 index 0000000..d075588 --- /dev/null +++ b/border-spacing.html @@ -0,0 +1 @@ + Border Spacing

In the following table, the cells should have 5 pixels of border-spacing in the horizontal, and 10 pixels in the vertical.

r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
\ No newline at end of file diff --git a/bullet-test.html b/bullet-test.html new file mode 100644 index 0000000..98a039a --- /dev/null +++ b/bullet-test.html @@ -0,0 +1 @@ + Untitled
\ No newline at end of file diff --git a/bullet-test2.html b/bullet-test2.html new file mode 100644 index 0000000..6a183dc --- /dev/null +++ b/bullet-test2.html @@ -0,0 +1 @@ + Untitled
\ No newline at end of file diff --git a/c/style-insert-tests.css b/c/style-insert-tests.css new file mode 100644 index 0000000..210701d --- /dev/null +++ b/c/style-insert-tests.css @@ -0,0 +1,9 @@ +head {display: block;} +style#tests {display: block; + max-height: 20.33em; + overflow: auto; + white-space: pre; + font: small/1 monospace, serif; + padding: 0 1em 0.75em; + border-bottom: 3px double #999; + background: #DDD; color: #333;} \ No newline at end of file diff --git a/c/style-reveal.css b/c/style-reveal.css new file mode 100644 index 0000000..12254f0 --- /dev/null +++ b/c/style-reveal.css @@ -0,0 +1,4 @@ +/* reveal styles in modern browsers */ +head {display: block; padding-bottom: 1px; margin-bottom: 2em; border-bottom: 3px double #AAA;} +style {display: block; font: small monospace; white-space: pre; padding: 0 1em 1em; + border-bottom: 1px solid #AAA; background: #F1F1F1; color: #666;} diff --git a/c/style-show-tr.css b/c/style-show-tr.css new file mode 100644 index 0000000..c647cee --- /dev/null +++ b/c/style-show-tr.css @@ -0,0 +1,6 @@ +head {display: block;} +style {display: block; position: fixed; + top: 0; right: 0; width: 17.5em; padding: 0 1em 1em; + background: #BBB; border: 1px solid gray; border-width: 0 0 1px 1px; + font-family: monospace; white-space: pre;} +style:hover, style:focus {background: transparent; border-width: 0;} diff --git a/calc.html b/calc.html new file mode 100644 index 0000000..4048ef4 --- /dev/null +++ b/calc.html @@ -0,0 +1,60 @@ + + + +Calculation + + + + +
Testing div with width of 100%
+
Testing div with width of (100% - 200px)
+ +
    +
  1. calc(100px / 2 * 3)
  2. +
  3. calc((100px / 2) * 3)
  4. +
  5. calc(100px / (2 * 3))
  6. +
+ + + diff --git a/captiontest.html b/captiontest.html new file mode 100644 index 0000000..343db4d --- /dev/null +++ b/captiontest.html @@ -0,0 +1,37 @@ + + + +Caption test + + + + +
div
+ + + + + + + + + + + + + +
Test caption
tc r1c1tc r1c2tc r1c3
tc r2c1tc r2c2tc r2c3
+ +
div
+ + + diff --git a/circadients.html b/circadients.html new file mode 100644 index 0000000..0679916 --- /dev/null +++ b/circadients.html @@ -0,0 +1,378 @@ + + + + + +Cicadients + + + + +

Cicadients

+

+A reworking of the first two examples of “The Cicada Principle and Why It Matters to Web Designers” using CSS gradients. (The third example would be theoretically possible to do with gradients, but it would be the worst possible approach.) +

+ +

Example #1

+

Unprefixed CSS: 0.59KB (604 characters, unminified). Total CSS, both prefixed and not: 2.66KB (2,720 characters, unminified). Total, original images: ~7KB (plus two extra server hits).

+
+ +

Example #2

+

+This only covers the first two of the three ‘layers’ in the original example; the third layer would be easily possible but hasn’t yet been done. +

+

Unprefixed CSS: 0.63KB (643 characters, unminified). Total CSS, both prefixed and not: 2.81KB (2,882 characters, unminified). Total, original images: ~23KB (plus two extra server hits).

+
+ + + diff --git a/class-id.html b/class-id.html new file mode 100644 index 0000000..30ae41a --- /dev/null +++ b/class-id.html @@ -0,0 +1,58 @@ + + + +Class+ID test + + + + + +

+What's my color, weight, and border? +[test one][#ex1] +

+

+What's my color, weight, and border? +[test one][#ex2] +

+

+What's my color, weight, and border? +[test two][#ex3] +

+

+What's my color, weight, and border? +[test two][#ex4] +

+

+What's my color, weight, and border? +[test][#ex5] +

+ + + + diff --git a/clip.htm b/clip.htm new file mode 100644 index 0000000..9d7bf8b --- /dev/null +++ b/clip.htm @@ -0,0 +1 @@ + 11.1.2 clip
.contain {position: relative; height: 3.5em; border: 1px dotted gray;}
.cl1 {clip: rect(5px 10px 10px 5px);
   position: absolute;
   padding: 0; border: 1px solid gray; background: #FCC;}
.cl2 {clip: inset-rect(5px 10px 10px 5px);
   position: absolute;
   padding: 0; border: 1px solid gray; background: #FCC;}

[cl1] The content of this 'p' element should be clipped slightly: 5 pixels on the top, 10 pixels to the right, 10 pixels on the bottom, and 5 pixels to the left. This will cause the text to be cut off to a small extent on each side of the element.

[cl2] The content of this 'p' element should be clipped slightly: 5 pixels on the top, 10 pixels to the right, 10 pixels on the bottom, and 5 pixels to the left. This will cause the text to be cut off to a small extent on each side of the element.

\ No newline at end of file diff --git a/counters.html b/counters.html new file mode 100644 index 0000000..c4acd4a --- /dev/null +++ b/counters.html @@ -0,0 +1,47 @@ + + + +Figure 12-31 + + + + + +
    +
  1. Lists +
      +
    1. Types of Lists
    2. +
    3. List Item Images
    4. +
    5. List Marker Positions
    6. +
    7. List Styles in Shorthand
    8. +
    9. List Layout
    10. +
  2. +
  3. Generated Content +
      +
    1. Inserting Generated Content +
        +
      1. Generated Content and Run-In Content
      2. +
    2. +
    3. Specifying Content +
        +
      1. Inserting Attribute Values
      2. +
      3. Generated Quotes
      4. +
    4. +
    5. Counters +
        +
      1. Resetting and Incrementing
      2. +
      3. Using Counters
      4. +
      5. Counters and Scope
      6. +
    6. +
  4. +
  5. Conclusion
  6. +
+ + + diff --git a/counters2.html b/counters2.html new file mode 100644 index 0000000..8848709 --- /dev/null +++ b/counters2.html @@ -0,0 +1,113 @@ + + + +Untitled + + + + + +

Testing counters()

+ +

CSS relevant to counting:

+

+
+ +
    +
  1. "1" is expected +
      +
    1. "1.1" is expected
    2. +
    3. "1.2" is expected
    4. +
    +
  2. +
  3. "2" is expected
  4. +
  5. "3" is expected +
      +
    1. "3.1" is expected
    2. +
    3. "3.2" is expected
    4. +
    +
  6. +
  7. "4" is expected
  8. +
  9. "5" is expected +
      +
    1. "5.1" is expected
    2. +
    3. "5.2" is expected
    4. +
    +
  10. +
+ +
    +
  1. "1" is expected
  2. +
  3. "2" is expected +
      +
    1. "2.1" is expected +
        +
      1. "2.1.1" is expected
      2. +
      3. "2.1.2" is expected
      4. +
      +
    2. +
    3. "2.2" is expected +
        +
      1. "2.2.1" is expected
      2. +
      3. "2.2.2" is expected
      4. +
      5. "2.2.3" is expected
      6. +
      +
    4. +
    +
  4. +
  5. "3" is expected
  6. +
+ +
    +
  1. "1" is expected +
      +
    1. "1.1" is expected +
        +
      1. "1.1.1" is expected +
          +
        1. "1.1.1.1" is expected +
            +
          1. "1.1.1.1.1" is expected
          2. +
          +
        2. +
        +
      2. +
      +
    2. +
    +
  2. +
  3. "2" is expected +
      +
    1. "2.1" is expected +
        +
      1. "2.1.1" is expected +
          +
        1. "2.1.1.1" is expected +
            +
          1. "2.1.1.1.1" is expected
          2. +
          +
        2. +
        3. "2.1.1.2" is expected +
            +
          1. "2.1.1.2.1" is expected
          2. +
          3. "2.1.1.2.2" is expected
          4. +
          +
        4. +
        +
      2. +
      +
    2. +
    +
  4. +
+ + + diff --git a/countertest.html b/countertest.html new file mode 100644 index 0000000..fe137a2 --- /dev/null +++ b/countertest.html @@ -0,0 +1 @@ + Untitled
  1. a list item element
  2. a list item element
  3. a list item element
  4. a list item element
    1. a list item element
    2. a list item element
  5. a list item element
  6. a list item element
    1. a list item element
    2. a list item element
      1. a list item element
      2. a list item element
  7. a list item element
  8. a list item element

just a test

\ No newline at end of file diff --git a/css1/CWRU.gif b/css1/CWRU.gif new file mode 100755 index 0000000..e85bebc Binary files /dev/null and b/css1/CWRU.gif differ diff --git a/css1/NIST.gif b/css1/NIST.gif new file mode 100755 index 0000000..a8af50a Binary files /dev/null and b/css1/NIST.gif differ diff --git a/css1/W3C-rsrc-test.css b/css1/W3C-rsrc-test.css new file mode 100644 index 0000000..05a1813 --- /dev/null +++ b/css1/W3C-rsrc-test.css @@ -0,0 +1 @@ + /* a simple style sheets for W3C Resources */ BODY { font-family: Arial, sans-serif; /* font-size: 1em; */ /* ns linux */ background: white; color: black; margin: 2em 1em 2em 70px; background-image: url(W3Crsrc.gif); background-position: top left; background-attachment: fixed; background-repeat: no-repeat; } TH, TD { /* ns 4 */ font-family: Arial, sans-serif; /* font-size: 1em; */ /* ns linux */ } H1, H2, H3 { font-family: Tahoma, Verdana, "Myriad Web", Syntax, sans-serif; font-weight: normal; color: #0050B2; background: transparent; text-align: left; } H1 { font-size: 2em } H2 { font-size: 1.5em } H3 { font-size: 1.3em } .hide { display: none } DIV.head { margin-bottom: 1em } DIV.head H1 { margin-top: 3em } DIV.head H2 { font-size: 1.3em } DIV.head TABLE { margin: 2em } /* A { text-decoration: none; background: transparent; } */ A:link { color: #F30; background: transparent } A:visited { color: #363; background: transparent } A:active { color: #F30; background: transparent } A:hover { background: #FFA } PRE { margin-left: 2em } P { margin-top: 0.6em; margin-bottom: 0.6em; } DT, DD { margin-top: 0; margin-bottom: 0 } /* opera 3.50 */ DT { font-weight: bold } PRE { font-family: monospace } /* navigator 4*/ \ No newline at end of file diff --git a/css1/W3C.gif b/css1/W3C.gif new file mode 100755 index 0000000..97eb7c2 Binary files /dev/null and b/css1/W3C.gif differ diff --git a/css1/W3Crsrc.gif b/css1/W3Crsrc.gif new file mode 100755 index 0000000..deef0fe Binary files /dev/null and b/css1/W3Crsrc.gif differ diff --git a/css1/base.css b/css1/base.css new file mode 100644 index 0000000..84e3336 --- /dev/null +++ b/css1/base.css @@ -0,0 +1 @@ +BODY {color: black; background: #CCCCCC url(basebg.gif);} A:link {color: blue;} A:visited {color: #006600;} \ No newline at end of file diff --git a/css1/basebg.gif b/css1/basebg.gif new file mode 100755 index 0000000..26604e6 Binary files /dev/null and b/css1/basebg.gif differ diff --git a/css1/bg.gif b/css1/bg.gif new file mode 100755 index 0000000..a5cabb9 Binary files /dev/null and b/css1/bg.gif differ diff --git a/css1/crosshair.gif b/css1/crosshair.gif new file mode 100755 index 0000000..0e87532 Binary files /dev/null and b/css1/crosshair.gif differ diff --git a/css1/crosshair2.gif b/css1/crosshair2.gif new file mode 100755 index 0000000..5aebcc9 Binary files /dev/null and b/css1/crosshair2.gif differ diff --git a/css1/folder/lastlink.css b/css1/folder/lastlink.css new file mode 100644 index 0000000..eed92df --- /dev/null +++ b/css1/folder/lastlink.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(lastlinkimport.css); @import url(lastlinkimportmediascreen.css) screen; @import url(lastlinkimportmediatty.css) tty; /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .folderlastlinkimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/lastlinkimport.css b/css1/folder/lastlinkimport.css new file mode 100644 index 0000000..e2e7eea --- /dev/null +++ b/css1/folder/lastlinkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlastlinkimportimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/link.css b/css1/folder/link.css new file mode 100644 index 0000000..877240c --- /dev/null +++ b/css1/folder/link.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(linkimport.css); @import url(linkimportmediascreen.css) screen; @import url(linkimportmediatty.css) tty; /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .folderlink { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/linkimport.css b/css1/folder/linkimport.css new file mode 100644 index 0000000..90b167b --- /dev/null +++ b/css1/folder/linkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/linkmediaall.css b/css1/folder/linkmediaall.css new file mode 100644 index 0000000..76c9f1d --- /dev/null +++ b/css1/folder/linkmediaall.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediaall { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/linkmediascreen.css b/css1/folder/linkmediascreen.css new file mode 100644 index 0000000..755dd2c --- /dev/null +++ b/css1/folder/linkmediascreen.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediascreen { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/linkmediascreenprojection.css b/css1/folder/linkmediascreenprojection.css new file mode 100644 index 0000000..ed72e17 --- /dev/null +++ b/css1/folder/linkmediascreenprojection.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediascreenprojection { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/folder/linkmediatty.css b/css1/folder/linkmediatty.css new file mode 100644 index 0000000..55ee0be --- /dev/null +++ b/css1/folder/linkmediatty.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediatty { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/folder/sec64.css b/css1/folder/sec64.css new file mode 100644 index 0000000..dfe9e57 --- /dev/null +++ b/css1/folder/sec64.css @@ -0,0 +1 @@ +P.one {background: white url(redsqr.gif) center no-repeat;} \ No newline at end of file diff --git a/css1/folder/sec642.css b/css1/folder/sec642.css new file mode 100644 index 0000000..614c3a9 --- /dev/null +++ b/css1/folder/sec642.css @@ -0,0 +1 @@ +P.two {background: white url(redsqr.gif) center no-repeat;} \ No newline at end of file diff --git a/css1/folder/styleimport.css b/css1/folder/styleimport.css new file mode 100644 index 0000000..b61c2c1 --- /dev/null +++ b/css1/folder/styleimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderstyleimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/hblank1.gif b/css1/hblank1.gif new file mode 100755 index 0000000..2f862fb Binary files /dev/null and b/css1/hblank1.gif differ diff --git a/css1/hblank2.gif b/css1/hblank2.gif new file mode 100755 index 0000000..d82a7d1 Binary files /dev/null and b/css1/hblank2.gif differ diff --git a/css1/horiz_description.gif b/css1/horiz_description.gif new file mode 100755 index 0000000..2d9a4ff Binary files /dev/null and b/css1/horiz_description.gif differ diff --git a/css1/horiz_pixel_ruler.gif b/css1/horiz_pixel_ruler.gif new file mode 100755 index 0000000..26ee74b Binary files /dev/null and b/css1/horiz_pixel_ruler.gif differ diff --git a/css1/imptest1.css b/css1/imptest1.css new file mode 100644 index 0000000..af43571 --- /dev/null +++ b/css1/imptest1.css @@ -0,0 +1 @@ +LI.three {color: green;} \ No newline at end of file diff --git a/css1/imptest1a.css b/css1/imptest1a.css new file mode 100644 index 0000000..8f341fb --- /dev/null +++ b/css1/imptest1a.css @@ -0,0 +1 @@ +LI.threea {color: purple;} \ No newline at end of file diff --git a/css1/imptest2.css b/css1/imptest2.css new file mode 100644 index 0000000..5e73d50 --- /dev/null +++ b/css1/imptest2.css @@ -0,0 +1 @@ +P.five {color: red;} \ No newline at end of file diff --git a/css1/index.html b/css1/index.html new file mode 100644 index 0000000..506bae8 --- /dev/null +++ b/css1/index.html @@ -0,0 +1 @@ + CSS1 Test Suite

W3C CSS1 Test Suite

The CSS1 Test Suite is provided as a way for vendors and page authors to test their browser's conformance to the CSS1 specification. This test suite is organized around individual properties of Cascading Style Sheets, Level 1 (CSS1). In order to use it most effectively, you will NEED to make sure that you have completely read and understood the contents of Prologue before you start testing any user agent.

For each property, there is at least one page which tests the property's values in various combinations, using HTML 4.0 markup. The test pages are broken out into a number of sections which reflect the structure of the CSS1 specification itself, in addition to a Prologue and a few appendicies.

Table of Contents


Feedback regarding the CSS1 Test Suite should be sent to css-test@w3.org.

The CSS1 Test Suite is a joint effort of the World Wide Web Consortium, the National Insititue of Standards and Technology, and Case Western Reserve University.  W3C  NIST  CWRU
\ No newline at end of file diff --git a/css1/index.html~ b/css1/index.html~ new file mode 100755 index 0000000..bf4f346 --- /dev/null +++ b/css1/index.html~ @@ -0,0 +1,68 @@ + + + +CSS1 Test Suite + + + + + + +

W3C CSS1 Test Suite

+ +

+The CSS1 Test Suite is provided as a way for vendors and page authors to test their browser's conformance to the CSS1 specification. This test suite is organized around individual properties of Cascading Style Sheets, Level 1 (CSS1). In order to use it most effectively, you will NEED to make sure that you have completely read and understood the contents of Prologue before you start testing any user agent. +

+

+For each property, there is at least one page which tests the property's values in various combinations, using HTML 4.0 markup. The test pages are broken out into a number of sections which reflect the structure of the CSS1 specification itself, in addition to a Prologue and a few appendicies. +

+ +

Table of Contents

+ + + + + + +
+ +

+Feedback regarding the CSS1 Test Suite should be sent to css-test@w3.org. +

+ + + + + + +
+The CSS1 Test Suite is a joint effort of the World Wide Web Consortium, the National Insititue of Standards and Technology, and Case Western Reserve University. + + W3C + NIST + CWRU +
+ + diff --git a/css1/lastlink.css b/css1/lastlink.css new file mode 100644 index 0000000..4514384 --- /dev/null +++ b/css1/lastlink.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(lastlinkimport.css); @import url(lastlinkimportmediascreen.css) screen; @import url(lastlinkimportmediatty.css) tty; @import url(folder/lastlink.css); /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .lastlink { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css1/lastlinkimport.css b/css1/lastlinkimport.css new file mode 100644 index 0000000..aa98706 --- /dev/null +++ b/css1/lastlinkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .lastlinkimport { font-weight: bold; color: green; background: silver none; } .folderlastlinkimportimport { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/link.css b/css1/link.css new file mode 100644 index 0000000..9ca1294 --- /dev/null +++ b/css1/link.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(linkimport.css); @import url(linkimportmediascreen.css) screen; @import url(linkimportmediatty.css) tty; /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .link { font-weight: bold; color: green; background: silver none; } .folderlink { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linkimport.css b/css1/linkimport.css new file mode 100644 index 0000000..70dfcff --- /dev/null +++ b/css1/linkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .linkimport { font-weight: bold; color: green; background: silver none; } .folderlinkimport { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linkmediaall.css b/css1/linkmediaall.css new file mode 100644 index 0000000..40763d7 --- /dev/null +++ b/css1/linkmediaall.css @@ -0,0 +1 @@ +/*Import Test File*/ .linkmediaall { font-weight: bold; color: green; background: silver none; } .folderlinkmediaall { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linkmediascreen.css b/css1/linkmediascreen.css new file mode 100644 index 0000000..c992f24 --- /dev/null +++ b/css1/linkmediascreen.css @@ -0,0 +1 @@ +/*Import Test File*/ .linkmediascreen { font-weight: bold; color: green; background: silver none; } .folderlinkmediascreen { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linkmediascreenprojection.css b/css1/linkmediascreenprojection.css new file mode 100644 index 0000000..19d5dcb --- /dev/null +++ b/css1/linkmediascreenprojection.css @@ -0,0 +1 @@ +/*Import Test File*/ .linkmediascreenprojection { font-weight: bold; color: green; background: silver none; } .folderlinkmediascreenprojection { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linkmediatty.css b/css1/linkmediatty.css new file mode 100644 index 0000000..b5b2f0e --- /dev/null +++ b/css1/linkmediatty.css @@ -0,0 +1 @@ +/*Import Test File*/ .linkmediatty { color: red; background: yellow none; } .folderlinkmediatty { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/linktest.css b/css1/linktest.css new file mode 100644 index 0000000..95342da --- /dev/null +++ b/css1/linktest.css @@ -0,0 +1 @@ +.one {text-decoration: underline;} \ No newline at end of file diff --git a/css1/linktest2.css b/css1/linktest2.css new file mode 100644 index 0000000..da3c2d8 --- /dev/null +++ b/css1/linktest2.css @@ -0,0 +1 @@ +P.two {text-decoration: underline;} \ No newline at end of file diff --git a/css1/orancirc.gif b/css1/orancirc.gif new file mode 100755 index 0000000..6bdd68b Binary files /dev/null and b/css1/orancirc.gif differ diff --git a/css1/oransqr.gif b/css1/oransqr.gif new file mode 100755 index 0000000..bea5f04 Binary files /dev/null and b/css1/oransqr.gif differ diff --git a/css1/redsqr.gif b/css1/redsqr.gif new file mode 100644 index 0000000..1af1c0e Binary files /dev/null and b/css1/redsqr.gif differ diff --git a/css1/sec00.htm b/css1/sec00.htm new file mode 100755 index 0000000..52354ee --- /dev/null +++ b/css1/sec00.htm @@ -0,0 +1 @@ + CSS1 Test Suite: Prologue

CSS1 Test Suite: Prologue


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec01.htm b/css1/sec01.htm new file mode 100755 index 0000000..09df8e9 --- /dev/null +++ b/css1/sec01.htm @@ -0,0 +1 @@ + CSS1 Test Suite: Configuring Your System

CSS1 Test Suite: Configuring Your System


[Previous] [Next] [Section] [Contents] [Specification]

In the first place, you will need to make sure that your browser is configured to pay attention to style sheets at all. This is typically done by finding an entry in your preferences dialog which says something like "Enable style sheets" and making sure the appropriate box is checked. You may have to enable other features as well. Please read the article Enabling Your Style Sheets if you need further information.

You will also need to be using a browser which is able to load LINKed style sheets. Every test page in the suite uses the style sheet base.css. This provides a consistent look to the pages, and so when something overrides the base style sheet, you'll know it. If the current page has a white background with a light gray grid, then the base stylesheet has been imported via the LINK element. If not, you should double-check to make sure that you do not have a user stylesheet set (see next section).

Disabling User-Defined Style Sheets

Furthermore, you will need to make sure that you are not using a user-defined style sheet. If you have set up your own style sheet and have your browser configured to use it, then you will need to disable this feature before you start.

Under Internet Explorer 4.x for Windows, you should take the following steps:

  1. Select "Internet Options..." under the "View" menu.
  2. Select the "Accessibility..." button near the bottom of the Internet Options dialog.
  3. Check to make sure that, under "User Style Sheet," the checkbox is not checked. There may be a file listed under it, although you're probably safer if there isn't.

As of this writing, user-defined stylesheets are not supported by any other popular browser.

Units and Monitor Settings

Some of the CSS1 Test Suite's test pages use "real-world" lengths; that is, they are units such as inches or centimeters. However, your computer may or may not have the slightest idea how far a "centimeter" really is, in terms of the number of pixels. On Windows95/98, using some display drivers, it is possible to find out by taking the following steps:

  1. Open your Display Settings.
  2. Select the "Settings" tab.
  3. Select the "Advanced" button near the bottom.
  4. Select the "Fonts" tab.
  5. You should now see a ruler.
  6. Hold a (physical) ruler up to the screen, and click and drag the screen ruler to resize it until it matches the physical one.
  7. Click "OK".

Under WindowsNT and the MacOS, the system should have already determined real-world distances for your particular monitor and its settings. It is assumed that the user agent will take advantage of this, although it's always a good idea to check for yourself, using an actual ruler.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec02.htm b/css1/sec02.htm new file mode 100755 index 0000000..af739dd --- /dev/null +++ b/css1/sec02.htm @@ -0,0 +1 @@ + CSS1 Test Suite: Understanding the Test Pages

CSS1 Test Suite: Understanding the Test Pages


[Previous] [Next] [Section] [Contents] [Specification]

Each page has a number of test statements, each of which describes a given effect which should be seen. If the effects you see do not match the description given, then there is a problem with your browser's CSS support. The test statements on each page are duplicated inside a one-cell table. This was done to provide at least rudimentary testing of conformance within tables, which are know to be a weak point in many CSS implementations.

Above the test statements, the style declarations for that specific page are displayed. There are also navigation links at the top and bottom of the page. The top of the page will look something like this:

CSS1 Test Suite: 5.2.4 font-variant


[Next] [Previous] [Section] [Contents] [Reference Image] [Specification]

The first line is not only the page's title, but also includes the name of the property being tested on that page, and its section number in the CSS1 specification. The six links under the title are, respectively:

Finally, it is assumed that visual user agents are being tested against this test suite, and the test statements are written with this assumption in mind. There are currently no provisions given for text-only agents, although these should still be testable, or for speaking browsers, which are beyond the scope of CSS1 in any case.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec03.htm b/css1/sec03.htm new file mode 100755 index 0000000..dc9b2ec --- /dev/null +++ b/css1/sec03.htm @@ -0,0 +1 @@ + CSS1 Test Suite: CSS1 vs. CSS2

CSS1 Test Suite: CSS1 vs. CSS2


[Previous] [Next] [Section] [Contents] [Specification]

This page is intended to give some idea of how much support your user agent has for both CSS1 and CSS2. These are not intended to be normative tests, but instead indicators of what to expect further on in the test, and where potential confusion may arise. Note that just because a user agent passes the following tests, it cannot be assumed to have full support for either CSS1 or CSS2.

Following are some CSS1 tests:

If your user agent did not display the above list as described, or seemed to have trouble with some of the display, then it does not have complete CSS1 support. (Even if it did render the list correctly, it may not have complete CSS1 support.)

Following are some CSS2 tests:

If your user agent did not display the above list as described, or seemed to have trouble with some of the display, then it does not have complete CSS2 support. (Even if it did render the list correctly, it may not have complete CSS2 support.)


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec04.htm b/css1/sec04.htm new file mode 100755 index 0000000..31224d6 --- /dev/null +++ b/css1/sec04.htm @@ -0,0 +1 @@ + CSS1 Test Suite: LINK and @import

CSS1 Test Suite: LINK and @import


[Previous] [Next] [Section] [Contents] [Specification]

The style declaration applied in each following case is: {font-weight: bold; color: green; background: silver none;}.

1. Inline style (style attribute).

3. Linked stylesheet with media attribute set to all.

4. Linked stylesheet with media attribute set to screen.

5. Linked stylesheet with media attribute set to screen, projection.

6. Stylesheet imported by linked stylesheet.

7. Embedded stylesheet (style element).

8. Stylesheet imported by embedded stylesheet.

10. Linked stylesheet in another folder with media attribute set to all.

11. Linked stylesheet in another folder with media attribute set to screen.

12. Linked stylesheet in another folder with media attribute set to screen, projection.

13. Stylesheet in another folder imported by linked stylesheet in that same other folder.

14. Stylesheet in another folder imported by embedded stylesheet.

16. Stylesheet imported by last linked stylesheet.

17. Stylesheet in another folder imported by last linked stylesheet.

18. Stylesheet in another folder imported by stylesheet in that same folder imported by last linked stylesheet in this folder.

NOTE: The following should be red only if the browser is displaying the results on a tty. Normally, these should be uncoloured (not green). Note, though, that results for numbers 19 and 20 are irrelevant if any of the tests 1 to 18 are either uncolored or red.

19. Linked stylesheet with media attribute set to tty.

20. Linked stylesheet in another folder with media attribute set to tty.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec10.htm b/css1/sec10.htm new file mode 100755 index 0000000..df212b2 --- /dev/null +++ b/css1/sec10.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.0 Basic Concepts

CSS1 Test Suite: 1.0 Basic Concepts


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec11.htm b/css1/sec11.htm new file mode 100755 index 0000000..032dbe7 --- /dev/null +++ b/css1/sec11.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.1 Containment in HTML

CSS1 Test Suite: 1.1 Containment in HTML


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" href="linktest.css" title="Default SS">
<LINK rel="alternate stylesheet" type="text/css" href="linktest2.css" title="Alternate SS">
@import url(imptest1.css);
@import "imptest1a.css";
UL {color: red;}
.four {color: purple;}
@import url(imptest2.css);
<!--
P.six {color: green;}
-->

This sentence should be underlined due to the linked style sheet linktest.css, the reference to which is shown above.

This sentence should NOT be underlined due to the linked style sheet linktest2.css, unless the external style sheet "Alternate SS" has been selected via the user agent.

This sentence should be purple, and it doesn't have a terminating paragraph tag.

  1. This list should NOT be purple.
  2. It should, instead, be black.
  3. If it IS purple, then the browser hasn't correctly parsed the preceding paragraph.

This sentence should be black. If it is red, then the browser has inappropriately imported the styles from the file imptest2.css (see section 3.0 of the CSS1 specification for more details).

This paragraph should be green.

TABLE Testing Section
 

This sentence should be underlined due to the linked style sheet linktest.css, the reference to which is shown above.

This sentence should NOT be underlined due to the linked style sheet linktest2.css, unless the external style sheet "Alternate SS" has been selected via the user agent.

  • This sentence should be green due to an imported style sheet [@import url(imptest1.css);].
  • This sentence should be purple due to an imported style sheet [@import "imptest1a.css"].
  • This sentence should be green thanks to the STYLE attribute [STYLE="color: green;"].

This sentence should be purple, and it doesn't have a terminating paragraph tag.

  1. This list should NOT be purple.
  2. It should, instead, be black.
  3. If it IS purple, then the browser hasn't correctly parsed the preceding paragraph.

This sentence should be black. If it is red, then the browser has inappropriately imported the styles from the file imptest2.css (see section 3.0 of the CSS1 specification for more details).

This paragraph should be green.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec12.htm b/css1/sec12.htm new file mode 100755 index 0000000..42113fe --- /dev/null +++ b/css1/sec12.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.2 Grouping

CSS1 Test Suite: 1.2 Grouping


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one, .two, .three {color: green;}


This sentence should be green.

This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec13.htm b/css1/sec13.htm new file mode 100755 index 0000000..257f385 --- /dev/null +++ b/css1/sec13.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.3 Inheritance

CSS1 Test Suite: 1.3 Inheritance


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {color: green;}
H3 {color: blue;}
EM {color: purple;}
.one {font-style: italic;}
.two {text-decoration: underline;}
#two {color: navy;}
.three {color: purple;}

This sentence should show blue and purple.

This sentence should be blue throughout.

This should be green except for the emphasized words, which should be purple.

This should be blue and underlined.

This sentence should be underlined, including this part, this part, this part, and this part.

This sentence should also be underlined, as well as dark blue (navy), including this part.

This sentence should be purple, including this part and this part (which is spanned).

TABLE Testing Section
 

This sentence should show blue and purple.

This sentence should be blue throughout.

This should be green except for the emphasized words, which should be purple.

This should be blue and underlined.

This sentence should be underlined, including this part, this part, this part, and this part.

This sentence should also be underlined, as well as dark blue (navy), including this part.

This sentence should be purple, including this part and this part (which is spanned).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec14.htm b/css1/sec14.htm new file mode 100755 index 0000000..f3ed822 --- /dev/null +++ b/css1/sec14.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.4 Class as selector

CSS1 Test Suite: 1.4 Class as selector


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {color: green;}
.a1 {color: green;}
P.two {color: purple;}

This sentence should be green.

This sentence should be green.

This sentence should be purple.

This sentence should NOT be purple.
TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This sentence should be purple.

This sentence should NOT be purple.
  • This sentence should NOT be purple.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec15.htm b/css1/sec15.htm new file mode 100755 index 0000000..d897b90 --- /dev/null +++ b/css1/sec15.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.5 ID as selector

CSS1 Test Suite: 1.5 ID as selector


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

#one {color: green;}
#a1 {color: green;}
P#two {color: blue;}
P#three {color: purple;}

This sentence should be green.

This sentence should be green.

This paragraph should be blue [ID="two"].

This sentence should NOT be blue [PRE ID="two"].
This sentence should be black [PRE ID="three"].
TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This paragraph should be blue [ID="two"].

This sentence should NOT be blue [PRE ID="two"].
This sentence should be black [PRE ID="three"].
  • This sentence should NOT be blue.
  • This sentence should NOT be purple.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec16.htm b/css1/sec16.htm new file mode 100755 index 0000000..25e9e44 --- /dev/null +++ b/css1/sec16.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.6 Contextual selectors

CSS1 Test Suite: 1.6 Contextual selectors


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {color: navy; font-family: serif;}
HTML BODY TABLE P {color: purple; font-family: sans-serif;}
EM, UL LI LI {color: green;}


This sentence should be navy serif in the first half of the page, but purple and sans-serif in the table.

This sentence should be normal for its section, except for the last word, which should be green.

TABLE Testing Section
 

This sentence should be navy serif in the first half of the page, but purple and sans-serif in the table.

This sentence should be normal for its section, except for the last word, which should be green.

  • Hello. The first "hello" should be green, but this part should be black.
    • This should be green.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec17.htm b/css1/sec17.htm new file mode 100755 index 0000000..866779d --- /dev/null +++ b/css1/sec17.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 1.7 Comments

CSS1 Test Suite: 1.7 Comments


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

/* This is a CSS1 comment. */
.one {color: green;} /* Another comment */
/* The following should not be used:
.two {color: red;} */
.three {color: green; /* color: red; */}
/**
.four {color: red;} */
.five {color: green;}
/**/
.six {color: green;}
/*********/
.seven {color: green;}
/* a comment **/
.eight {color: green;}


This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec20.htm b/css1/sec20.htm new file mode 100755 index 0000000..ce077f8 --- /dev/null +++ b/css1/sec20.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.0 Pseudo-Classes and Pseudo-Elements

CSS1 Test Suite: 2.0 Pseudo-Classes and Pseudo-Elements


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec21.htm b/css1/sec21.htm new file mode 100755 index 0000000..17be358 --- /dev/null +++ b/css1/sec21.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.1 anchor

CSS1 Test Suite: 2.1 anchor


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

A {color: green;}
A:link {color: purple;}
A:visited {color: lime;}
A:active {color: maroon;}
#one {color: #006600;}


The following anchors should appear as described; none of them should be red.

The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A element are applied to them under CSS1. It also should NOT turn maroon when clicked upon.

TABLE Testing Section
 

The following anchors should appear as described; none of them should be red.

The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A element are applied to them under CSS1. It also should NOT turn maroon when clicked upon.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec23.htm b/css1/sec23.htm new file mode 100755 index 0000000..2d0720c --- /dev/null +++ b/css1/sec23.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.3 first-line

CSS1 Test Suite: 2.3 first-line


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {color: green;}
.two:first-line {font-size: 200%;}
.three:first-line {font-variant: small-caps;}


The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line.

TABLE Testing Section
 

The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec24.htm b/css1/sec24.htm new file mode 100755 index 0000000..be5e077 --- /dev/null +++ b/css1/sec24.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.4 first-letter

CSS1 Test Suite: 2.4 first-letter


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-letter {color: maroon;}
.two:first-letter {font-size: 200%;}
P.three:first-letter {font-size: 350%;}


The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 3.5 times bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended.

TABLE Testing Section
 

The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 3.5 times bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec25.htm b/css1/sec25.htm new file mode 100755 index 0000000..b85c37e --- /dev/null +++ b/css1/sec25.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.5 Pseudo-elements in Selectors

CSS1 Test Suite: 2.5 Pseudo-elements in Selectors


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {font-weight: bold;}
P.two:first-line {color: green;}
P:first-line.three {color: red;}


The first line of this paragraph, and only that line, should be boldfaced. This test is included simply to establish a baseline for the following tests, since if this test fails, then the rest of the tests on this page are expected to fail as well.

The first line of this paragraph, and only that line, should be boldfaced and green, thanks to its selector. If this is not the case, then the user agent may have failed to properly parse the selector, or it may simply not support the :first-line pseudo-element.

The first line of this paragraph, and only that line, should be boldfaced. If it is red, then the user agent has violated the specification in allowing pseudo-elements at a point other than the end of a selector. If neither is the case, then the user agent has correctly ignored the incorrect selector, but has suppressed other styles which are valid, and therefore must be considered to have failed the test.

TABLE Testing Section
 

The first line of this paragraph, and only that line, should be boldfaced. This test is included simply to establish a baseline for the following tests, since if this test fails, then the rest of the tests on this page are expected to fail as well.

The first line of this paragraph, and only that line, should be boldfaced and green, thanks to its selector. If this is not the case, then the user agent may have failed to properly parse the selector, or it may simply not support the :first-line pseudo-element.

The first line of this paragraph, and only that line, should be boldfaced. If it is red, then the user agent has violated the specification in allowing pseudo-elements at a point other than the end of a selector. If neither is the case, then the user agent has correctly ignored the incorrect selector, but has suppressed other styles which are valid, and therefore must be considered to have failed the test.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec26.htm b/css1/sec26.htm new file mode 100755 index 0000000..2b655c2 --- /dev/null +++ b/css1/sec26.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 2.6 Multiple Pseudo-Elements

CSS1 Test Suite: 2.6 Multiple Pseudo-Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {color: green;}
P:first-letter {color: maroon;}
.two:first-line {font-size: 200%;}
.two:first-letter {font-size: 350%;}
P.three:first-letter {font-size: 350%;}
P.three:first-line {font-variant: small-caps;}


The first letter of this paragraph, and only that one, should be maroon (dark red), while the entire first line should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be 350% bigger than the rest of the first line of this paragraph and maroon (dark red), while the entire first line should be 200% bigger than normal and green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon (dark red). Note that the inclusion of both the quotation mark and the 'W' in the first-letter style is not required under CSS1, but it is recommended. In addition, the entire first line should be in a small-caps font and green.

TABLE Testing Section
 

The first letter of this paragraph, and only that one, should be maroon (dark red), while the entire first line should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be 350% bigger than the rest of the first line of this paragraph and maroon (dark red), while the entire first line should be 200% bigger than normal and green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon (dark red). Note that the inclusion of both the quotation mark and the 'W' in the first-letter style is not required under CSS1, but it is recommended. In addition, the entire first line should be in a small-caps font and green.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec30.htm b/css1/sec30.htm new file mode 100755 index 0000000..56c5a50 --- /dev/null +++ b/css1/sec30.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 3.0 The Cascade

CSS1 Test Suite: 3.0 The Cascade


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec31.htm b/css1/sec31.htm new file mode 100755 index 0000000..9c7abe1 --- /dev/null +++ b/css1/sec31.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 3.1 important

CSS1 Test Suite: 3.1 important


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {color: green ! important;}
P {color: red;}
P#id1 {color: purple;}


This paragraph should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet.

This paragraph should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than delcarations which use ID selectors.

This paragraph should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.

TABLE Testing Section
 

This paragraph should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet.

This paragraph should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than delcarations which use ID selectors.

This paragraph should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec32.htm b/css1/sec32.htm new file mode 100755 index 0000000..5653aa2 --- /dev/null +++ b/css1/sec32.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 3.2 Cascading Order

CSS1 Test Suite: 3.2 Cascading Order


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" HREF="linktest.css">
LI {color: purple;}
UL LI {color: blue;}
UL LI LI {color: gray;}
LI.red {color: green;}
UL LI.mar {color: #660000;}
UL LI#gre {color: green;}
.test {color: blue;}
.test {color: purple;}
.one {text-decoration: line-through;}


This sentence should be blue (STYLE attr.).

This sentence should be purple [class="test"].

This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported).

TABLE Testing Section
 
  • This list item should be blue...
  • ...and so should this; neither should be purple.
    • This list item should be gray...
    • ...as should this....
    • ...but this one should be green.
  • This ought to be dark red...
  • ...this green...
  • ...and this blue.

This sentence should be blue (STYLE attr.).

This sentence should be purple [class="test"].

This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec40.htm b/css1/sec40.htm new file mode 100755 index 0000000..a0f7a09 --- /dev/null +++ b/css1/sec40.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.0 Formatting Model

CSS1 Test Suite: 4.0 Formatting Model


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec411.htm b/css1/sec411.htm new file mode 100755 index 0000000..922d265 --- /dev/null +++ b/css1/sec411.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.1.1 Vertical Formatting

CSS1 Test Suite: 4.1.1 Vertical Formatting


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {margin-bottom: 2cm; padding-bottom: 0;}
P.two {margin-top: 2cm; padding-top: 0;}
P.three {margin-top: 0; padding-top: 0;}
P.four {margin-top: -1cm; margin-bottom: 0;
        padding-top: 0; padding-bottom: 0;}
DIV.five {margin-top: 1cm; margin-bottom: 1cm;
          padding-top: 1cm; padding-bottom: 0;}
P.six {margin-top: 1cm; margin-bottom: 1cm;
       padding-top: 0; padding-bottom: 0;}
P.seven {margin-top: 1cm; padding-top: 0;}
P.eight {margin-bottom: -1cm; padding-bottom: 2cm;}
P.nine {margin-top: -1cm; padding-top: 1cm;
        padding-bottom: 0; margin-bottom: 1cm;}
P.ten {margin-top: 1cm;padding-top: 0;
       float: left;width: 50%;}
P.eleven {margin-top: 1cm; padding-top: 0; clear: none;}
P.twelve {margin-bottom: 0; padding-bottom: 1cm; clear: both;}
P.thirteen {margin-top: 0; padding-top: 1cm;}
TABLE {clear: both;}


There should be a two-centimeter margin between this paragraph and the next, because adjacent vertical margins should collapse to the maximum of the margins.

This is another paragraph.

There should be a two-centimeter margin between this paragraph and the next.

This is another paragraph.

There should be a one-centimeter margin between this paragraph and the next, because when there is one negative margin, the two margins should be added (the minus sign should be kept).

This is another paragraph.

There should be three centimeters between this text and the text above, but only one centimeter between this text and the text below, because vertical margins of nested elements should collapse only if there is no border or padding between the margins.

This is more text.

There should be two centimeters between this paragraph and the one below, because negative margins collapse to a negative margin with the largest absolute value of the margins collapsed.

This is a paragraph, which I should make very long so that you can easily see how much space there is between it and the one below it and to the right.

There should be two centimeters between this paragraph and the one above it, since margins do not collapse on floating elements.

There should be one centimeter between this paragraph and the (non-floating) one above it, since the float should not effect the paragraph spacing.

There should be two centimeters of padding between this paragraph and the one below. Padding does not collapse, and there is 1cm of padding on each side.

This is the next paragraph.

TABLE Testing Section
 

There should be a two-centimeter margin between this paragraph and the next, because adjacent vertical margins should collapse to the maximum of the margins.

This is another paragraph.

There should be a two-centimeter margin between this paragraph and the next.

This is another paragraph.

There should be a one-centimeter margin between this paragraph and the next, because when there is one negative margin, the two margins should be added (the minus sign should be kept).

This is another paragraph.

There should be three centimeters between this text and the text above, but only one centimeter between this text and the text below, because vertical margins of nested elements should collapse only if there is no border or padding between the margins.

This is more text.

There should be two centimeters between this paragraph and the one below, because negative margins collapse to a negative margin with the largest absolute value of the margins collapsed.

This is a paragraph, which I should make very long so that you can easily see how much space there is between it and the one below it and to the right.

There should be two centimeters between this paragraph and the one above it, since margins do not collapse on floating elements.

There should be one centimeter between this paragraph and the (non-floating) one above it, since the float should not effect the paragraph spacing.

There should be two centimeters of padding between this paragraph and the one below. Padding does not collapse, and there is 1cm of padding on each side.

This is the next paragraph.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec412.htm b/css1/sec412.htm new file mode 100755 index 0000000..f6fd170 --- /dev/null +++ b/css1/sec412.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.1.2 Horizontal Formatting

CSS1 Test Suite: 4.1.2 Horizontal Formatting


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.ruler {padding: 0px; margin: 0px; border-width: 0px;}
P#ruled {background-color: aqua; width: 400px;
     border-style: solid; border-color: silver;
     border-top-width: 0px; border-bottom-width: 0px;
     border-left-width: 40px; border-right-width: 40px;
     padding-left: 40px; padding-right: 40px;
     margin-top: 0px; margin-bottom: 0px; margin-left: 40px; margin-right: 40px;}

P.one {margin-left: 10px;}
DIV.two {margin-left: 10px;}
P.three {margin-left: 0; width: 50%; margin-right: auto;
         background-color: gray;}
P.four {margin-left: auto; width: 50%; margin-right: auto;
        background-color: gray;}
P.five {margin-left: auto; width: 50%; margin-right: 0;
        background-color: gray;}
P.six {margin-left: auto; width: auto; margin-right: 0;
       background-color: gray; }
P.seven {margin-left: 0; width: auto; margin-right: auto;
         background-color: gray;}
P.eight {margin-left: auto; width: auto; margin-right: auto;
         background-color: gray;}
P.nine {padding-left: auto; padding-right: auto; margin-left: 0; margin-right: 0;
        width: 50%; background-color: gray;}
P.ten {margin-left: auto; width: 100%; margin-right: auto;
       background-color: gray;}


[ruler]

This text is inside a P element. The border, padding, and margins for this paragraph should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

[labels]

This paragraph should be indented ten pixels.

This paragraph should be indented twenty pixels, since horizontal margins do not collapse.

This element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified.

Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport.

Because this paragraph has width 100%, the auto margins become zero, so it should not be centered.

TABLE Testing Section
 
[ruler]

This text is inside a P element. The border, padding, and margins for this paragraph should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

[labels]

This paragraph should be indented ten pixels.

This paragraph should be indented twenty pixels, since horizontal margins do not collapse.

This element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified.

Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport.

Because this paragraph has width 100%, the auto margins become zero, so it should not be centered.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec414.htm b/css1/sec414.htm new file mode 100755 index 0000000..bb58b2f --- /dev/null +++ b/css1/sec414.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.1.4 Floating Elements

CSS1 Test Suite: 4.1.4 Floating Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

HR.minor {clear: both; width: 5%;}
HR.major {clear: both; width: 75%; margin: 1.5em;}
DIV {border: 5px solid purple; padding: 0; margin: 0.125em;}
P.left, P.right {width: 10em; padding: 1em; margin: 0;
   border: 1px solid lime; background-color: silver;}
IMG.left, IMG.right {margin: 0; border: 3px solid black;}
.left {float: left;}
.right {float: right;}


On this test page, each test is performed once with floating paragraphs, and then again with floating images. Other than the substitution of images for pargraphs, the structure of the test is exactly the same, including the direction of the floats.


This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV.

This is the first left-floating paragraph.

This is the second left-floating paragraph.

This is the third left-floating paragraph.

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated elements should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated images should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is a right-floating paragraph (first in source).

This is a left-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating box should not be higher than the top of the right-floating box.

This is text within the DIV. The floating images within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating image should not be higher than the top of the right-floating image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated element.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be,*

This is a left-floating paragraph (third in source).

at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. *

This is a left-floating paragraph (fourth in source).

In order to mark these points clearly, an asterisk has been inserted just before each floated element. If a line has room for a floated element, then the element should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, * at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. * In order to mark these points clearly, an asterisk has been inserted just before each floated image. If a line has room for a floated image, then the image should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is *

This is a left-floating paragraph (first in source).

*

This is a right-floating paragraph (second in source).

text within the DIV. Under CSS1, the left floating element should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. Similarly, the right floating element should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. The text of the DIV element should flow between and under the two floating elements. The two asterisk characters mark the insertion points of the floating elements. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

This is * * text within the DIV. Under CSS1, the left floating image should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. Similarly, the right floating image should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. The text of the DIV element should flow between and under the two floating image. The two asterisk characters mark the insertion points of the floating image. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

TABLE Testing Section
 

On this test page, each test is performed once with floating paragraphs, and then again with floating images. Other than the substitution of images for pargraphs, the structure of the test is exactly the same, including the direction of the floats.


This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV.

This is the first left-floating paragraph.

This is the second left-floating paragraph.

This is the third left-floating paragraph.

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated elements should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated images should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is a right-floating paragraph (first in source).

This is a left-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating box should not be higher than the top of the right-floating box.

This is text within the DIV. The floating images within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating image should not be higher than the top of the right-floating image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated element.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be,*

This is a left-floating paragraph (third in source).

at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. *

This is a left-floating paragraph (fourth in source).

In order to mark these points clearly, an asterisk has been inserted just before each floated element. If a line has room for a floated element, then the element should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, * at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. * In order to mark these points clearly, an asterisk has been inserted just before each floated image. If a line has room for a floated image, then the image should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is *

This is a left-floating paragraph (first in source).

*

This is a right-floating paragraph (second in source).

text within the DIV. Under CSS1, the left floating element should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. Similarly, the right floating element should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. The text of the DIV element should flow between and under the two floating elements. The two asterisk characters mark the insertion points of the floating elements. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

This is * * text within the DIV. Under CSS1, the left floating image should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. Similarly, the right floating image should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. The text of the DIV element should flow between and under the two floating image. The two asterisk characters mark the insertion points of the floating image. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec42.htm b/css1/sec42.htm new file mode 100755 index 0000000..55cbf84 --- /dev/null +++ b/css1/sec42.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.2 Inline Elements

CSS1 Test Suite: 4.2 Inline Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {line-height: 200%;}
SPAN.two {border-style: solid; border-width: 10px; border-color: red;
          padding: 2pt; margin: 30pt;}
P.three {font-size: 10pt; line-height: 12pt;}
SPAN.four {border-style: solid; border-width: 12px; border-color: red;
          padding: 2pt;}


This is a paragraph that has a very long span in it, and the span has a 10px red border separated from the span by 2pt, and a margin of 30pt. The padding and border should be present on all sides of the span (although vertical lines should appear only at the beginning and the end of the whole span, not on each line). The padding, border, and margin should all be noticeable at the beginning and end of the span. However, the line height should not be changed by any of them, so the margin should be unnoticeable and the border should overlap text on other lines. The line spacing in the whole paragraph should be 200% of the font size.

This is a paragraph that has a very long span in it, and the span has a 12px red border separated from the span by 2pt of padding (the difference between the line-height and the font-size), which should overlap with the lines of text above and below the span, since the padding and border should not effect the line height. The span's border should have vertical lines only at the beginning and end of the whole span, not on each line. The line spacing in the whole paragraph should be 12pt, with font-size 10pt.

TABLE Testing Section
 

This is a paragraph that has a very long span in it, and the span has a 10px red border separated from the span by 2pt, and a margin of 30pt. The padding and border should be present on all sides of the span (although vertical lines should appear only at the beginning and the end of the whole span, not on each line). The padding, border, and margin should all be noticeable at the beginning and end of the span. However, the line height should not be changed by any of them, so the margin should be unnoticeable and the border should overlap text on other lines. The line spacing in the whole paragraph should be 200% of the font size.

This is a paragraph that has a very long span in it, and the span has a 12px red border separated from the span by 2pt of padding (the difference between the line-height and the font-size), which should overlap with the lines of text above and below the span, since the padding and border should not effect the line height. The span's border should have vertical lines only at the beginning and end of the whole span, not on each line. The line spacing in the whole paragraph should be 12pt, with font-size 10pt.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec43.htm b/css1/sec43.htm new file mode 100755 index 0000000..516edea --- /dev/null +++ b/css1/sec43.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.3 Replaced Elements

CSS1 Test Suite: 4.3 Replaced Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

IMG.one {display: inline;}
IMG.two {display: block;}
IMG.three {display: block;
           margin-right: auto; margin-left: auto; width: auto;}
IMG.four {display: block;
          margin-right: auto; margin-left: auto; width: 50%;}
IMG.five {display: block;
          margin-right: 0; margin-left: auto; width: 50%;}

[Image]The image at the beginning of this sentence should be a 15px square.

[Image]

The above image should be a 15px square with the same left edge as this text.

[Image]

The above image should be a 15px square aligned at the center.

[Image]

The above image should be a square resized so its width is 50% of the its parent element, and centered horizontally within the parent element: the document body in the first half, and the table cell in the second.

[Image]

The above image should be a square resized so its width is 50% of its parent element, and aligned at the right edge of the parent element: the document body in the first half, and the table cell in the second.

TABLE Testing Section
 

[Image]The image at the beginning of this sentence should be a 15px square.

[Image]

The above image should be a 15px square with the same left edge as this text.

[Image]

The above image should be a 15px square aligned at the center.

[Image]

The above image should be a square resized so its width is 50% of the its parent element, and centered horizontally within the parent element: the document body in the first half, and the table cell in the second.

[Image]

The above image should be a square resized so its width is 50% of its parent element, and aligned at the right edge of the parent element: the document body in the first half, and the table cell in the second.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec44.htm b/css1/sec44.htm new file mode 100755 index 0000000..b594474 --- /dev/null +++ b/css1/sec44.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.4 The Height of Lines

CSS1 Test Suite: 4.4 The Height of Lines


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {font-size: 14px; line-height: 20px;}
IMG.onea {vertical-align: text-bottom;
     width: 200px; height: 200px;}
IMG.oneb {vertical-align: text-top; width: 200px; height: 200px;}

P.two {font-size: 14px; line-height: 20px;}
IMG.twoa {vertical-align: text-bottom; width: 100px; height: 100px;
     padding: 5px; border-style: solid;
     border-width: 10px; margin: 15px;}
IMG.twob {vertical-align: text-top;
          width: 100px; height: 100px;
     padding: 5px; border-style: solid;
     border-width: 10px; margin: 15px;}

IMG.twoc {vertical-align: middle; width: 50px; height: 50px;
     padding: 5px; border-style: solid;
     border-width: 10px; margin: -10px;}


This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels, three of which are part of the line-box of each line. Any images within the paragraph should increase the height of the line-box so that they fit within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned.

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels. Any images within the paragraph should increase the height of the line-box so that they fit, including their padding (5px), border (10px) and margins (15px) within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned. It is the outer edge of the margin that should be text-bottom and text-top aligned in this paragraph, so for the first image the bottom border of the image should begin 15px above the bottom of the text, and for the second image the top border should begin 15px below the top of the text [Image]. The last image in this paragraph has -10px margins set on it, so that should pull the text in toward the image in the vertical direction, and also in the horizontal direction.

TABLE Testing Section
 

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels, three of which are part of the line-box of each line. Any images within the paragraph should increase the height of the line-box so that they fit within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned.

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels. Any images within the paragraph should increase the height of the line-box so that they fit, including their padding (5px), border (10px) and margins (15px) within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned. It is the outer edge of the margin that should be text-bottom and text-top aligned in this paragraph, so for the first image the bottom border of the image should begin 15px above the bottom of the text, and for the second image the top border should begin 15px below the top of the text [Image]. The last image in this paragraph has -10px margins set on it, so that should pull the text in toward the image in the vertical direction, and also in the horizontal direction.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec45.htm b/css1/sec45.htm new file mode 100755 index 0000000..05bf378 --- /dev/null +++ b/css1/sec45.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 4.5 The Canvas

CSS1 Test Suite: 4.5 The Canvas


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

HTML {background-color: aqua;}
BODY {background-color: green; background-image: none; margin: 25px;}

The body of this document should have a green background. It also has a margin of 25 pixels, so the light blue background set for the HTML element should surround the BODY. If the BODY content is significantly shorter than the browser's window height, then the bottom border may be larger than 25 pixels.

TABLE Testing Section
 

The body of this document should have a green background. It also has a margin of 25 pixels, so the light blue background set for the HTML element should surround the BODY. If the BODY content is significantly shorter than the browser's window height, then the bottom border may be larger than 25 pixels.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec52.htm b/css1/sec52.htm new file mode 100755 index 0000000..8c0802e --- /dev/null +++ b/css1/sec52.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2 Font Properties

CSS1 Test Suite: 5.2 Font Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec522.htm b/css1/sec522.htm new file mode 100755 index 0000000..d77cf17 --- /dev/null +++ b/css1/sec522.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.2 font-family

CSS1 Test Suite: 5.2.2 font-family


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

DIV.a {font-family: serif;}
DIV.b {font-family: monospace;}
.one {font-family: serif;}
.two {font-family: sans-serif;}
.three {font-family: cursive;}
.four {font-family: fantasy;}
.five {font-family: monospace;}
.six {font-family: sans-serif,cursive;}
.seven {font-family: monospace,serif;}

This sentence is normal for the first division, which is the next five sentences; it should be a serif font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


This sentence should be in a sans-serif font, not cursive.

This sentence should be in a monospace font, not serif.


This sentence is normal for the first division, which is the next five sentences; it should be a monospace font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.

TABLE Testing Section
 

This sentence is normal for the first division, which is the next five sentences; it should be a serif font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


This sentence should be in a sans-serif font, not cursive.

This sentence should be in a monospace font, not serif.


This sentence is normal for the first division, which is the next five sentences; it should be a monospace font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec523.htm b/css1/sec523.htm new file mode 100755 index 0000000..2be6aac --- /dev/null +++ b/css1/sec523.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.3 font-style

CSS1 Test Suite: 5.2.3 font-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-style: italic;}
.two {font-style: oblique;}
.three, I {font-style: normal;}


This paragraph should be in italics, but the last word of the sentence should be normal.

This paragraph should be oblique.

This paragraph should be normal.

TABLE Testing Section
 

This paragraph should be in italics, but the last word of the sentence should be normal.

This paragraph should be oblique.

This paragraph should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec524.htm b/css1/sec524.htm new file mode 100755 index 0000000..08feb02 --- /dev/null +++ b/css1/sec524.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.4 font-variant

CSS1 Test Suite: 5.2.4 font-variant


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-variant: small-caps;}
.two {font-variant: normal;}


This Paragraph should be in Small Caps.

This Paragraph should be in Small Caps, but the Last Word in the Sentence should be Normal.

TABLE Testing Section
 

This Paragraph should be in Small Caps.

This Paragraph should be in Small Caps, but the Last Word in the Sentence should be Normal.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec525.htm b/css1/sec525.htm new file mode 100755 index 0000000..e98e710 --- /dev/null +++ b/css1/sec525.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.5 font-weight

CSS1 Test Suite: 5.2.5 font-weight


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-weight: bold;}
.two {font-weight: bolder;}
.three {font-weight: lighter;}
.four {font-weight: 100;}
.five {font-weight: 300;}
.six {font-weight: 500;}
.seven {font-weight: 700;}
.eight {font-weight: 900;}
.nine {font-weight: normal;}
B {font-weight: lighter;}


This sentence should be bold.

This sentence should be bolder than normal.

This is a heading-4.

This is a bolder heading-4.

This sentence should be normal (boldface made lighter).

This sentence should be weight 100.

This sentence should be weight 300.

This sentence should be weight 500.

This sentence should be weight 700.

This sentence should be weight 900.

This sentence should be bold, but the last word in the sentence should be normal.

TABLE Testing Section
 

This sentence should be bold.

This sentence should be bolder than normal.

This is a heading-4.

This is a bolder heading-4.

This sentence should be normal (boldface made lighter).

This sentence should be weight 100.

This sentence should be weight 300.

This sentence should be weight 500.

This sentence should be weight 700.

This sentence should be weight 900.

This sentence should be bold, but the last word in the sentence should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec526.htm b/css1/sec526.htm new file mode 100755 index 0000000..e1dfda6 --- /dev/null +++ b/css1/sec526.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.6 font-size

CSS1 Test Suite: 5.2.6 font-size


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-size: medium;}
.two {font-size: larger;}
.three {font-size: smaller;}
.four {font-size: xx-small;}
.five {font-size: x-small;}
.six {font-size: small;}
.seven {font-size: large;}
.eight {font-size: x-large;}
.nine {font-size: xx-large;}
.a {font-size: 0.5in;}
.b {font-size: 1cm;}
.c {font-size: 10mm;}
.d {font-size: 18pt;}
.e {font-size: 1.5pc;}
.f {font-size: 2em;}
.g {font-size: 3ex;}
.h {font-size: 25px;}
.i {font-size: 200%;}
.j {font-size: -0.5in;}


This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent.

This sentence has been set to medium, which may or may not be the same size as unstyled text.

This sentence should be larger than unstyled text.

This sentence should be smaller than unstyled text.

This sentence should be very small, but the last word in the sentence should be medium.

This sentence should be rather small, but the last word in the sentence should be medium.

This sentence should be small, but the last word in the sentence should be medium.

This sentence should be large, but the last word in the sentence should be medium.

This sentence should be rather large, but the last word in the sentence should be medium.

This sentence should be very large, but the last word in the sentence should be medium.

This sentence should be half an inch tall.

This sentence should be one centimeter tall.

This sentence should be ten millimeters tall.

This sentence should be eighteen points tall.

This sentence should be one and one half picas tall.

This sentence should be two em tall.

This sentence should be three ex tall.

This sentence should be twenty-five pixels tall.

This sentence should be twice normal size.

This sentence should be normal size, since no negative values are allowed and therefore should be ignored.

TABLE Testing Section
 

This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent.

This sentence has been set to medium, which may or may not be the same size as unstyled text.

This sentence should be larger than unstyled text.

This sentence should be smaller than unstyled text.

This sentence should be very small, but the last word in the sentence should be medium.

This sentence should be rather small, but the last word in the sentence should be medium.

This sentence should be small, but the last word in the sentence should be medium.

This sentence should be large, but the last word in the sentence should be medium.

This sentence should be rather large, but the last word in the sentence should be medium.

This sentence should be very large, but the last word in the sentence should be medium.

This sentence should be half an inch tall.

This sentence should be one centimeter tall.

This sentence should be ten millimeters tall.

This sentence should be eighteen points tall.

This sentence should be one and one half picas tall.

This sentence should be two em tall.

This sentence should be three ex tall.

This sentence should be twenty-five pixels tall.

This sentence should be twice normal size.

This sentence should be normal size, since no negative values are allowed and therefore should be ignored.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec527.htm b/css1/sec527.htm new file mode 100755 index 0000000..19ad352 --- /dev/null +++ b/css1/sec527.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.2.7 font

CSS1 Test Suite: 5.2.7 font


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {font-size: 12px;}
.one {font: italic small-caps 13pt Helvetica;}
.two {font: 150%/150% serif;}
.three {font: 150%/150% sans-serif;}
.four {font: small/200% cursive;}
.five {font: italic small-caps 900 150%/150% sans-serif;}
.six {font: italic small-caps 100 150%/300% sans-serif;}
.seven {font: italic small-caps 900 150%/2em monospace;}
.eight {font: italic small-caps 500 150%/1in sans-serif;}
.nine {font: oblique normal 700 18px/200% sans-serif;}
.ten {font: normal 400 80%/2.5 sans-serif;}
SPAN.color {background-color: silver;}

This element is unstyled, and should inherit a font-size of 12px from the BODY element. This is the "base font size" referred to in the following tests.

This element should be 13pt. Helvetica which is in small-cap italics.

This element should be in a serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a cursive font, 'small' in size, with a line-height 200% the height of the text's actual size. For example, if the font-size value small is calculated at 10px, then the line-height should be 20px. The actual value of the font-size is UA-dependent. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a monospace font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 2em, or twice the element's font size (18px and 36px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 500. Its font-size should be 150% the base font size, or 18px, and its line-height should be 1in. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, oblique and not small-caps, with a weight of 700. Its font-size should be 18 pixels, and its line-height should be 36px (200% this element's font size). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, with a weight of 400. Its font-size should be 80% of 12px, or 9.6px, and its line-height shoud be 2.5 times that, or 24px. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). The text should have a silver background. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.

TABLE Testing Section
 

This element is unstyled, and should inherit a font-size of 12px from the BODY element. This is the "base font size" referred to in the following tests.

This element should be 13pt. Helvetica which is in small-cap italics.

This element should be in a serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a cursive font, 'small' in size, with a line-height 200% the height of the text's actual size. For example, if the font-size value small is calculated at 10px, then the line-height should be 20px. The actual value of the font-size is UA-dependent. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a monospace font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 2em, or twice the element's font size (18px and 36px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 500. Its font-size should be 150% the base font size, or 18px, and its line-height should be 1in. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, oblique and not small-caps, with a weight of 700. Its font-size should be 18 pixels, and its line-height should be 36px (200% this element's font size). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, with a weight of 400. Its font-size should be 80% of 12px, or 9.6px, and its line-height shoud be 2.5 times that, or 24px. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). The text should have a silver background. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec53.htm b/css1/sec53.htm new file mode 100755 index 0000000..e8563a7 --- /dev/null +++ b/css1/sec53.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3 Color and Background Properties

CSS1 Test Suite: 5.3 Color and Background Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec531.htm b/css1/sec531.htm new file mode 100755 index 0000000..5f1442b --- /dev/null +++ b/css1/sec531.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.1 color

CSS1 Test Suite: 5.3.1 color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {color: green;}


This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec532.htm b/css1/sec532.htm new file mode 100755 index 0000000..c2d3043 --- /dev/null +++ b/css1/sec532.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.2 background-color

CSS1 Test Suite: 5.3.2 background-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {background-color: green;}
.one {background-color: lime;}
.two {background-color: transparent;}


This element's background should be green.

This element's background should be lime (light green).

This element's background should be green, and the last word in this sentence should also have a green background. This is because the background color of the parent element (the paragraph) should "shine through" the SPANned word "background," which was set to transparent. If the document background is visible, the browser is in error.

This element should allow the document background to "shine through." There should be no green backgrounds here!

TABLE Testing Section
 

This element's background should be green.

This element's background should be lime (light green).

This element's background should be green, and the last word in this sentence should also have a green background. This is because the background color of the parent element (the paragraph) should "shine through" the SPANned word "background," which was set to transparent. If the document background is visible, the browser is in error.

This element should allow the document background to "shine through." There should be no green backgrounds here!


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec533.htm b/css1/sec533.htm new file mode 100755 index 0000000..db8f8d1 --- /dev/null +++ b/css1/sec533.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.3 background-image

CSS1 Test Suite: 5.3.3 background-image


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {background-image: url(bg.gif);}
.one {background-image: none;}


This sentence should be backed by an image-- a green grid pattern, in this case. The background image should also tile along both axes, because no repeat direction is specified (specific tests for repeating are found elsewhere).

This sentence should be backed by a repeated green-grid image, as should the last three words in this sentence. If it is not, then none is interpreted incorrectly. (none means that the element has no background image, allowing the parent to "shine through" by default; since the parent of the words "in this sentence" is the paragraph, then the paragraph's image should be visible.)

This sentence should NOT be backed by a repeated green-grid image, allowing the page's background to "shine through" instead.

TABLE Testing Section
 

This sentence should be backed by an image-- a green grid pattern, in this case. The background image should also tile along both axes, because no repeat direction is specified (specific tests for repeating are found elsewhere).

This sentence should be backed by a repeated green-grid image, as should the last three words in this sentence. If it is not, then none is interpreted incorrectly. (none means that the element has no background image, allowing the parent to "shine through" by default; since the parent of the words "in this sentence" is the paragraph, then the paragraph's image should be visible.)

This sentence should NOT be backed by a repeated green-grid image, allowing the page's background to "shine through" instead.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec534.htm b/css1/sec534.htm new file mode 100755 index 0000000..1f785b3 --- /dev/null +++ b/css1/sec534.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.4 background-repeat

CSS1 Test Suite: 5.3.4 background-repeat


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {background-image: url(oransqr.gif); background-repeat: repeat-y;}
.two {background-image: url(oransqr.gif); background-repeat: repeat-x;}
.three {background-image: url(oransqr.gif); background-repeat: no-repeat;}
.four {background-image: url(bg.gif); background-position: 50% 50%; background-repeat: repeat-y;}
.five {background-image: url(crosshair2.gif); background-position: 50% 50%;
       background-color: red;}
.six {background-image: url(crosshair2.gif); background-position: center top;
      background-color: red;}
.seven {background-image: url(crosshair2.gif); background-position: top left;
        background-color: red;}
.eight {background-image: url(crosshair2.gif); background-position: bottom right;
        background-color: red;}
.nine {background-image: url(crosshair2.gif); background-position: 50% 50%;
       background-color: red;}


This sentence should have an orange stripe repeated in the "y" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have an orange stripe repeated in the "x" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a single orange square behind it, placed at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a green-hatch stripe running vertically down the center of the paragraph, with the origin image exactly centered in the paragraph. This is because repeat-y specifies tiling in both directions on the y-axis. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious.

This paragraph should have a tiled background, with the origin image exactly centered in the paragraph. This is because background-repeat specifies tiling in all directions, regardless of the position of the origin image. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible then the image has not bee correctly tiled.

This sentence should have a fully tiled background which starts at its center top; that is, the background's origin should be the exact center of the top of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its top left. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its bottom right; in other words, a complete instance of the image should be anchored in the bottom right corner, with the tiled background extending out from there. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its center and is tiled in all directions; that is, the background's origin should be the exact center of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. In fact, a lot of extra text will be necessary to make this at all obvious. This is true because I am not able to increase the text size without resorting to either headings or other CSS properties, neither of which I want to use in this circumstance. This ought to be enough text, though. A background color is present, although if it is visible, then the image may not have been tiled correctly.

TABLE Testing Section
 

This sentence should have an orange stripe repeated in the "y" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have an orange stripe repeated in the "x" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a single orange square behind it, placed at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a green-hatch stripe running vertically down the center of the paragraph, with the origin image exactly centered in the paragraph. This is because repeat-y specifies tiling in both directions on the y-axis. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious.

This paragraph should have a tiled background, with the origin image exactly centered in the paragraph. This is because background-repeat specifies tiling in all directions, regardless of the position of the origin image. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible then the image has not bee correctly tiled.

This sentence should have a fully tiled background which starts at its center top; that is, the background's origin should be the exact center of the top of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its top left. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its bottom right; in other words, a complete instance of the image should be anchored in the bottom right corner, with the tiled background extending out from there. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its center and is tiled in all directions; that is, the background's origin should be the exact center of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. In fact, a lot of extra text will be necessary to make this at all obvious. This is true because I am not able to increase the text size without resorting to either headings or other CSS properties, neither of which I want to use in this circumstance. This ought to be enough text, though. A background color is present, although if it is visible, then the image may not have been tiled correctly.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec535.htm b/css1/sec535.htm new file mode 100755 index 0000000..c4a33d3 --- /dev/null +++ b/css1/sec535.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.5 background-attachment

CSS1 Test Suite: 5.3.5 background-attachment


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background-image: url(bg.gif); background-repeat: repeat-x; background-attachment: fixed;}


This document should have a green grid-pattern line across the top of the page (or at least a tiled background) which does NOT scroll with the document. It should, instead, appear to be a fixed pattern past which the content scrolls, even when the end of the page is reached. In addition, the default Test Suite background should NOT appear, as it's been overridden by the styles shown above. I'll have to add a lot of extra text to the page in order to make all this something we can actually check. Don't worry, I'll think of something.

In fact, why not the relevant section from the CSS1 specification? A capital idea.



5.3.5    'background-attachment'

Value: scroll | fixed
Initial: scroll
Applies to: all elements
Inherited: no
Percentage values: N/A

If a background image is specified, the value of 'background-attachment' determines if it is fixed with regard to the canvas or if it scrolls along with the content.

  BODY { 
    background: red url(pendant.gif);
    background-repeat: repeat-y;
    background-attachment: fixed;
  }

CSS1 core: UAs may treat 'fixed' as 'scroll'. However, it is recommended they interpret 'fixed' correctly, at least on the HTML and BODY elements, since there is no way for an author to provide an image only for those browsers that support 'fixed'.

TABLE Testing Section
 

This document should have a green grid-pattern line across the top of the page (or at least a tiled background) which does NOT scroll with the document. It should, instead, appear to be a fixed pattern past which the content scrolls, even when the end of the page is reached. In addition, the default Test Suite background should NOT appear, as it's been overridden by the styles shown above. I'll have to add a lot of extra text to the page in order to make all this something we can actually check. Don't worry, I'll think of something.

In fact, why not the relevant section from the CSS1 specification? A capital idea.



5.3.5    'background-attachment'

Value: scroll | fixed
Initial: scroll
Applies to: all elements
Inherited: no
Percentage values: N/A

If a background image is specified, the value of 'background-attachment' determines if it is fixed with regard to the canvas or if it scrolls along with the content.

  BODY { 
    background: red url(pendant.gif);
    background-repeat: repeat-y;
    background-attachment: fixed;
  }

CSS1 core: UAs may treat 'fixed' as 'scroll'. However, it is recommended they interpret 'fixed' correctly, at least on the HTML and BODY elements, since there is no way for an author to provide an image only for those browsers that support 'fixed'.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec536.htm b/css1/sec536.htm new file mode 100755 index 0000000..0bc6cbd --- /dev/null +++ b/css1/sec536.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.6 background-position

CSS1 Test Suite: 5.3.6 background-position


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background-image: url(bg.gif); background-position: right top;
      background-repeat: no-repeat;}
.one {background-image: url(bg.gif); background-position: center;
      background-repeat: no-repeat; background-color: aqua;}
.two {background-image: url(bg.gif); background-position: 50% 50%;
      background-repeat: no-repeat; background-color: aqua;}
.three {background-image: url(bg.gif); background-position: bottom right;
        background-repeat: no-repeat; background-color: aqua;}
.four {background-image: url(bg.gif); background-position: 100% 100%;
       background-repeat: no-repeat; background-color: aqua;}
.five {background-image: url(bg.gif); background-position: 0% 50%;
       background-repeat: no-repeat; background-color: aqua;}
.six {background-image: url(bg.gif); background-position: 75% 25%;
       background-repeat: no-repeat; background-color: aqua;}
.seven {background-image: url(bg.gif); background-position: 20px 20px;
       background-repeat: no-repeat; background-color: aqua;}


This document should have a single, small green image in its upper right corner.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image exactly at the left center; that is, the left center of the image should be fixed at the left center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image positioned 75% of the way across the element, and 25% down. The background color will make it easier to determine the edges of the paragraph, which should help in determining if all this is so, and the extra text should make the element long enough for this test to be simpler to evaluate.

This paragraph should have a single, small green image positioned 20 pixels down and to the left of the upper left-hand corner; that is, the upper left-hand corner of the image should be 20 pixels down and to the left of the upper-left corner of the element. The background color will make it easier to determine the edges of the paragraph, which should assist in evaluating this test.

TABLE Testing Section
 

This document should have a single, small green image in its upper right corner.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image exactly at the left center; that is, the left center of the image should be fixed at the left center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image positioned 75% of the way across the element, and 25% down. The background color will make it easier to determine the edges of the paragraph, which should help in determining if all this is so, and the extra text should make the element long enough for this test to be simpler to evaluate.

This paragraph should have a single, small green image positioned 20 pixels down and to the left of the upper left-hand corner; that is, the upper left-hand corner of the image should be 20 pixels down and to the left of the upper-left corner of the element. The background color will make it easier to determine the edges of the paragraph, which should assist in evaluating this test.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec537.htm b/css1/sec537.htm new file mode 100755 index 0000000..4915630 --- /dev/null +++ b/css1/sec537.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.3.7 background

CSS1 Test Suite: 5.3.7 background


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background: green url(oransqr.gif) repeat-x center top fixed;}
.one {background: lime url(oransqr.gif) repeat-y 100% 0%;}
.two {background: lime url(oransqr.gif) repeat-y center top;}
.three {background: lime url(oransqr.gif) repeat-x left top;}

This document should have a green background with an orange strip running across the entire top of the page, since repeat-x indicates tiling in both directions of the x-axis. Furthermore, the strip should be fixed in place. I'll have to add extra text at the end of this page to make it long enough to scroll conveniently.

This paragraph should have a lime background and an orange strip which starts at the top right and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the center top and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the top left and runs to the top right. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

TABLE Testing Section
 

This document should have a green background with an orange strip running across the entire top of the page, since repeat-x indicates tiling in both directions of the x-axis. Furthermore, the strip should be fixed in place. I'll have to add extra text at the end of this page to make it long enough to scroll conveniently.

This paragraph should have a lime background and an orange strip which starts at the top right and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the center top and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the top left and runs to the top right. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec54.htm b/css1/sec54.htm new file mode 100755 index 0000000..bec7c1e --- /dev/null +++ b/css1/sec54.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4 Text Properties

CSS1 Test Suite: 5.4 Text Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec541.htm b/css1/sec541.htm new file mode 100755 index 0000000..03c2392 --- /dev/null +++ b/css1/sec541.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.1 word-spacing

CSS1 Test Suite: 5.4.1 word-spacing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {word-spacing: 0.3in;}
.two {word-spacing: 0.5cm;}
.three {word-spacing: 5mm;}
.four {word-spacing: 3pt;}
.five {word-spacing: 0.25pc;}
.six {word-spacing: 1em;}
.seven {word-spacing: 1ex;}
.eight {word-spacing: 5px;}
.nine {word-spacing: normal;}
.ten {word-spacing: 300%;}
.eleven {word-spacing: -0.2em;}


This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them, but the last few words in the sentence should have normal spacing.

This sentence should have normal word-spacing, since percentage values are not allowed on this property.

This words in this sentence should have reduced space between them, since negative values are allowed on this property.

TABLE Testing Section
 

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them, but the last few words in the sentence should have normal spacing.

This sentence should have normal word-spacing, since percentage values are not allowed on this property.

This words in this sentence should have reduced space between them, since negative values are allowed on this property.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec542.htm b/css1/sec542.htm new file mode 100755 index 0000000..7c4312d --- /dev/null +++ b/css1/sec542.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.2 letter-spacing

CSS1 Test Suite: 5.4.2 letter-spacing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {letter-spacing: 0.3in;}
.two {letter-spacing: 0.5cm;}
.three {letter-spacing: 5mm;}
.four {letter-spacing: 3pt;}
.five {letter-spacing: 0.25pc;}
.six {letter-spacing: 1em;}
.seven {letter-spacing: 1ex;}
.eight {letter-spacing: 5px;}
.nine {letter-spacing: normal;}
.ten {letter-spacing: 300%;}
.eleven {letter-spacing: -0.1em;}

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them, but the last few words in the sentence should show normal spacing.

This letters in this sentence should have normal space between them, since percentage values are not allowed on this property.

This letters in this sentence should have reduced space between them, since negative values are allowed on this property.

TABLE Testing Section
 

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them, but the last few words in the sentence should show normal spacing.

This letters in this sentence should have normal space between them, since percentage values are not allowed on this property.

This letters in this sentence should have reduced space between them, since negative values are allowed on this property.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec543.htm b/css1/sec543.htm new file mode 100755 index 0000000..6dab64e --- /dev/null +++ b/css1/sec543.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.3 text-decoration

CSS1 Test Suite: 5.4.3 text-decoration


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-decoration: underline;}
.two {text-decoration: overline;}
.three {text-decoration: line-through;}
.four {text-decoration: blink;}
B.five {text-decoration: none;}
.six {text-decoration: underline overline;}
.seven {text-decoration: underline overline line-through;}


This sentence should be underlined.

This sentence should be overlined.

This sentence should have stricken text (linethrough).

This element should be blinking. (It is not required, however, that UAs support this behavior.)

The text in this element should be underlined. The boldfaced text in this element should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own.

This sentence should be underlined and overlined.

This sentence should be underlined, overlined, and stricken.

There should be nothing visible between this sentence and the one above (there is an empty paragraph element with class of seven).

Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements.

The underlining in this sentence should be green, no matter what the text color may be.

The colors of the underlining in this sentence should be the same as that of the parent text (that is, the first word in the sentence, which should be black).

TABLE Testing Section
 

This sentence should be underlined.

This sentence should be overlined.

This sentence should have stricken text (linethrough).

This element should be blinking. (It is not required, however, that UAs support this behavior.)

The text in this element should be underlined. The boldfaced text in this element should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own.

This sentence should be underlined and overlined.

This sentence should be underlined, overlined, and stricken.

There should be nothing visible between this sentence and the one above (there is an empty paragraph element with class of seven).

Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements.

The underlining in this sentence should be green, no matter what the text color may be.

The colors of the underlining in this sentence should be the same as that of the parent text (that is, the first word in the sentence, which should be black).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec544.htm b/css1/sec544.htm new file mode 100755 index 0000000..63ce9b1 --- /dev/null +++ b/css1/sec544.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.4 vertical-align

CSS1 Test Suite: 5.4.4 vertical-align


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {font-size: 12pt;}
.one {vertical-align: sub;}
.two {vertical-align: super;}
.three {vertical-align: top; font-size: 12pt;}
.four {vertical-align: text-top; font-size: 12pt;}
.five {vertical-align: middle; font-size: 12pt;}
.six {vertical-align: bottom; font-size: 12pt;}
.seven {vertical-align: text-bottom; font-size: 12pt;}
.eight {vertical-align: baseline; font-size: 12pt;}
.nine {vertical-align: 50%; font-size: 12px; line-height: 16px;}

P.example {font-size: 14pt;}
BIG {font-size: 16pt;}
SMALL {font-size: 12pt;}
.ttopalign {vertical-align: text-top;}
.topalign {vertical-align: top;}
.midalign {vertical-align: middle;}


[Image]The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle).

[Image] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line.

[Image] The image at the beginning of this sentence should be middle-aligned, which should align its middle with the point defined as the text baseline plus half the x-height.

[Image] The first four words in this sentence should be 12pt in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line.

[Image] The first eight words ("eight" has a descender) in this sentence should be 12pt in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line.

[Image] The first four words in this sentence should be 12pt in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line.

[Image]The first four words in this sentence should have a font-size of 12px and a line-height of 16px; they are also 50%-aligned, which should raise them 8px relative to the natural baseline.

In the following paragraph, all images should be aligned with the top of the 14-point text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the middle of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been SPANned appropriately in order to cause this to happen.

This paragraph [Image] contains many images [Image] and some text [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] the tallest element in [Image] whichever line the elements appear. [Image]

TABLE Testing Section
 

[Image]The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle).

[Image] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line.

[Image] The image at the beginning of this sentence should be middle-aligned, which should align its middle with the point defined as the text baseline plus half the x-height.

[Image] The first four words in this sentence should be 12pt in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line.

[Image] The first eight words ("eight" has a descender) in this sentence should be 12pt in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line.

[Image] The first four words in this sentence should be 12pt in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line.

[Image]The first four words in this sentence should have a font-size of 12px and a line-height of 16px; they are also 50%-aligned, which should raise them 8px relative to the natural baseline.

In the following paragraph, all images should be aligned with the top of the 14-point text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the middle of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been SPANned appropriately in order to cause this to happen.

This paragraph [Image] contains many images [Image] and some text [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] the tallest element in [Image] whichever line the elements appear. [Image]


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec545.htm b/css1/sec545.htm new file mode 100755 index 0000000..d184661 --- /dev/null +++ b/css1/sec545.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.5 text-transform

CSS1 Test Suite: 5.4.5 text-transform


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.ttn {text-transform: none;}
.cap {text-transform: capitalize;}
.upp {text-transform: uppercase;}
.low {text-transform: lowercase;}


This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal.

This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence.

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital letter.

This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, the last eight words should not be uppercase.

This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase.

TABLE Testing Section
 

This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal.

This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence.

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital letter.

This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, the last eight words should not be uppercase.

This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec546.htm b/css1/sec546.htm new file mode 100755 index 0000000..b2286fe --- /dev/null +++ b/css1/sec546.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.6 text-align

CSS1 Test Suite: 5.4.6 text-align


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-align: left;}
.two {text-align: right;}
.three {text-align: center;}
.four {text-align: justify;}


This sentence should be left-justified.

This sentence should be right-justified.

This sentence should be centered.

This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages.

TABLE Testing Section
 

This sentence should be left-justified.

This sentence should be right-justified.

This sentence should be centered.

This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec547.htm b/css1/sec547.htm new file mode 100755 index 0000000..1837b08 --- /dev/null +++ b/css1/sec547.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.7 text-indent

CSS1 Test Suite: 5.4.7 text-indent


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-indent: 0.5in; background: aqua;}
.two {text-indent: 2cm; background: aqua;}
.three {text-indent: 20mm; background: aqua;}
.four {text-indent: 24pt; background: aqua;}
.five {text-indent: 2pc; background: aqua;}
.six {text-indent: 2em; background: aqua;}
.seven {text-indent: 2ex; background: aqua;}
.eight {text-indent: 50%; background: aqua;}
.nine {text-indent: 25px; background: aqua;}
blockquote {text-indent: 50%; background: aqua;}


The first line of this sentence should be indented half an inch.

The first line of this sentence should be indented two centimeters.

The first line of this sentence should be indented twenty millimeters.

The first line of this sentence should be indented twenty-four points.

The first line of this sentence should be indented two picas.

The first line of this sentence should be indented two em.

The first line of this sentence should be indented two ex.

The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page.

The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page.

Only the first line of this sentence should be indented half an inch,
no matter where the lines might start, and
regardless of any other markup which may be present.

In the first half of the test page, this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY; in the second half, it is a child of TABLE.
TABLE Testing Section
 

The first line of this sentence should be indented half an inch.

The first line of this sentence should be indented two centimeters.

The first line of this sentence should be indented twenty millimeters.

The first line of this sentence should be indented twenty-four points.

The first line of this sentence should be indented two picas.

The first line of this sentence should be indented two em.

The first line of this sentence should be indented two ex.

The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page.

The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page.

Only the first line of this sentence should be indented half an inch,
no matter where the lines might start, and
regardless of any other markup which may be present.

In the first half of the test page, this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY; in the second half, it is a child of TABLE.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec548.htm b/css1/sec548.htm new file mode 100755 index 0000000..c247b11 --- /dev/null +++ b/css1/sec548.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.4.8 line-height

CSS1 Test Suite: 5.4.8 line-height


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {line-height: 0.5in; font-size: 12px;}
.two {line-height: 2cm; font-size: 12px;}
.three {line-height: 20mm; font-size: 12px;}
.four {line-height: 24pt; font-size: 12px;}
.five {line-height: 2pc; font-size: 12px;}
.six {line-height: 2em; font-size: 12px;}
.seven {line-height: 3ex; font-size: 12px;}
.eight {line-height: 200%; font-size: 12px;}
.nine {line-height: 2; font-size: 12px;}
.ten {line-height: 50px; font-size: 12px;}
.eleven {line-height: -1em; font-size: 12px;}
TABLE .ten {line-height: normal; font-size: 12px;}
DIV {background-color: silver;}
SPAN.color {background-color: silver;}

This sentence should have a line-height of half an inch, which should cause extra spacing between the lines.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty millimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty-four points, which should cause extra spacing between the lines.

This sentence should have a line-height of two picas, which should cause extra spacing between the lines.

This sentence should have a line-height of two em, which should cause extra spacing between the lines.

This sentence should have a line-height of three ex, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the DIV's font size, or 28px; this should not cause extra spacing between the lines, since the line-height and font-size should have the same value.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which is 200% normal thanks to an inline style; this should cause extra spacing between the lines, as the font-size will be 28px and the line-height will be 56px.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This paragraph should have a line-height of 50 pixels in the first section, which should cause extra spacing between the lines. In the second section (within the table) its line-height should be normal.

This sentence should have a normal line-height, because negative values are not permitted for this property.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines. The text has a background color of silver, but no padding or border. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.

TABLE Testing Section
 

This sentence should have a line-height of half an inch, which should cause extra spacing between the lines.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty millimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty-four points, which should cause extra spacing between the lines.

This sentence should have a line-height of two picas, which should cause extra spacing between the lines.

This sentence should have a line-height of two em, which should cause extra spacing between the lines.

This sentence should have a line-height of three ex, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the DIV's font size, or 28px; this should not cause extra spacing between the lines, since the line-height and font-size should have the same value.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which is 200% normal thanks to an inline style; this should cause extra spacing between the lines, as the font-size will be 28px and the line-height will be 56px.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This paragraph should have a line-height of 50 pixels in the first section, which should cause extra spacing between the lines. In the second section (within the table) its line-height should be normal.

This sentence should have a normal line-height, because negative values are not permitted for this property.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines. The text has a background color of silver, but no padding or border. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec55.htm b/css1/sec55.htm new file mode 100755 index 0000000..88a3f81 --- /dev/null +++ b/css1/sec55.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5 Box Properties

CSS1 Test Suite: 5.5 Box Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5501.htm b/css1/sec5501.htm new file mode 100755 index 0000000..4555ee3 --- /dev/null +++ b/css1/sec5501.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.01 margin-top

CSS1 Test Suite: 5.5.01 margin-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-top: 0;}
.one {margin-top: 0.5in; background-color: aqua;}
.two {margin-top: 25px; background-color: aqua;}
.three {margin-top: 5em; background-color: aqua;}
.four {margin-top: 25%; background-color: aqua;}
.five {margin-top: 25px;}
.six {margin-top: -10px; background-color: aqua;}
P, UL {margin-bottom: 0;}

This element has a class of zero.

This element also has a class of zero.

This element should have a top margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

This element has a top margin of -10px, which should cause it to be shifted "upward" on the page, and no bottom margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

TABLE Testing Section
 

This element has a class of zero.

This element also has a class of zero.

This element should have a top margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

  • This list has a margin-top of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a top margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This element has a class of zero.

This element has a top margin of -10px, which should cause it to be shifted "upward" on the page, and no bottom margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5501b.htm b/css1/sec5501b.htm new file mode 100755 index 0000000..eb1667a --- /dev/null +++ b/css1/sec5501b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.01 margin-top

CSS1 Test Suite: 5.5.01 margin-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-top: 0;}
.one {margin-top: 25px; background-color: aqua;}
.two {margin-top: -10px; background-color: aqua;}


This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving the inline element an aqua background and a -10px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving the inline element an aqua background and a -10px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5502.htm b/css1/sec5502.htm new file mode 100755 index 0000000..ec5a328 --- /dev/null +++ b/css1/sec5502.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.02 margin-right

CSS1 Test Suite: 5.5.02 margin-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-right: 0; text-align: right;}
.one {margin-right: 0.5in; text-align: right; background-color: aqua;}
.two {margin-right: 25px; text-align: right; background-color: aqua;}
.three {margin-right: 5em; text-align: right; background-color: aqua;}
.four {margin-right: 25%; text-align: right; background-color: aqua;}
.five {margin-right: -10px; background-color: aqua;}

This element has a class of zero.

This sentence should have a right margin of half an inch.

This sentence should have a right margin of 25 pixels.

This sentence should have a right margin of 5 em.

This sentence should have a right margin of 25%, which is calculated with respect to the width of the parent element.

This element has a class of zero.

This paragraph has a right margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative right margin and the background color.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a right margin of half an inch.

This sentence should have a right margin of 25 pixels.

This sentence should have a right margin of 5 em.

This sentence should have a right margin of 25%, which is calculated with respect to the width of the parent element.

  • The right margin on this unordered list has been set to 25 pixels, and the background color has been set to gray.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its right margin also set to 25 pixels, which should combine with the list's margin to make 50 pixels of margin, and its background-color has been set to white.
  • This is an unclassed list item

This element has a class of zero.

This paragraph has a right margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative right margin and the background color.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5502b.htm b/css1/sec5502b.htm new file mode 100755 index 0000000..6275700 --- /dev/null +++ b/css1/sec5502b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.02 margin-right

CSS1 Test Suite: 5.5.02 margin-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-right: 25px; text-align: right; background-color: aqua;}
.two {margin-right: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right margin only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px right margin only in the last line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right margin only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px right margin only in the last line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5503.htm b/css1/sec5503.htm new file mode 100755 index 0000000..3bfa78c --- /dev/null +++ b/css1/sec5503.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.03 margin-bottom

CSS1 Test Suite: 5.5.03 margin-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-bottom: 0;}
.one {margin-bottom: 0.5in; background-color: aqua;}
.two {margin-bottom: 25px; background-color: aqua;}
.three {margin-bottom: 5em; background-color: aqua;}
.four {margin-bottom: 25%; background-color: aqua;}
.five {margin-bottom: 25px;}
.six {margin-bottom: -10px; background-color: aqua;}
P, UL {margin-top: 0;}


This element has a class of zero.

This sentence should have a bottom margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a bottom margin of 25%, which will require extra text in order to make sure that the margin isn't applied to each line.

This element has a class of zero.

This element also has a class of zero.

This paragraph has a bottom margin of -10px, which should cause elements after it to be shifted "upward" on the page, and no top margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

This element has a class of zero.

This element also has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a bottom margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a bottom margin of 25%, which will require extra text in order to make sure that the margin isn't applied to each line.

This element has a class of zero.

This element also has a class of zero.

  • This list has a margin-bottom of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a bottom margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This paragraph has a bottom margin of -10px, which should cause elements after it to be shifted "upward" on the page, and no top margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

This element has a class of zero.

This element also has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5503b.htm b/css1/sec5503b.htm new file mode 100755 index 0000000..dc9a85e --- /dev/null +++ b/css1/sec5503b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.03 margin-bottom

CSS1 Test Suite: 5.5.03 margin-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-bottom: 25px; background-color: aqua;}
.two {margin-bottom: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5504.htm b/css1/sec5504.htm new file mode 100755 index 0000000..5e8d5dc --- /dev/null +++ b/css1/sec5504.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.04 margin-left

CSS1 Test Suite: 5.5.04 margin-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-left: 0;}
.one {margin-left: 0.5in; background-color: aqua;}
.two {margin-left: 25px; background-color: aqua;}
.three {margin-left: 5em; background-color: aqua;}
.four {margin-left: 25%; background-color: aqua;}
.five {margin-left: -10px; background-color: aqua;}

This element has a class of zero.

This sentence should have a left margin of half an inch.

This sentence should have a left margin of 25 pixels.

This sentence should have a left margin of 5 em.

This sentence should have a left margin of 25%, which is calculated with respect to the width of the parent element.

This element has a class of zero.

This paragraph has a left margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative left margin and the background color.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a left margin of half an inch.

This sentence should have a left margin of 25 pixels.

This sentence should have a left margin of 5 em.

This sentence should have a left margin of 25%, which is calculated with respect to the width of the parent element.

  • The left margin on this unordered list has been set to 25 pixels, and its background color has been set to gray.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its left margin also set to 25 pixels, which should combine with the list's margin to make 50 pixels of margin, and its background color has been set to white.
  • This is an unclassed list item

This element has a class of zero.

This paragraph has a left margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative left margin and the background color.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5504b.htm b/css1/sec5504b.htm new file mode 100755 index 0000000..f4a497c --- /dev/null +++ b/css1/sec5504b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.04 margin-left

CSS1 Test Suite: 5.5.04 margin-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-left: 25px; background-color: aqua;}
.two {margin-left: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel left margin only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px left margin only in the first line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel left margin only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px left margin only in the first line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5505.htm b/css1/sec5505.htm new file mode 100755 index 0000000..6ed3885 --- /dev/null +++ b/css1/sec5505.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.05 margin

CSS1 Test Suite: 5.5.05 margin


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin: 0;}
.one {margin: 0.5in; background-color: aqua;}
.two {margin: 25px; background-color: aqua;}
.three {margin: 5em; background-color: aqua;}
.four {margin: 25%; background-color: aqua;}
.five {margin: 25px;}
.six {margin: -10px; background-color: aqua;}

NOTE: The following tests are separated by class-zero paragraphs, so as to prevent margin-collapsing as described in section 4.1.1 of the CSS1 specification.

This element has a class of zero.

This sentence should have an overall margin of half an inch, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25 pixels, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 5 em, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

This element has a class of zero.

This paragraph has an overall margin of -10px, which should make it wider than usual as well as shift it upward and pull subsequent text up toward it, and a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative margin and the background color.

This element has a class of zero.

TABLE Testing Section
 

NOTE: The following tests are separated by class-zero paragraphs, so as to prevent margin-collapsing as described in section 4.1.1 of the CSS1 specification.

This element has a class of zero.

This sentence should have an overall margin of half an inch, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25 pixels, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 5 em, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

  • This list has a margin of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This element has a class of zero.

This paragraph has an overall margin of -10px, which should make it wider than usual as well as shift it upward and pull subsequent text up toward it, and a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative margin and the background color.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5505b.htm b/css1/sec5505b.htm new file mode 100755 index 0000000..5575092 --- /dev/null +++ b/css1/sec5505b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.05 margin

CSS1 Test Suite: 5.5.05 margin


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin: 0;}
.one {margin: 25px; background-color: aqua;}
.two {margin: -10px; background-color: aqua;}

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a 25px margin to the left side of the inline box in the first line it appears, and a 25px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a -10px margin to the left side of the inline box in the first line it appears, and a -10px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a 25px margin to the left side of the inline box in the first line it appears, and a 25px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a -10px margin to the left side of the inline box in the first line it appears, and a -10px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5506.htm b/css1/sec5506.htm new file mode 100755 index 0000000..8e854a2 --- /dev/null +++ b/css1/sec5506.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.06 padding-top

CSS1 Test Suite: 5.5.06 padding-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-top: 0;}
.one {padding-top: 0.5in; background-color: aqua;}
.two {padding-top: 25px; background-color: aqua;}
.three {padding-top: 5em; background-color: aqua;}
.four {padding-top: 25%; background-color: aqua;}
.five {padding-top: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a top padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). This will require extra text in order to test.

This element should have no top padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a top padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). This will require extra text in order to test.

This element should have no top padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5506b.htm b/css1/sec5506b.htm new file mode 100755 index 0000000..f20923c --- /dev/null +++ b/css1/sec5506b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.06 padding-top

CSS1 Test Suite: 5.5.06 padding-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-top: 25px; background-color: aqua;}
.two {padding-top: -10px; background-color: aqua;}


This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no top padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no top padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5507.htm b/css1/sec5507.htm new file mode 100755 index 0000000..6409e30 --- /dev/null +++ b/css1/sec5507.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.07 padding-right

CSS1 Test Suite: 5.5.07 padding-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-right: 0;}
.one {padding-right: 0.5in; text-align: right; background-color: aqua;}
.two {padding-right: 25px; text-align: right; background-color: aqua;}
.three {padding-right: 5em; text-align: right; background-color: aqua;}
.four {padding-right: 25%; text-align: right; background-color: aqua;}
.five {padding-right: -20px; text-align: right; background-color: aqua;}

This element has a class of zero.

This element should have a right padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have no right padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue). The text has been right-aligned in order to make the lack of right padding easier to see.

TABLE Testing Section
 

This element has a class of zero.

This element should have a right padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

  • The right padding on this unordered list has been set to 25 pixels, which will require some extra text in order to test.
  • This list item has a right padding of 25 pixels, which will appear to the left of the gray padding of the UL element.

This element should have no right padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue). The text has been right-aligned in order to make the lack of right padding easier to see.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5507b.htm b/css1/sec5507b.htm new file mode 100755 index 0000000..c3b31e6 --- /dev/null +++ b/css1/sec5507b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.07 padding-right

CSS1 Test Suite: 5.5.07 padding-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-right: 25px; text-align: right; background-color: aqua;}
.two {padding-right: -10px; text-align: right; background-color: aqua;}


This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right padding (which should also be light blue) only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in no right padding, since negative padding values are not allowed, in the last line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right padding (which should also be light blue) only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in no right padding, since negative padding values are not allowed, in the last line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5508.htm b/css1/sec5508.htm new file mode 100755 index 0000000..d6feae9 --- /dev/null +++ b/css1/sec5508.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.08 padding-bottom

CSS1 Test Suite: 5.5.08 padding-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-bottom: 0;}
.one {padding-bottom: 0.5in; background-color: aqua;}
.two {padding-bottom: 25px; background-color: aqua;}
.three {padding-bottom: 5em; background-color: aqua;}
.four {padding-bottom: 25%; background-color: aqua;}
.five {padding-bottom: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a bottom padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element has a class of zero.

This element should have no bottom padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a bottom padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element has a class of zero.

This element should have no bottom padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5508b.htm b/css1/sec5508b.htm new file mode 100755 index 0000000..a3d4cac --- /dev/null +++ b/css1/sec5508b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.08 padding-bottom

CSS1 Test Suite: 5.5.08 padding-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-bottom: 25px; background-color: aqua;}
.two {padding-bottom: -10px; background-color: aqua;}


This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px bottom padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px bottom padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5509.htm b/css1/sec5509.htm new file mode 100755 index 0000000..8455bcc --- /dev/null +++ b/css1/sec5509.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.09 padding-left

CSS1 Test Suite: 5.5.09 padding-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-left: 0;}
.one {padding-left: 0.5in; background-color: aqua;}
.two {padding-left: 25px; background-color: aqua;}
.three {padding-left: 5em; background-color: aqua;}
.four {padding-left: 25%; background-color: aqua;}
.five {padding-left: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a left padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 5em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no left padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a left padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 5em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

  • The left padding on this unordered list has been set to 25 pixels, which will require some extra test in order to test.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its left padding also set to 25 pixels, which should combine with the list's padding to make 50 pixels of margin.

This element should have no left padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5509b.htm b/css1/sec5509b.htm new file mode 100755 index 0000000..dcd4212 --- /dev/null +++ b/css1/sec5509b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.09 padding-left

CSS1 Test Suite: 5.5.09 padding-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-left: 25px; background-color: aqua;}
.two {padding-left: -10px; background-color: aqua;}


This element is unstyled save for a background color of gray. However, it contains an inline element of class one which should result in 25-pixel left padding (which should also be a light blue) only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one which should result in 25-pixel left padding (which should also be a light blue) only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5510.htm b/css1/sec5510.htm new file mode 100755 index 0000000..f6cbea5 --- /dev/null +++ b/css1/sec5510.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.10 padding

CSS1 Test Suite: 5.5.10 padding


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding: 0;}
.one {padding: 0.5in; background-color: aqua;}
.two {padding: 25px; background-color: aqua;}
.three {padding: 5em; background-color: aqua;}
.four {padding: 25%; background-color: aqua;}
.five {padding: -20px; background-color: aqua;}

This element has a class of zero.

This element should have an overall padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have an overall padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5510b.htm b/css1/sec5510b.htm new file mode 100755 index 0000000..9a39d5f --- /dev/null +++ b/css1/sec5510b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.10 padding

CSS1 Test Suite: 5.5.10 padding


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding: 0;}
.one {padding: 25px; background-color: aqua;}
.two {padding: -10px; background-color: aqua;}


This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display above and below each line. However, there should be at least 25px of padding to the left side of the inline box in the first line it appears, and 25px of padding to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display above and below each line. However, there should be at least 25px of padding to the left side of the inline box in the first line it appears, and 25px of padding to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5511.htm b/css1/sec5511.htm new file mode 100755 index 0000000..e596696 --- /dev/null +++ b/css1/sec5511.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.11 border-top-width

CSS1 Test Suite: 5.5.11 border-top-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-top-width: 0;}
.one {border-top-width: 25px; border-style: solid;}
.two {border-top-width: thick; border-style: solid;}
.three {border-top-width: medium; border-style: solid;}
.four {border-top-width: thin; border-style: solid;}
.five {border-top-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This paragraph should have a top border width of 25 pixels.

This paragraph should have a thick top border width.

This paragraph should have a medium top border width.

This paragraph should have a thin top border width.

This paragraph should have no border and no extra "padding" on its top side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This paragraph should have a top border width of 25 pixels.

This paragraph should have a thick top border width.

This paragraph should have a medium top border width.

This paragraph should have a thin top border width.

This paragraph should have no border and no extra "padding" on its top side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5511b.htm b/css1/sec5511b.htm new file mode 100755 index 0000000..9ecd5dc --- /dev/null +++ b/css1/sec5511b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.11 border-top-width

CSS1 Test Suite: 5.5.11 border-top-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top-width: 25px; border-style: solid;}
.two {border-top-width: thin; border-style: solid;}
.three {border-top-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the top side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no top border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the top side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no top border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5512.htm b/css1/sec5512.htm new file mode 100755 index 0000000..d219d90 --- /dev/null +++ b/css1/sec5512.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.12 border-right-width

CSS1 Test Suite: 5.5.12 border-right-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-right-width: 0;}
.one {border-right-width: 25px; border-style: solid;}
.two {border-right-width: thick; border-style: solid;}
.three {border-right-width: medium; border-style: solid;}
.four {border-right-width: thin; border-style: solid;}
.five {border-right-width: 100px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a right border width of 25 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick right border width, which will be more obvious if the element is more than one line long.

This element should have a medium right border width, which will be more obvious if the element is more than one line long.

This element should have a thin right border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its right side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a right border width of 25 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick right border width, which will be more obvious if the element is more than one line long.

This element should have a medium right border width, which will be more obvious if the element is more than one line long.

This element should have a thin right border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its right side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5512b.htm b/css1/sec5512b.htm new file mode 100755 index 0000000..69304d6 --- /dev/null +++ b/css1/sec5512b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.12 border-right-width

CSS1 Test Suite: 5.5.12 border-right-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-right-width: 25px; border-style: solid;}
.two {border-right-width: thin; border-style: solid;}
.three {border-right-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the right side of the last box of the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no right border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the right side of the last box of the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no right border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5513.htm b/css1/sec5513.htm new file mode 100755 index 0000000..80c7694 --- /dev/null +++ b/css1/sec5513.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.13 border-bottom-width

CSS1 Test Suite: 5.5.13 border-bottom-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-bottom-width: 0;}
.one {border-bottom-width: 50px; border-style: solid;}
.two {border-bottom-width: thick; border-style: solid;}
.three {border-bottom-width: medium; border-style: solid;}
.four {border-bottom-width: thin; border-style: solid;}
.five {border-bottom-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a bottom border width of 50 pixels.

This element should have a thick bottom border width.

This element should have a medium bottom border width.

This element should have a thin bottom border width.

This element should have no border and no extra "padding" on its bottom side, as no border-style was set.

This element has a class of zero.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a bottom border width of 50 pixels.

This element should have a thick bottom border width.

This element should have a medium bottom border width.

This element should have a thin bottom border width.

This element should have no border and no extra "padding" on its bottom side, as no border-style was set.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5513b.htm b/css1/sec5513b.htm new file mode 100755 index 0000000..801b7bc --- /dev/null +++ b/css1/sec5513b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.13 border-bottom-width

CSS1 Test Suite: 5.5.13 border-bottom-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom-width: 25px; border-style: solid;}
.two {border-bottom-width: thin; border-style: solid;}
.three {border-bottom-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the bottom side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no bottom border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the bottom side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no bottom border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5514.htm b/css1/sec5514.htm new file mode 100755 index 0000000..92d495c --- /dev/null +++ b/css1/sec5514.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.14 border-left-width

CSS1 Test Suite: 5.5.14 border-left-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-left-width: 0;}
.one {border-left-width: 50px; border-style: solid;}
.two {border-left-width: thick; border-style: solid;}
.three {border-left-width: medium; border-style: solid;}
.four {border-left-width: thin; border-style: solid;}
.five {border-left-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a left border width of 50 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick left border width, which will be more obvious if the element is more than one line long.

This element should have a medium left border width, which will be more obvious if the element is more than one line long.

This element should have a thin left border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its left side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a left border width of 50 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick left border width, which will be more obvious if the element is more than one line long.

This element should have a medium left border width, which will be more obvious if the element is more than one line long.

This element should have a thin left border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its left side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5514b.htm b/css1/sec5514b.htm new file mode 100755 index 0000000..eebad6d --- /dev/null +++ b/css1/sec5514b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.14 border-left-width

CSS1 Test Suite: 5.5.14 border-left-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-left-width: 25px; border-style: solid;}
.two {border-left-width: thin; border-style: solid;}
.three {border-left-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the left side of the first box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no left border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the left side of the first box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no left border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5515.htm b/css1/sec5515.htm new file mode 100755 index 0000000..9e6bbf6 --- /dev/null +++ b/css1/sec5515.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.15 border-width

CSS1 Test Suite: 5.5.15 border-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-width: 0;}
.one {border-width: 50px; border-style: solid;}
.two {border-width: thick; border-style: solid;}
.three {border-width: medium; border-style: solid;}
.four {border-width: thin; border-style: solid;}
.five {border-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have an overall border width of 50 pixels.

This element should have a thick overall border width.

This element should have a medium overall border width.

This element should have a thin overall border width.

This element should have no border and no extra "padding" on any side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have an overall border width of 50 pixels.

This element should have a thick overall border width.

This element should have a medium overall border width.

This element should have a thin overall border width.

This element should have no border and no extra "padding" on any side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5515b.htm b/css1/sec5515b.htm new file mode 100755 index 0000000..9c84553 --- /dev/null +++ b/css1/sec5515b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.15 border-width

CSS1 Test Suite: 5.5.15 border-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-width: 25px; border-style: solid;}
.two {border-width: thin; border-style: solid;}
.three {border-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on each side of each box in the inline element. There is also an inline element of class three, which should have no border width because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on each side of each box in the inline element. There is also an inline element of class three, which should have no border width because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5516.htm b/css1/sec5516.htm new file mode 100755 index 0000000..5c4e7b3 --- /dev/null +++ b/css1/sec5516.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.16 border-color

CSS1 Test Suite: 5.5.16 border-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-color: purple; border-style: solid;}
.two {border-color: purple; border-width: medium; border-style: solid;}
.three {border-color: purple green blue yellow; border-width: medium; border-style: solid;}

This element should have a purple border surrounding it.

This element should have a medium-width purple border surrounding it.

This element should be surrounded by a medium width border which is purple on top, green on the right side, blue on the bottom, and yellow on the left side.

TABLE Testing Section
 

This element should have a purple border surrounding it.

This element should have a medium-width purple border surrounding it.

This element should be surrounded by a medium width border which is purple on top, green on the right side, blue on the bottom, and yellow on the left side.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5516b.htm b/css1/sec5516b.htm new file mode 100755 index 0000000..30aa071 --- /dev/null +++ b/css1/sec5516b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.16 border-color

CSS1 Test Suite: 5.5.16 border-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-color: purple; border-style: solid;}
.two {border-color: purple; border-width: medium; border-style: solid;}
.three {border-color: purple green blue yellow; border-width: medium; border-style: solid;}

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, class two, and class three. The effect for each inline element should be to have a purple medium-width solid border in the first and second cases, and a purple-green-blue-yellow medium-width solid border in the third. The line-height of the parent element should not change at all, on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, class two, and class three. The effect for each inline element should be to have a purple medium-width solid border in the first and second cases, and a purple-green-blue-yellow medium-width solid border in the third. The line-height of the parent element should not change at all, on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5517.htm b/css1/sec5517.htm new file mode 100755 index 0000000..f5a6eba --- /dev/null +++ b/css1/sec5517.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.17 border-style

CSS1 Test Suite: 5.5.17 border-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-style: dotted; border-color: black; border-width: thick;}
.two {border-style: dashed; border-color: black; border-width: thick;}
.three {border-style: solid; border-color: black; border-width: thick;}
.four {border-style: double; border-color: black; border-width: thick;}
.five {border-style: groove; border-color: olive; border-width: thick;}
.six {border-style: ridge; border-color: olive; border-width: thick;}
.seven {border-style: inset; border-color: olive; border-width: thick;}
.eight {border-style: outset; border-color: olive; border-width: thick;}
.nine {border-style: double groove; border-color: purple; border-width: thick;}
.ten {border-style: double groove ridge inset;
   border-color: purple; border-width: thick;}
.eleven {border-style: none; border-color: red; border-width: thick;}

This paragraph should have a thick black dotted border all the way around.

This paragraph should have a thick black dashed border all the way around.

This paragraph should have a thick black solid border all the way around.

This paragraph should have a thick black double border all the way around.

This paragraph should have a thick olive groove border all the way around.

This paragraph should have a thick olive ridge border all the way around.

This paragraph should have a thick olive inset border all the way around.

This paragraph should have a thick olive outset border all the way around.

This paragraph should have thick double top and bottom borders, and thick grooved side borders. The color of all four sides should be based on purple.

This paragraph should have, in clockwise order from the top, a double, grooved, ridged, and inset thick border. The color of all four sides should be based on purple.

This paragraph should have no border at all.

TABLE Testing Section
 

This paragraph should have a thick black dotted border all the way around.

This paragraph should have a thick black dashed border all the way around.

This paragraph should have a thick black solid border all the way around.

This paragraph should have a thick black double border all the way around.

This paragraph should have a thick olive groove border all the way around.

This paragraph should have a thick olive ridge border all the way around.

This paragraph should have a thick olive inset border all the way around.

This paragraph should have a thick olive outset border all the way around.

This paragraph should have thick double top and bottom borders, and thick grooved side borders. The color of all four sides should be based on purple.

This paragraph should have, in clockwise order from the top, a double, grooved, ridged, and inset thick border. The color of all four sides should be based on purple.

This paragraph should have no border at all.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5517b.htm b/css1/sec5517b.htm new file mode 100755 index 0000000..636ff07 --- /dev/null +++ b/css1/sec5517b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.17 border-style

CSS1 Test Suite: 5.5.17 border-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-style: dashed; border-color: black; border-width: thick;}
.two {border-style: groove; border-color: purple; border-width: thick;}
.three {border-style: none; border-color: purple; border-width: thick;}

This is an unstyled element, save for the background color, and it contains inline elements with classes of class one, which will result in a dashed thick black border; class two, which should result in a grooved thick purple border, and class three, which should result in no border at all. The line-height of the parent element should not change, on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and it contains inline elements with classes of class one, which will result in a dashed thick black border; class two, which should result in a grooved thick purple border, and class three, which should result in no border at all. The line-height of the parent element should not change, on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5518.htm b/css1/sec5518.htm new file mode 100755 index 0000000..e7fbe97 --- /dev/null +++ b/css1/sec5518.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.18 border-top

CSS1 Test Suite: 5.5.18 border-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top: purple double 10px;}
.two {border-top: purple thin solid;}
.three {border-top: black medium solid;}
TD {border-top: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their top sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel top border.

This paragraph should have a thin purple top border.

Every cell in this table should have a 2-pixel solid green top border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their top sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel top border.

This paragraph should have a thin purple top border.

Every cell in this table should have a 2-pixel solid green top border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this list should have a medium-width black border at its top.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5518b.htm b/css1/sec5518b.htm new file mode 100755 index 0000000..c628094 --- /dev/null +++ b/css1/sec5518b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.18 border-top

CSS1 Test Suite: 5.5.18 border-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top: purple double 10px;}
.two {border-top: purple thin solid;}


This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double top border; and class two, which should have a thin solid purple top border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double top border; and class two, which should have a thin solid purple top border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5519.htm b/css1/sec5519.htm new file mode 100755 index 0000000..918e9d3 --- /dev/null +++ b/css1/sec5519.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.19 border-right

CSS1 Test Suite: 5.5.19 border-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-right: 20px;}
.one {border-right: purple double 10px;}
.two {border-right: purple thin solid;}
.threea {border-right: black medium solid;}
.threeb {border-right: purple medium solid;}
.threec {border-right: blue medium solid;}
TD {border-right: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their right sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel right border.

This paragraph should have a thin purple right border.

Every cell in this table should have a 2-pixel solid green right border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their right sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel right border.

This paragraph should have a thin purple right border.

Every cell in this table should have a 2-pixel solid green right border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this 'parent' list should have a medium-width border along its right side, in each of three colors. The first item's border should travel the entire height the nested list (to end near the baseline of the line "...nested within the list item."), even though the nested list does not have any border styles set. The borders should line up together at the right edge of the document's body, as each list element has a default width of 100%.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5519b.htm b/css1/sec5519b.htm new file mode 100755 index 0000000..d699a37 --- /dev/null +++ b/css1/sec5519b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.19 border-right

CSS1 Test Suite: 5.5.19 border-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-right: 20px;}
.one {border-right: purple double 10px;}
.two {border-right: purple thin solid;}


This paragraph has a background color of silver and a 20-pixel right margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double right border; and class two, which should have a thin solid purple right border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This paragraph has a background color of silver and a 20-pixel right margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double right border; and class two, which should have a thin solid purple right border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5520.htm b/css1/sec5520.htm new file mode 100755 index 0000000..8112b3b --- /dev/null +++ b/css1/sec5520.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.20 border-bottom

CSS1 Test Suite: 5.5.20 border-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom: purple double 10px;}
.two {border-bottom: purple thin solid;}
.three {border-bottom: black medium solid;}
TD {border-bottom: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their bottom sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel bottom border.

This paragraph should have a thin purple bottom border.

Every cell in this table should have a 2-pixel solid green bottom border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their bottom sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel bottom border.

This paragraph should have a thin purple bottom border.

Every cell in this table should have a 2-pixel solid green bottom border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this list should have a medium-width black border at its bottom, which for the first item means that it should appear beneath the nested list (below the line "...nested within the list item.").

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5520b.htm b/css1/sec5520b.htm new file mode 100755 index 0000000..75ad4b1 --- /dev/null +++ b/css1/sec5520b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.20 border-bottom

CSS1 Test Suite: 5.5.20 border-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom: purple double 10px;}
.two {border-bottom: purple thin solid;}


This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double bottom border; and class two, which should have a thin solid purple bottom border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double bottom border; and class two, which should have a thin solid purple bottom border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5521.htm b/css1/sec5521.htm new file mode 100755 index 0000000..ac3f9c0 --- /dev/null +++ b/css1/sec5521.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.21 border-left

CSS1 Test Suite: 5.5.21 border-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-left: 20px;}
.one {border-left: purple double 10px;}
.two {border-left: purple thin solid;}
.threea {border-left: black medium solid;}
.threeb {border-left: purple medium solid;}
.threec {border-left: blue medium solid;}
TD {border-left: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their left sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel left border.

This paragraph should have a thin purple left border.

Every cell in this table should have a 2-pixel solid green left border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their left sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel left border.

This paragraph should have a thin purple left border.

Every cell in this table should have a 2-pixel solid green left border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this 'parent' list should have a medium-width border along its left side, in each of three colors. The first item's border should travel the entire height the nested list (to end near the baseline of the line "...nested within the list item."), even though the nested list does not have any border styles set.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5521b.htm b/css1/sec5521b.htm new file mode 100755 index 0000000..a84cca4 --- /dev/null +++ b/css1/sec5521b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.21 border-left

CSS1 Test Suite: 5.5.21 border-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-left: 20px;}
.one {border-left: purple double 10px;}
.two {border-left: purple thin solid;}


This paragraph has a background color of silver and a 20-pixel left margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double left border; and class two, which should have a thin solid purple left border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This paragraph has a background color of silver and a 20-pixel left margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double left border; and class two, which should have a thin solid purple left border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5522.htm b/css1/sec5522.htm new file mode 100755 index 0000000..dfff322 --- /dev/null +++ b/css1/sec5522.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.22 border

CSS1 Test Suite: 5.5.22 border


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border: medium black solid;}
.two {border: thin maroon ridge;}
.three {border: 10px teal outset;}
.four {border: 10px olive inset;}
.five {border: 10px maroon;}
.six {border: maroon double;}
.seven {border: left red solid;}
.eight {border: 0px;}
TD {border: 2px solid green;}

Note that all table cells on this page should have a two-pixel solid green border along all four sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a medium black solid border all the way around.

This paragraph should have a thin maroon ridged border all the way around.

This paragraph should have a ten-pixel-wide teal outset border all the way around.

This paragraph should have a ten-pixel-wide olive inset border all the way around.

This paragraph should have no border around it, as the border-style was not set, and it should not be offset in any way.

This paragraph should have a medium maroon double border around it, even though border-width was not explicitly set.

This paragraph should have no border around it, as its declaration is invalid and should be ignored.

The following image is also an anchor which points to a target on this page, but it should not have a border around it: [Image].

Every cell in this table should have a 2-pixel solid green border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!

This is an unstyled element.

TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along all four sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a medium black solid border all the way around.

This paragraph should have a thin maroon ridged border all the way around.

This paragraph should have a ten-pixel-wide teal outset border all the way around.

This paragraph should have a ten-pixel-wide olive inset border all the way around.

This paragraph should have no border around it, as the border-style was not set, and it should not be offset in any way.

This paragraph should have a medium maroon double border around it, even though border-width was not explicitly set.

This paragraph should have no border around it, as its declaration is invalid and should be ignored.

The following image is also an anchor which points to a target on this page, but it should not have a border around it: [Image].

Every cell in this table should have a 2-pixel solid green border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!

This is an unstyled element.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5522b.htm b/css1/sec5522b.htm new file mode 100755 index 0000000..d340dc5 --- /dev/null +++ b/css1/sec5522b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.22 border

CSS1 Test Suite: 5.5.22 border


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border: 10px teal outset;}
.two {border: 10px olive inset;}


This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, which should result in a 10-pixel outset teal border; and class two, which should result in a 10-pixel inset olive border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, which should result in a 10-pixel outset teal border; and class two, which should result in a 10-pixel inset olive border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5523.htm b/css1/sec5523.htm new file mode 100755 index 0000000..e242be7 --- /dev/null +++ b/css1/sec5523.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.23 width

CSS1 Test Suite: 5.5.23 width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {width: 50px;}
.two {width: 50%;}
TABLE {width: 50%;}

[Image]

The square above should be fifty pixels wide.

[Image]

The square above should be half as wide as the image's parent element (either the BODY or the table cell).

This paragraph should be half the width of its parent element (either the BODY or the table, which should itself be half as wide as the BODY element). This is extra text included to ensure that this will be a fair test of the width property without the need for the user to resize the viewing window.

TABLE Testing Section
  [Image]

The square above should be fifty pixels wide.

[Image]

The square above should be half as wide as the image's parent element (either the BODY or the table cell).

This paragraph should be half the width of its parent element (either the BODY or the table, which should itself be half as wide as the BODY element). This is extra text included to ensure that this will be a fair test of the width property without the need for the user to resize the viewing window.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5524.htm b/css1/sec5524.htm new file mode 100755 index 0000000..8d3145b --- /dev/null +++ b/css1/sec5524.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.24 height

CSS1 Test Suite: 5.5.24 height


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {height: 50px;}
.two {height: 100px;}


[Image]

The square above should be fifty pixels tall.

[Image]

The square above should be 100 pixels tall and wide.

[Image]

The rectangular image above should be 100 pixels tall and 30 pixels wide (the original image is 50x15, and the size has been doubled using the height property).

TABLE Testing Section
  [Image]

The square above should be fifty pixels tall.

[Image]

The square above should be 100 pixels tall and wide.

[Image]

The rectangular image above should be 100 pixels tall and 30 pixels wide (the original image is 50x15, and the size has been doubled using the height property).


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5525.htm b/css1/sec5525.htm new file mode 100755 index 0000000..69408a6 --- /dev/null +++ b/css1/sec5525.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {float: left;}
.two {float: right;}


[Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window. In this case, it is the image which has been floated to the left.



[Image]

This text should be flowing past a tall orange rectangle on the right side of the browser window. In this case, it is the image which has been floated to the right.

TABLE Testing Section
  [Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window. In this case, it is the image which has been floated to the left.



[Image]

This text should be flowing past a tall orange rectangle on the right side of the browser window. In this case, it is the image which has been floated to the right.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5525b.htm b/css1/sec5525b.htm new file mode 100755 index 0000000..1144b12 --- /dev/null +++ b/css1/sec5525b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.test {background: white; font-size: 20px;
        margin-left: 30px; margin-right: 10px; padding: 0; border: 0;}
IMG {padding: 0; border: 0; margin: 0;}
P.test IMG {float: left;}
#img2 {margin-top: 30px; margin-left: 30px;}
#img3 {margin-top: -30px; margin-left: -30px;}
#img4 {margin-right: 30px; margin-bottom: 30px;}
#img5 {margin-right: -30px; margin-bottom: -30px;}


This paragraph should have a white background which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever. If the background of the entire box is not white, this may cause problems with the following tests; at any rate, it must be taken into account.

[Image] The image in the upper left corner of this paragraph should be floated left, and nothing more. The edges of the white background should line up with the top and left edges of the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed down and to the right 30 pixels each from the upper left corner of the paragraph's box, and displace the paragraph text accordingly. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed up and to the left 30 pixels each from the upper left corner of the paragraph's box, thus causing the edges of the white background to align with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, there should be 30 pixels of space between the right and bottom edges of the image and the paragraph text around it. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, the text should overlap the image's right and bottom sides, lining up with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

TABLE Testing Section
 

This paragraph should have a white background which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever. If the background of the entire box is not white, this may cause problems with the following tests; at any rate, it must be taken into account.

[Image] The image in the upper left corner of this paragraph should be floated left, and nothing more. The edges of the white background should line up with the top and left edges of the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed down and to the right 30 pixels each from the upper left corner of the paragraph's box, and displace the paragraph text accordingly. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed up and to the left 30 pixels each from the upper left corner of the paragraph's box, thus causing the edges of the white background to align with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, there should be 30 pixels of space between the right and bottom edges of the image and the paragraph text around it. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, the text should overlap the image's right and bottom sides, lining up with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5525c.htm b/css1/sec5525c.htm new file mode 100755 index 0000000..222ebfa --- /dev/null +++ b/css1/sec5525c.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align: justify;}
.one {float: left; width: 50%; background-color: yellow; padding: 0; margin: 0;}
.two {float: left; background-color: yellow; width: 100%;
      margin: 0; padding: 0; border-width: 0;}
.three {float: none;}
.four {float: left; font-size: 200%; font-weight: bold;
    width: 1.5em; background-color: silver;}
.five {float: right; width: 20em;
      background-color: yellow; border: 3px solid red;
      padding: 5px; margin: 10px;}
.six {float: right; width: 20em;
      background-color: yellow; border: none;
      padding: 5px; margin: 10px;}
.seven {float: right; width: 50%;
       background-color: yellow; border: 1px solid gray;}
.eight {float: left; width: 25%;
        background-color: #66CCFF;
        padding: 0; margin: 0}
.nine {float: right; width: 25%;
       background-color: yellow;
       padding: 0; margin: 0}


This paragraph is of class "one". It has a width of 50% and is floated to the left.

This paragraph should start on the right side of a yellow box which contains the previous paragraph. Since the text of this element is much longer than the text in the previous element, the text will wrap around the yellow box. There is no padding, border or margins on this and the previous element, so the text of the two elements should be very close to each other.



This paragraph is of class "two". Since the width has been set to 100%, it should automatically be as wide as its parent element allows it to be. Therefore, even though the element is floated, there is no room for other content on the sides and a orange square image should be seen AFTER the paragraph, not next to it. A yellow background has been added to this paragraph for diagnostic purposes.

[Image]

This paragraph is floated to the left and the orange square image should appear to the right of the paragraph. This paragraph has a yellow background and no padding, margin or border. The right edge of this yellow box should be horizontally aligned with the left edge of the yellow box undernearth.

[Image]

This paragraph is floated to the right (using a STYLE attribute) and the orange square image should appear to the left of the paragraph. This paragraph has a yellow background and no padding, margin or border. The left edge of this yellow box should be horizonally aligned with the right edge of the yellow box above.

[Image]

The first letter (a "T") of this paragraph should float left and be twice the font-size of the rest of the paragraph, as well as bold, with a content width of 1.5em and a background-color of silver. The top of the big letter "T" should be vertically aligned with the top of the first line of this paragraph. This is commonly known as "drop-cap".



This paragraph should be floated to the right, sort of like a 'sidebar' in a magazine article. Its width is 20em so the box should not be reformatted when the size of the viewport is changed (e.g. when the window is resized). The background color of the element is yellow, and there should be a 3px solid red border outside a 5px wide padding. Also, the element has a 10px wide margin around it where the blue background of the paragraph in the normal flow should shine through.

This paragraph is not floating. If there is enough room, the textual content of the paragraph should appear on the left side of the yellow "sidebar" on the right. The content of this element should flow around the floated element. However, the floated element may or may not be obscured by the blue background of this element, as the specification does not say which is drawn "on top." Even if the floated element is obscured, it still forces the content of this element to flow around it. If the floated element is not obscured, then the blue rectangle of this paragraph should extend 10px above and to the right of the sidebar's red border, due to the margin styles set for the floated element.



This paragraph is placed inside a DIV element which is floated to the right. The width of the DIV element is 20em. The background is yellow and there is a 5px padding, a 10px margin and no border. Since it is floated, the yellow box should be rendered on top of the background and borders of adjacent non-floated elements. To the left of this yellow box there should be a short paragraph with a blue background and a red border. The yellow box should be rendered on top of the bottom red border. I.e., the bottom red border will appear broken where it's overlaid by the yellow rectangle.

See description in the box on the right side



This paragraph is inside a DIV which is floated left. Its background is blue and the width is 25%.

This paragraph is inside a DIV which is floated right. Its background is yellow and the width is 25%.

This paragraph should appear between a blue box (on the left) and a yellow box (on the right).



See description in the box on the left side.

This paragraph is inside a DIV which is floated left. The background of the DIV element is blue and its width is 75%. This text should all be inside the blue rectangle. The blue DIV element has another DIV element as a child. It has a yellow background color and is floated to the right. Since it is a child of the blue DIV, the yellow DIV should appear inside the blue rectangle. Due to it being floated to the right and having a 10px right margin, the yellow rectange should have a 10px blue stripe on its right side.



TABLE Testing Section
 

This paragraph is of class "one". It has a width of 50% and is floated to the left.

This paragraph should start on the right side of a yellow box which contains the previous paragraph. Since the text of this element is much longer than the text in the previous element, the text will wrap around the yellow box. There is no padding, border or margins on this and the previous element, so the text of the two elements should be very close to each other.



This paragraph is of class "two". Since the width has been set to 100%, it should automatically be as wide as its parent element allows it to be. Therefore, even though the element is floated, there is no room for other content on the sides and a orange square image should be seen AFTER the paragraph, not next to it. A yellow background has been added to this paragraph for diagnostic purposes.

[Image]

This paragraph is floated to the left and the orange square image should appear to the right of the paragraph. This paragraph has a yellow background and no padding, margin or border. The right edge of this yellow box should be horizontally aligned with the left edge of the yellow box undernearth.

[Image]

This paragraph is floated to the right (using a STYLE attribute) and the orange square image should appear to the left of the paragraph. This paragraph has a yellow background and no padding, margin or border. The left edge of this yellow box should be horizonally aligned with the right edge of the yellow box above.

[Image]

The first letter (a "T") of this paragraph should float left and be twice the font-size of the rest of the paragraph, as well as bold, with a content width of 1.5em and a background-color of silver. The top of the big letter "T" should be vertically aligned with the top of the first line of this paragraph. This is commonly known as "drop-cap".



This paragraph should be floated to the right, sort of like a 'sidebar' in a magazine article. Its width is 20em so the box should not be reformatted when the size of the viewport is changed (e.g. when the window is resized). The background color of the element is yellow, and there should be a 3px solid red border outside a 5px wide padding. Also, the element has a 10px wide margin around it where the blue background of the paragraph in the normal flow should shine through.

This paragraph is not floating. If there is enough room, the textual content of the paragraph should appear on the left side of the yellow "sidebar" on the right. The content of this element should flow around the floated element. However, the floated element may or may not be obscured by the blue background of this element, as the specification does not say which is drawn "on top." Even if the floated element is obscured, it still forces the content of this element to flow around it. If the floated element is not obscured, then the blue rectangle of this paragraph should extend 10px above and to the right of the sidebar's red border, due to the margin styles set for the floated element.



This paragraph is placed inside a DIV element which is floated to the right. The width of the DIV element is 20em. The background is yellow and there is a 5px padding, a 10px margin and no border. Since it is floated, the yellow box should be rendered on top of the background and borders of adjacent non-floated elements. To the left of this yellow box there should be a short paragraph with a blue background and a red border. The yellow box should be rendered on top of the bottom red border. I.e., the bottom red border will appear broken where it's overlaid by the yellow rectangle.

See description in the box on the right side



This paragraph is inside a DIV which is floated left. Its background is blue and the width is 25%.

This paragraph is inside a DIV which is floated right. Its background is yellow and the width is 25%.

This paragraph should appear between a blue box (on the left) and a yellow box (on the right).



See description in the box on the left side.

This paragraph is inside a DIV which is floated left. The background of the DIV element is blue and its width is 75%. This text should all be inside the blue rectangle. The blue DIV element has another DIV element as a child. It has a yellow background color and is floated to the right. Since it is a child of the blue DIV, the yellow DIV should appear inside the blue rectangle. Due to it being floated to the right and having a 10px right margin, the yellow rectange should have a 10px blue stripe on its right side.




[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5525d.htm b/css1/sec5525d.htm new file mode 100755 index 0000000..ad52f45 --- /dev/null +++ b/css1/sec5525d.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align:  justify;}

DIV.yellow, DIV.blue, DIV.red, DIV.green {
 width: 60px; padding: 20px; margin: 10px;
 border: 20px solid black; float: left; text-align: center;
 font-family: "Times New Roman",Times,serif;}
DIV.yellow {margin-left: 0px; background: yellow; color: black;}
DIV.blue {background: blue; color: white;}
DIV.red {background: red; color: black;}
DIV.green {background: green; color: white;}
DIV.below {clear: both;}
TABLE {margin: 20px 0px;}


The four floating DIV elements below should appear next to each other horizontally. The table at the bottom of this page indicates how the DIV elements should be laid out horizontally. They should align with each other.

Yellow

Blue

Red

Green

;
TABLE Testing Section
 

The four floating DIV elements below should appear next to each other horizontally. The table at the bottom of this page indicates how the DIV elements should be laid out horizontally. They should align with each other.

Yellow

Blue

Red

Green

;

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5526.htm b/css1/sec5526.htm new file mode 100755 index 0000000..563e514 --- /dev/null +++ b/css1/sec5526.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {clear: left;}
.two {clear: right;}
.three {clear: both;}
.four {clear: none;}

[Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window.


[Image]

This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it.


[Image]

This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it.


[Image] [Image]

This paragraph should appear below the two tall orange rectangles, and not flow between them.

[Image] [Image]

This paragraph should be between both tall orange rectangles.


TABLE Testing Section
  [Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window.


[Image]

This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it.


[Image]

This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it.


[Image] [Image]

This paragraph should appear below the two tall orange rectangles, and not flow between them.

[Image] [Image]

This paragraph should be between both tall orange rectangles.



[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5526b.htm b/css1/sec5526b.htm new file mode 100755 index 0000000..195f465 --- /dev/null +++ b/css1/sec5526b.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align:  justify;}

DIV.menu {float: left; clear: left; width: 11em;
          margin: 0; margin-bottom: 10px; padding: 0.5em;}
DIV.menu H1 {font-size: 1.2em; margin: 0; padding: 0;}
DIV.menu UL {margin: 0.2em 0.3em 0.2em 1em; padding: 0;}
DIV.article {padding: 0.5em; margin: 0; margin-left: 14em; margin-right: 2em;
             color: black; background: yellow; clear: none;}


The 'clear' property

This page has two floating "menus" on the side; one has a green background, and the other a blue background. Due to settings on the 'float' and 'clear' properties, the two menus should appear on the left side of the page, the blue below the green. There should be a 10px gap between the two menus. There should also be a 10px gap between the top menu and the top of the page.

The top of the yellow rectangle (to which this paragraph belongs) should be vertically aligned with the top of the green rectangle.

TABLE Testing Section
 

The 'clear' property

This page has two floating "menus" on the side; one has a green background, and the other a blue background. Due to settings on the 'float' and 'clear' properties, the two menus should appear on the left side of the page, the blue below the green. There should be a 10px gap between the two menus. There should also be a 10px gap between the top menu and the top of the page.

The top of the yellow rectangle (to which this paragraph belongs) should be vertically aligned with the top of the green rectangle.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec5526c.htm b/css1/sec5526c.htm new file mode 100755 index 0000000..2459e9b --- /dev/null +++ b/css1/sec5526c.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the linked page are:

html { font: 10px/1 Verdana, sans-serif;
background-color: blue; color: white; }

body { margin: 1.5em; border: .5em solid black;
padding: 0; width: 48em; background-color: white; }

dl { margin: 0; border: 0; padding: .5em; }

dt { background-color: rgb(204,0,0); margin: 0; padding: 1em;
width: 10.638%; /* refers to parent element's width of 47em. = 5em or 50px */
height: 28em; border: .5em solid black; float: left; }

dd { float: right; margin: 0 0 0 1em; border: 1em solid black;
padding: 1em; width: 34em; height: 27em; }

ul { margin: 0; border: 0; padding: 0; }

li { display: block; /* i.e., suppress marker */ color: black;
height: 9em; width: 5em; margin: 0; border: .5em solid black;
padding: 1em; float: left; background-color: #FC0; }

#bar { background-color: black; color: white; width: 41.17%; /* = 14em */
border: 0; margin: 0 1em; } 

#baz { margin: 1em 0; border: 0; padding: 1em; width: 10em;
height: 10em; background-color: black; color: white; }

form { margin: 0; display: inline; }

p { margin: 0; }

form p { line-height: 1.9; }

blockquote { margin: 1em 1em 1em 2em; border-width: 1em 1.5em 2em .5em;
border-style: solid; border-color: black; padding: 1em 0; width: 5em;
height: 9em; float: left; background-color: #FC0; color: black; }

address { font-style: normal; }

h1 { background-color: black; color: white; float: left; margin: 1em 0;
border: 0; padding: 1em; width: 10em; height: 10em; font-weight: normal;
font-size: 1em; }

The test itself is on a separate page.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec56.htm b/css1/sec56.htm new file mode 100755 index 0000000..e99bc0f --- /dev/null +++ b/css1/sec56.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6 Classification Properties

CSS1 Test Suite: 5.6 Classification Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec561.htm b/css1/sec561.htm new file mode 100755 index 0000000..001f23a --- /dev/null +++ b/css1/sec561.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.1 display

CSS1 Test Suite: 5.6.1 display


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {display: block;}
.two {display: inline;}
.three {display: list-item; list-style-type: square; margin-left: 3em;}
.four {display: none; color: red;}
I {display: block;}

This sentence should be a block-level element.

This sentence should be part of an inline element, as are the next three.

This sentence and the next two are part of a second inline element. They should therefore appear, along with the sentence above, to be all one paragraph which is four sentences long. If this is not the case, then the keyword inline is being ignored.

This sentence should be treated as a list-item, and therefore be rendered however this user agent displays list items (if list-style-type is supported, there will be a square for the item marker). A 3em left margin has been applied in order to ensure that there is space for the list-item marker.

The next paragraph should be invisible (if it's visible, you'll see red text).

This paragraph should be invisible.

There should be no text after the colon: fnord.

The italicized text in this paragraph should be a block-level element.

TABLE Testing Section
 

This sentence should be a block-level element.

This sentence should be part of an inline element, as are the next three.

This sentence and the next two are part of a second inline element. They should therefore appear, along with the sentence above, to be all one paragraph which is four sentences long. If this is not the case, then the keyword inline is being ignored.

This sentence should be treated as a list-item, and therefore be rendered however this user agent displays list items (if list-style-type is supported, there will be a square for the item marker). A 3em left margin has been applied in order to ensure that there is space for the list-item marker.

The next paragraph should be invisible (if it's visible, you'll see red text).

This paragraph should be invisible.

There should be no text after the colon: fnord.

The italicized text in this paragraph should be a block-level element.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec562.htm b/css1/sec562.htm new file mode 100755 index 0000000..44c752c --- /dev/null +++ b/css1/sec562.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.2 white-space

CSS1 Test Suite: 5.6.2 white-space


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {white-space: pre;}
.two {white-space: nowrap;}
.three {white-space: normal;}


This sentence should show extra space where there would ordinarily not be any. There should also be preservation of returns as this sentence very clearly demonstrates.

This sentence should not word-wrap, no matter how long the sentence is, as it has been set to nowrap and that should have the obvious effect.

This sentence should show extra space, except in the second half.

TABLE Testing Section
 

This sentence should show extra space where there would ordinarily not be any. There should also be preservation of returns as this sentence very clearly demonstrates.

This sentence should not word-wrap, no matter how long the sentence is, as it has been set to nowrap and that should have the obvious effect.

This sentence should show extra space, except in the second half.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec563.htm b/css1/sec563.htm new file mode 100755 index 0000000..63a2034 --- /dev/null +++ b/css1/sec563.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.3 list-style-type

CSS1 Test Suite: 5.6.3 list-style-type


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-type: disc;}
.two {list-style-type: circle;}
.three {list-style-type: square;}
.four {list-style-type: lower-roman;}
.five {list-style-type: upper-roman;}
.six {list-style-type: lower-alpha;}
.seven {list-style-type: upper-alpha;}
.eight {list-style-type: decimal;}
.nine {list-style-type: none;}


  1. This list...
  2. ...should feature...
  3. ...lowercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase letters for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase letters for each item.
  1. This list should feature...
  2. ...letters for each item...
  3. ...except this one.
TABLE Testing Section
 
  • This list...
  • ...should feature...
  • ...discs for each item.
  • This list...
  • ...should feature...
  • ...circles for each item.
  • This list...
  • ...should feature...
  • ...squares for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase letters for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase letters for each item.
  1. This list should feature...
  2. ...letters for each item...
  3. ...except this one.
  • This list...
  • ...should feature...
  • ...nothing for each item.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec564.htm b/css1/sec564.htm new file mode 100755 index 0000000..05c11ca --- /dev/null +++ b/css1/sec564.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.4 list-style-image

CSS1 Test Suite: 5.6.4 list-style-image


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-image: url(orancirc.gif);}
.two {list-style-image: none;}


TABLE Testing Section
 
  • This list...
  • ...should feature...
  • ...orange circle images for each item.
  • This list...
  • ...should feature...
  • ...standard list markers for each item.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec565.htm b/css1/sec565.htm new file mode 100755 index 0000000..006ee99 --- /dev/null +++ b/css1/sec565.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.5 list-style-position

CSS1 Test Suite: 5.6.5 list-style-position


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-position: outside;}
.two {list-style-position: inside;}


TABLE Testing Section
 
  • The text in this item should behave as expected; that is, it should line up with itself on the left margin, leaving blank space beneath the bullet.
  • The text in this item should not behave as expected; that is, it should line up with the bullet on the left margin, leaving no blank space beneath the bullet.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec566.htm b/css1/sec566.htm new file mode 100755 index 0000000..9d75a54 --- /dev/null +++ b/css1/sec566.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 5.6.6 list-style

CSS1 Test Suite: 5.6.6 list-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style: upper-alpha inside;}
.two {list-style: url(oransqr.gif) disc outside;}

TABLE Testing Section
 
  • The text in this item should not behave as expected; that is, it should line up with the capital-A on the left margin, leaving no blank space beneath the capital-A.
  • The text in this item have an orange square for its bullet; failing that, a disc. Also, the bullet should be outside the text block, as the list has been set to 'outside'.

[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec60.htm b/css1/sec60.htm new file mode 100755 index 0000000..0c230f0 --- /dev/null +++ b/css1/sec60.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 6.0 Units

CSS1 Test Suite: 6.0 Units


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec61.htm b/css1/sec61.htm new file mode 100755 index 0000000..39acf6d --- /dev/null +++ b/css1/sec61.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 6.1 Length Units

CSS1 Test Suite: 6.1 Length Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {margin-left: 0;}
.one {margin-left: 3em;}
.two {margin-left: 3ex;}
.three {margin-left: 36px;}
.four {margin-left: 0.5in;}
.five {margin-left: 1.27cm;}
.six {margin-left: 12.7mm;}
.seven {margin-left: 36pt;}
.eight {margin-left: 3pc;}
.nine {margin-left: +3pc;}
.ten {font-size: 40px; border-left: 1ex solid purple; background-color: aqua;}

This paragraph has no left margin. The following paragraphs have all been given a left margin and their left (outer) edges should therefore be appropriately shifted to the right of this paragraph's left edge.

This paragraph should have a left margin of 3em.

This paragraph should have a left margin of 3ex.

This paragraph should have a left margin of 36 pixels.

This paragraph should have a left margin of half an inch.

This paragraph should have a left margin of 1.27cm.

This paragraph should have a left margin of 12.7mm.

This paragraph should have a left margin of 36 points.

This paragraph should have a left margin of 3 picas.

This paragraph should have a left margin of 3 picas (the plus sign should make no difference).

This element has a font-size of 40px and a border-left of 1ex solid purple. This should make the left border the same number of pixels as the lower-case 'x' in this element's font, as well as solid purple.

TABLE Testing Section
 

This paragraph has no left margin. The following paragraphs have all been given a left margin and their left (outer) edges should therefore be appropriately shifted to the right of this paragraph's left edge.

This paragraph should have a left margin of 3em.

This paragraph should have a left margin of 3ex.

This paragraph should have a left margin of 36 pixels.

This paragraph should have a left margin of half an inch.

This paragraph should have a left margin of 1.27cm.

This paragraph should have a left margin of 12.7mm.

This paragraph should have a left margin of 36 points.

This paragraph should have a left margin of 3 picas.

This paragraph should have a left margin of 3 picas (the plus sign should make no difference).

This element has a font-size of 40px and a border-left of 1ex solid purple. This should make the left border the same number of pixels as the lower-case 'x' in this element's font, as well as solid purple.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec62.htm b/css1/sec62.htm new file mode 100755 index 0000000..ccdfc9f --- /dev/null +++ b/css1/sec62.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 6.2 Percentage Units

CSS1 Test Suite: 6.2 Percentage Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero { background: yellow }
.one { margin-left: 25%; margin-right: 25%; background: white }
.two { margin-left: 50%; margin-right: 0%; background: white }
.three {margin-left: 25%;}


This paragraph should be centered within its yellow containing block and its width should be half of the containing block.

This paragraph should be right-aligned within its yellow containing block and its width should be half of the containing block.

This paragraph should have a left margin of 25% the width of its parent element, which should require some extra text in order to test effectively.

TABLE Testing Section
 

This paragraph should be centered within its yellow containing block and its width should be half of the containing block.

This paragraph should be right-aligned within its yellow containing block and its width should be half of the containing block.

This paragraph should have a left margin of 25% the width of its parent element, which should require some extra text in order to test effectively.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec63.htm b/css1/sec63.htm new file mode 100755 index 0000000..03af247 --- /dev/null +++ b/css1/sec63.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 6.3 Color Units

CSS1 Test Suite: 6.3 Color Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {color: black;}
.one {color: #080;}
.two {color: #008000;}
.three {color: rgb(0,128,0);}
.four {color: rgb(0%,50%,0%);}
.five {color: rgb(0.0%,50.0%,0.0%);}
.six {color: green;}
.seven {color: invalidValue;}
.eight {color: rgb(0,128,1280);}
.nine {color: rgb(0,128,255);}
.ten {color: rgb(50%,-500%,60%);}
.eleven {color: rgb(50%,0%,60%);}

This sentence should be black.

This sentence should be green, although slightly different from those that follow.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be black, because the value given for class .seven is invalid.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be black.

This sentence should be a slightly different green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

TABLE Testing Section
 

This sentence should be black.

This sentence should be green, although slightly different from those that follow.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be black, because the value given for class .seven is invalid.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be black.

This sentence should be a slightly different green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec64.htm b/css1/sec64.htm new file mode 100755 index 0000000..b5e3431 --- /dev/null +++ b/css1/sec64.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 6.4 URLs

CSS1 Test Suite: 6.4 URLs


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" media="screen" href="folder/sec64.css">
@import url(folder/sec642.css);
BODY {background: url(bg.gif);}


This page should have a green grid pattern as its background.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

TABLE Testing Section
 

This page should have a green grid pattern as its background.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec70.htm b/css1/sec70.htm new file mode 100755 index 0000000..f501746 --- /dev/null +++ b/css1/sec70.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 7.0 CSS1 Conformance

CSS1 Test Suite: 7.0 CSS1 Conformance


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/sec71.htm b/css1/sec71.htm new file mode 100755 index 0000000..b121531 --- /dev/null +++ b/css1/sec71.htm @@ -0,0 +1 @@ + CSS1 Test Suite: 7.1 Forward-Compatible Parsing

CSS1 Test Suite: 7.1 Forward-Compatible Parsing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {color: green; rotation: 70deg;}
P.oneb {color: green;}
P.oneb {color: invalidValue;}
P.two {background-color: inherit;}
H1 + P.three {color: blue;}
P.four + H1 {color: red;}
P.five {background-color: "red";}
P.sixa {border-width: medium; border-style: solid;}
P.sixb {border-width: funny; border-style: solid;}
P.sixc {border-width: 50zu; border-style: solid;}
P.sixd {border-width: px; border-style: solid;}
@three-dee {
 @background-lighting {
  azimuth: 30deg;
  elevation: 190deg;
  }
 P.seven { color: red }
 }
P.eight {COLOR: GREEN;}
OL:wait {color: maroon;}
P.ten:first-child {color: maroon;}
UL:lang(fr) {color: gray;}
BLOCKQUOTE[href] {color: navy;}
ACRONYM[href="foo"] {color: purple;}
ADDRESS[href~="foo"] {color: purple;}
SPAN[lang|="fr"] {color: #c37;}
@media tty {
 H1 {color: red;}
 P.sixteen {color: red;}
 }
@three-dee {
 P.seventeen {color: red }
 }
P.eighteena {text-decoration: underline overline line-through diagonal;
            font: bold highlighted 100% sans-serif;}
P.eighteenb {text-decoration: underline overline line-through diagonal;
            font: bold highlighted 100% serif;}
EM, P.nineteena ! EM, STRONG {font-size: 200%; }

// UL.nineteenb,
P.nineteenb {color: red;}

P.twentya {rotation-code: "}"; color: blue;} 
P.twentyb {rotation-code: "\"}\""; color: green;}
P.twentyonea {rotation-code: '}'; color: purple;} 
P.twentyoneb {rotation-code: '\'}\''; color: green;}
P.twentytwo {
 type-display: @threedee {rotation-code: '}';};
 color: green;
 }
P.twentythree {text-indent: 0.5in;}
 color: maroon
P.twentyfour {color: red;}


This paragraph should be green, because only the rotation should be ignored.

This paragraph should be green, since error-checking should be done before calculating specificity.

In CSS1-only conforming agents, this paragraph should not have a solid gray background because, in CSS1, inherit is an invalid keyword. If the agent supports CSS2, then a gray background (not a grid) will be inherited in the first half of the document. In the second half (the table-testing section), the element will inherit a transparent background, thus allowing the grid to shine through.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should have a white background, since keywords cannot be quoted.

This paragraph should have a medium-width border around it (the same as the next three paragraphs). This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous and the next two paragraphs), because the border-width is invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the next and the previous two paragraphs), because the border-width units are invalid, and therefore the border-width should be ignored. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous three paragraphs), because the border-width does not have any value to go with its pixel unit, and is therefore invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

This paragraph should be green. CSS is case-insensitive, unless required to be case sensitive due to interaction with other standards (e.g., font names or URLs.)

  1. This ordered list item should be black, because the declaration has an invalid pseudo-class selector.

This paragraph should be black, because, in CSS1, :first-child is an invalid pseudo-class, and in CSS2, this paragraph is not the first child.

This blockquote should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This acronym should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This address should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This span should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule. However, it is valid in CSS2, so if this is being viewed on a tty browser that supports CSS2, it should be red.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the next paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the previous paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal size because the selector is invalid. The emphasized text and the strong text within it should also be normal size, since the entire ruleset should be skipped (since in some future version of CSS, there could be an operator within the selector that has higher precedence than a comma).

This paragraph should be black, because the line before the declaration is not a comment and therefore the selector for P.nineteenb is invalid.

This paragraph should be blue, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be purple, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be indented half an inch, but it should not be maroon. It should be black.

This paragraph should be black, because the color declaration after the previous ruleset should be considered part of the selector for this ruleset, and this ruleset therefore has an invalid selector and should not be applied.

TABLE Testing Section
 

This paragraph should be green, because only the rotation should be ignored.

This paragraph should be green, since error-checking should be done before calculating specificity.

In CSS1-only conforming agents, this paragraph should not have a solid gray background because, in CSS1, inherit is an invalid keyword. If the agent supports CSS2, then a gray background (not a grid) will be inherited in the first half of the document. In the second half (the table-testing section), the element will inherit a transparent background, thus allowing the grid to shine through.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should have a white background, since keywords cannot be quoted.

This paragraph should have a medium-width border around it (the same as the next three paragraphs). This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous and the next two paragraphs), because the border-width is invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the next and the previous two paragraphs), because the border-width units are invalid, and therefore the border-width should be ignored. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous three paragraphs), because the border-width does not have any value to go with its pixel unit, and is therefore invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

This paragraph should be green. CSS is case-insensitive, unless required to be case sensitive due to interaction with other standards (e.g., font names or URLs.)

  1. This ordered list item should be black, because the declaration has an invalid pseudo-class selector.

This paragraph should be black, because, in CSS1, :first-child is an invalid pseudo-class, and in CSS2, this paragraph is not the first child.

  • This unordered list item should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.
This blockquote should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This acronym should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This address should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This span should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule. However, it is valid in CSS2, so if this is being viewed on a tty browser that supports CSS2, it should be red.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the next paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the previous paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal size because the selector is invalid. The emphasized text and the strong text within it should also be normal size, since the entire ruleset should be skipped (since in some future version of CSS, there could be an operator within the selector that has higher precedence than a comma).

This paragraph should be black, because the line before the declaration is not a comment and therefore the selector for P.nineteenb is invalid.

This paragraph should be blue, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be purple, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be indented half an inch, but it should not be maroon. It should be black.

This paragraph should be black, because the color declaration after the previous ruleset should be considered part of the selector for this ruleset, and this ruleset therefore has an invalid selector and should not be applied.


[Previous] [Next] [Section] [Contents] [Specification]
\ No newline at end of file diff --git a/css1/slice b/css1/slice new file mode 100755 index 0000000..48d3c58 --- /dev/null +++ b/css1/slice @@ -0,0 +1,2 @@ +rm *.htm +./slicer.pl < w3c-suite diff --git a/css1/slicer.pl b/css1/slicer.pl new file mode 100755 index 0000000..e7e61f2 --- /dev/null +++ b/css1/slicer.pl @@ -0,0 +1,15 @@ +#! /usr/bin/perl + +@file = <>; +while (@file) { + $line = shift @file; + $line =~ s/\t//g; + $line =~ s/\cK/\n/g; + if ($line =~ s/^##### (\S+) #####//) { + open OUTFILE, ">$1"; + print OUTFILE $line; + close OUTFILE; + } else { + print STDERR "Unknown line in file: $line\n"; + } +} diff --git a/css1/slice~ b/css1/slice~ new file mode 100755 index 0000000..0d107bc --- /dev/null +++ b/css1/slice~ @@ -0,0 +1 @@ +rm *.htm ./slicer.pl < w3-suite \ No newline at end of file diff --git a/css1/static.css b/css1/static.css new file mode 100644 index 0000000..37f9388 --- /dev/null +++ b/css1/static.css @@ -0,0 +1 @@ +BODY {color: black; background: #CCCCCC;} A:link {color: blue;} A:visited {color: #006600;} \ No newline at end of file diff --git a/css1/styleimport.css b/css1/styleimport.css new file mode 100644 index 0000000..21f48a5 --- /dev/null +++ b/css1/styleimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .styleimport { font-weight: bold; color: green; background: silver none; } .folderstyleimport { color: red; background: yellow none; } \ No newline at end of file diff --git a/css1/tsack.html b/css1/tsack.html new file mode 100644 index 0000000..996799b --- /dev/null +++ b/css1/tsack.html @@ -0,0 +1 @@ + CSS1 Test Suite: Acknowledgments

W3C CSS1 Test Suite

Acknowledgments

Through a combination of common interest and serendipity, three people became the driving forces behind the creation of the CSS1 Test Suite:

The CSS1 Test Suite was first opened for public comment in late April 1998, being housed on CWRU's Web server at that time. In early May 1998, the Suite was moved over to the W3C Web server and announced to the general public in a press release by the W3C. After a few months of revisions and corrections, the CSS1 Test Suite was declared completed in conjunction with the release of the revised CSS1 specification on 17 December 1998.

In addition to the three people mentioned above, the following people made various contributions to the project:

Without the help of these individuals, and all those who took time to send us their comments, suggestions, and concerns, the Test Suite would be far less than it is today. Our deepest thanks go to them all.


[Contents]

\ No newline at end of file diff --git a/css1/tserr.html b/css1/tserr.html new file mode 100644 index 0000000..36a8510 --- /dev/null +++ b/css1/tserr.html @@ -0,0 +1 @@ + CSS1 Test Suite: Errata

W3C CSS1 Test Suite

Errata

There are currently no errata to document.

You may, however, look over the Version History from the public revision phase of the project. All changes made during that period are documented there.


[Contents]

\ No newline at end of file diff --git a/css1/tsref.html b/css1/tsref.html new file mode 100644 index 0000000..0f71dfd --- /dev/null +++ b/css1/tsref.html @@ -0,0 +1 @@ + CSS1 Test Suite: Related Resources

W3C CSS1 Test Suite

Related Resources

Historical W3C CSS tests
A hodgepodge of tests and examples, some of which made their way into the official Test Suite.
NIST CSS test pages
Neither for the faint of heart nor the impatient of mind, these tests are nonetheless an amazing resource.
CSS Pointers Group
A good collection of links to tips, tricks, tutorials, and other resources, all managed by CSS mavens Sue Sims and Jan Roland Eriksson.
comp.infosystems.www.authoring.stylesheets
The primary newsgroup for stylesheet authors. If the residents here don't know the answer, you've probably found something new. Note: in order for this link to work, you'll need a newsreader with access to a server that carries the group.

[Contents]

\ No newline at end of file diff --git a/css1/vblank.gif b/css1/vblank.gif new file mode 100755 index 0000000..332034b Binary files /dev/null and b/css1/vblank.gif differ diff --git a/css1/vhistory.html b/css1/vhistory.html new file mode 100644 index 0000000..28c7ea4 --- /dev/null +++ b/css1/vhistory.html @@ -0,0 +1 @@ + Version History

W3C CSS1 Test Suite

Version History

Versions are listed most to least recent, with the details of what was changed since the previous version of the Test Suite, a link to each changed page, and a link to the main page of each version. Note that, as time goes on, corrections made in earlier versions may be superseded or removed in later revisions.

19990126 (26 January 1999)
ENTIER SUITE Major additions, clarifications, rearrangements, and other changes in preparation for making the Suite official. This includes the addition of the Prologue, the separation of Box Model tests into separate pages for block-level and inline elements, tests covering more of section 2, section 4, and section 7.1 of the specification, and a host of corrections and other alterations to the tests and text throughout the Test Suite. These changes are, unfortunately, too numerous to document here. If you used the Test Suite before this revision, it is best to treat the new version as though everything changed, and re-run your tests accordingly.
19981002 (02 October 1998)
5.3.4 background-repeat Changed the image being tiled in the background of each test element, in order to make it easier to see just what's going on.
5.3.6 background-position Changed the image being tiled in the background of each test element, as in section 5.3.4.
5.4.4 vertical-align Altered tests .four through .nine to be more accurate, and added a generic rule for paragraph elements to support this change.
5.5.25c float Corrected the last two tests, which were previously in error.
5.5.25d float An entirely new test page, devoted to further testing of the behavior of floating text elements.
5.5.26b float An entirely new test page, devoted to further testing of clear (in this case, multiple floating test elements are used).
6.3 Color Units Fixed a syntax error in .five which had made the entire rule invalid.
19980901 (01 September 1998)
ALL TESTS Changed the page background for test pages to a light-gray grid on white; this change came as a result of user requests for a less intrusive background.
5.4.1 word-spacing Minor changes in wording of most tests.
5.4.2 letter-spacing Minor changes in wording of most tests.
5.4.7 text-indent Added a light blue background color to the test elements and reworded a couple of tests.
5.4.8 line-height Added the declaration font-size: 14px to all tests, in an attempt to ensure that the tested values of line-height are visible.
5.5.01 margin-top Added a light blue background color to all test elements.
5.5.02 margin-right Added a light blue background color to all test elements; added the declaration text-align: right to the test elements, in order to make the test easier to follow.
5.5.03 margin-bottom Added a light blue background color to all test elements.
5.5.04 margin-left Added a light blue background color to all test elements.
5.5.05 margin Added a light blue background color to all test elements.
5.5.06 padding-top Minor rewording of some tests.
5.5.07 padding-right Added the declaration text-align: right to the test elements, in order to make the test easier to follow.
5.5.08 padding-bottom Minor rewording of some tests.
5.5.10 padding Minor rewording of some tests.
5.5.22 border Corrected a hyperlink within the document to point to the correct target. Note that this incorrect URL did NOT affect the tests in previous versions of the Test Suite.
5.5.25 float Moved some tests to test page 5.5.25c, detailed below.
5.5.25c float An entirely new test page, devoted to testing the behavior of floating text elements.
6.1 Length Units Added a 'reference paragraph' with a left margin set to zero, for comparison against the other test statements.
6.2 Percentage Units Added a significant set of new test statements proposed by Håkon Lie, and clarified the wording of the test which had been there before.
6.3 Color Units Changed the color assigned to BODY to be black, and added tests to see what happens when an invalid or out-of-range value is specified: in .seven, a random string of letters is used, and in .eight through .eleven, out-of-bounds value clipping is tested.
19980715 (15 July 1998)
5.2.7 font Changed the wording relating to line heights to be more accurate, correctly describing it as being related to the font size; also added a new test which uses a pixel value for the font size.
5.5.06 - 5.5.10 padding-top, padding-right, padding-bottom, padding-left, padding In all cases, changed the non-standard color cyan to aqua.
5.5.22 border Changed the non-standard color brown to maroon; added a test for images which are also anchors, and the suppression of the border with border: 0px.
5.5.23 width Added a test of width as applied to a paragraph; added a rule which will set the table to be half the width of the viewing window.
5.4.8 line-height Corrected wording to be more accurate, as for the corrections to 5.2.7 above.
5.5.26 clear Corrected test four (clear: none) so that it actually tested for the desired behavior.
5.6.1 display Changed some wording to make the tests more clear, and also added a marker type to the test for list-item.
19980615 (15 June 1998)
1.1 Containment in HTML Placed the first two @import statements at the beginning of the inline stylesheet, and added another @import statement at the end of the stylesheet to test for browser compliance with section 3.0 of the specification.
1.3 Inheritance Fixed the declarations to include an omitted BODY rule, the lack of which was making some of the statements invalid; also changed color values of dark green to more obvious colors, based on user feedback that the specific dark green in use was too difficult to distinguish from black.
1.4 Class as Selector Changed color values of dark green to more obvious colors, as per the explanation for section 1.3.
1.5 ID as Selector Removed a test for handling of duplicate IDs as being beyond the scope of CSS1.
5.4.3 text-decoration Changed the invalid declaration {text-decoration: normal;} to use the correct value {text-decoration: none;}.
5.4.4 vertical-align Refined tests to make desired behavior (or a lack thereof) easier to see.
5.4.8 line-height Added a contextual selector TABLE .ten {line-height: normal;} to test handling of line-height within tables.
5.6.1 display Added color: red; to the class .four {display: none;}, making it easier to tell if the property value none is being interpreted correctly.
6.3 Color units Changed the declared values for color in classes .one through .four to match (or at least approximate) the defined color values for the keyword green found in the class .six; also added a test for real-number percentage values.
19980511 (11 May 1998)
Intial release.

[Contents]

\ No newline at end of file diff --git a/css1/w3c-suite b/css1/w3c-suite new file mode 100755 index 0000000..d454c58 --- /dev/null +++ b/css1/w3c-suite @@ -0,0 +1,122 @@ +##### sec00.htm ##### CSS1 Test Suite: Prologue

CSS1 Test Suite: Prologue


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec01.htm ##### CSS1 Test Suite: Configuring Your System

CSS1 Test Suite: Configuring Your System


[Previous] [Next] [Section] [Contents] [Specification]

In the first place, you will need to make sure that your browser is configured to pay attention to style sheets at all. This is typically done by finding an entry in your preferences dialog which says something like "Enable style sheets" and making sure the appropriate box is checked. You may have to enable other features as well. Please read the article Enabling Your Style Sheets if you need further information.

You will also need to be using a browser which is able to load LINKed style sheets. Every test page in the suite uses the style sheet base.css. This provides a consistent look to the pages, and so when something overrides the base style sheet, you'll know it. If the current page has a white background with a light gray grid, then the base stylesheet has been imported via the LINK element. If not, you should double-check to make sure that you do not have a user stylesheet set (see next section).

Disabling User-Defined Style Sheets

Furthermore, you will need to make sure that you are not using a user-defined style sheet. If you have set up your own style sheet and have your browser configured to use it, then you will need to disable this feature before you start.

Under Internet Explorer 4.x for Windows, you should take the following steps:

  1. Select "Internet Options..." under the "View" menu.
  2. Select the "Accessibility..." button near the bottom of the Internet Options dialog.
  3. Check to make sure that, under "User Style Sheet," the checkbox is not checked. There may be a file listed under it, although you're probably safer if there isn't.

As of this writing, user-defined stylesheets are not supported by any other popular browser.

Units and Monitor Settings

Some of the CSS1 Test Suite's test pages use "real-world" lengths; that is, they are units such as inches or centimeters. However, your computer may or may not have the slightest idea how far a "centimeter" really is, in terms of the number of pixels. On Windows95/98, using some display drivers, it is possible to find out by taking the following steps:

  1. Open your Display Settings.
  2. Select the "Settings" tab.
  3. Select the "Advanced" button near the bottom.
  4. Select the "Fonts" tab.
  5. You should now see a ruler.
  6. Hold a (physical) ruler up to the screen, and click and drag the screen ruler to resize it until it matches the physical one.
  7. Click "OK".

Under WindowsNT and the MacOS, the system should have already determined real-world distances for your particular monitor and its settings. It is assumed that the user agent will take advantage of this, although it's always a good idea to check for yourself, using an actual ruler.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec02.htm ##### CSS1 Test Suite: Understanding the Test Pages

CSS1 Test Suite: Understanding the Test Pages


[Previous] [Next] [Section] [Contents] [Specification]

Each page has a number of test statements, each of which describes a given effect which should be seen. If the effects you see do not match the description given, then there is a problem with your browser's CSS support. The test statements on each page are duplicated inside a one-cell table. This was done to provide at least rudimentary testing of conformance within tables, which are know to be a weak point in many CSS implementations.

Above the test statements, the style declarations for that specific page are displayed. There are also navigation links at the top and bottom of the page. The top of the page will look something like this:

CSS1 Test Suite: 5.2.4 font-variant


[Next] [Previous] [Section] [Contents] [Reference Image] [Specification]

The first line is not only the page's title, but also includes the name of the property being tested on that page, and its section number in the CSS1 specification. The six links under the title are, respectively:

Finally, it is assumed that visual user agents are being tested against this test suite, and the test statements are written with this assumption in mind. There are currently no provisions given for text-only agents, although these should still be testable, or for speaking browsers, which are beyond the scope of CSS1 in any case.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec03.htm ##### CSS1 Test Suite: CSS1 vs. CSS2

CSS1 Test Suite: CSS1 vs. CSS2


[Previous] [Next] [Section] [Contents] [Specification]

This page is intended to give some idea of how much support your user agent has for both CSS1 and CSS2. These are not intended to be normative tests, but instead indicators of what to expect further on in the test, and where potential confusion may arise. Note that just because a user agent passes the following tests, it cannot be assumed to have full support for either CSS1 or CSS2.

Following are some CSS1 tests:

If your user agent did not display the above list as described, or seemed to have trouble with some of the display, then it does not have complete CSS1 support. (Even if it did render the list correctly, it may not have complete CSS1 support.)

Following are some CSS2 tests:

If your user agent did not display the above list as described, or seemed to have trouble with some of the display, then it does not have complete CSS2 support. (Even if it did render the list correctly, it may not have complete CSS2 support.)


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec04.htm ##### CSS1 Test Suite: LINK and @import

CSS1 Test Suite: LINK and @import


[Previous] [Next] [Section] [Contents] [Specification]

The style declaration applied in each following case is: {font-weight: bold; color: green; background: silver none;}.

1. Inline style (style attribute).

3. Linked stylesheet with media attribute set to all.

4. Linked stylesheet with media attribute set to screen.

5. Linked stylesheet with media attribute set to screen, projection.

6. Stylesheet imported by linked stylesheet.

7. Embedded stylesheet (style element).

8. Stylesheet imported by embedded stylesheet.

10. Linked stylesheet in another folder with media attribute set to all.

11. Linked stylesheet in another folder with media attribute set to screen.

12. Linked stylesheet in another folder with media attribute set to screen, projection.

13. Stylesheet in another folder imported by linked stylesheet in that same other folder.

14. Stylesheet in another folder imported by embedded stylesheet.

16. Stylesheet imported by last linked stylesheet.

17. Stylesheet in another folder imported by last linked stylesheet.

18. Stylesheet in another folder imported by stylesheet in that same folder imported by last linked stylesheet in this folder.

NOTE: The following should be red only if the browser is displaying the results on a tty. Normally, these should be uncoloured (not green). Note, though, that results for numbers 19 and 20 are irrelevant if any of the tests 1 to 18 are either uncolored or red.

19. Linked stylesheet with media attribute set to tty.

20. Linked stylesheet in another folder with media attribute set to tty.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec10.htm ##### CSS1 Test Suite: 1.0 Basic Concepts

CSS1 Test Suite: 1.0 Basic Concepts


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec11.htm ##### CSS1 Test Suite: 1.1 Containment in HTML

CSS1 Test Suite: 1.1 Containment in HTML


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" href="linktest.css" title="Default SS"><LINK rel="alternate stylesheet" type="text/css" href="linktest2.css" title="Alternate SS">@import url(imptest1.css);@import "imptest1a.css";UL {color: red;}.four {color: purple;}@import url(imptest2.css);<!--P.six {color: green;}-->

This sentence should be underlined due to the linked style sheet linktest.css, the reference to which is shown above.

This sentence should NOT be underlined due to the linked style sheet linktest2.css, unless the external style sheet "Alternate SS" has been selected via the user agent.

This sentence should be purple, and it doesn't have a terminating paragraph tag.

  1. This list should NOT be purple.
  2. It should, instead, be black.
  3. If it IS purple, then the browser hasn't correctly parsed the preceding paragraph.

This sentence should be black. If it is red, then the browser has inappropriately imported the styles from the file imptest2.css (see section 3.0 of the CSS1 specification for more details).

This paragraph should be green.

TABLE Testing Section
 

This sentence should be underlined due to the linked style sheet linktest.css, the reference to which is shown above.

This sentence should NOT be underlined due to the linked style sheet linktest2.css, unless the external style sheet "Alternate SS" has been selected via the user agent.

  • This sentence should be green due to an imported style sheet [@import url(imptest1.css);].
  • This sentence should be purple due to an imported style sheet [@import "imptest1a.css"].
  • This sentence should be green thanks to the STYLE attribute [STYLE="color: green;"].

This sentence should be purple, and it doesn't have a terminating paragraph tag.

  1. This list should NOT be purple.
  2. It should, instead, be black.
  3. If it IS purple, then the browser hasn't correctly parsed the preceding paragraph.

This sentence should be black. If it is red, then the browser has inappropriately imported the styles from the file imptest2.css (see section 3.0 of the CSS1 specification for more details).

This paragraph should be green.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec12.htm ##### CSS1 Test Suite: 1.2 Grouping

CSS1 Test Suite: 1.2 Grouping


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one, .two, .three {color: green;}

This sentence should be green.

This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec13.htm ##### CSS1 Test Suite: 1.3 Inheritance

CSS1 Test Suite: 1.3 Inheritance


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {color: green;}H3 {color: blue;}EM {color: purple;}.one {font-style: italic;}.two {text-decoration: underline;}#two {color: navy;}.three {color: purple;}

This sentence should show blue and purple.

This sentence should be blue throughout.

This should be green except for the emphasized words, which should be purple.

This should be blue and underlined.

This sentence should be underlined, including this part, this part, this part, and this part.

This sentence should also be underlined, as well as dark blue (navy), including this part.

This sentence should be purple, including this part and this part (which is spanned).

TABLE Testing Section
 

This sentence should show blue and purple.

This sentence should be blue throughout.

This should be green except for the emphasized words, which should be purple.

This should be blue and underlined.

This sentence should be underlined, including this part, this part, this part, and this part.

This sentence should also be underlined, as well as dark blue (navy), including this part.

This sentence should be purple, including this part and this part (which is spanned).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec14.htm ##### CSS1 Test Suite: 1.4 Class as selector

CSS1 Test Suite: 1.4 Class as selector


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {color: green;}.a1 {color: green;}P.two {color: purple;}

This sentence should be green.

This sentence should be green.

This sentence should be purple.

This sentence should NOT be purple.
TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This sentence should be purple.

This sentence should NOT be purple.
  • This sentence should NOT be purple.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec15.htm ##### CSS1 Test Suite: 1.5 ID as selector

CSS1 Test Suite: 1.5 ID as selector


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

#one {color: green;}#a1 {color: green;}P#two {color: blue;}P#three {color: purple;}

This sentence should be green.

This sentence should be green.

This paragraph should be blue [ID="two"].

This sentence should NOT be blue [PRE ID="two"].
This sentence should be black [PRE ID="three"].
TABLE Testing Section
 

This sentence should be green.

This sentence should be green.

This paragraph should be blue [ID="two"].

This sentence should NOT be blue [PRE ID="two"].
This sentence should be black [PRE ID="three"].
  • This sentence should NOT be blue.
  • This sentence should NOT be purple.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec16.htm ##### CSS1 Test Suite: 1.6 Contextual selectors

CSS1 Test Suite: 1.6 Contextual selectors


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {color: navy; font-family: serif;}HTML BODY TABLE P {color: purple; font-family: sans-serif;}EM, UL LI LI {color: green;}

This sentence should be navy serif in the first half of the page, but purple and sans-serif in the table.

This sentence should be normal for its section, except for the last word, which should be green.

TABLE Testing Section
 

This sentence should be navy serif in the first half of the page, but purple and sans-serif in the table.

This sentence should be normal for its section, except for the last word, which should be green.

  • Hello. The first "hello" should be green, but this part should be black.
    • This should be green.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec17.htm ##### CSS1 Test Suite: 1.7 Comments

CSS1 Test Suite: 1.7 Comments


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

/* This is a CSS1 comment. */.one {color: green;} /* Another comment *//* The following should not be used:.two {color: red;} */.three {color: green; /* color: red; */}/**.four {color: red;} */.five {color: green;}/**/.six {color: green;}/*********/.seven {color: green;}/* a comment **/.eight {color: green;}

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be black.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec20.htm ##### CSS1 Test Suite: 2.0 Pseudo-Classes and Pseudo-Elements

CSS1 Test Suite: 2.0 Pseudo-Classes and Pseudo-Elements


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec21.htm ##### CSS1 Test Suite: 2.1 anchor

CSS1 Test Suite: 2.1 anchor


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

A {color: green;}A:link {color: purple;}A:visited {color: lime;}A:active {color: maroon;}#one {color: #006600;}

The following anchors should appear as described; none of them should be red.

The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A element are applied to them under CSS1. It also should NOT turn maroon when clicked upon.

TABLE Testing Section
 

The following anchors should appear as described; none of them should be red.

The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A element are applied to them under CSS1. It also should NOT turn maroon when clicked upon.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec23.htm ##### CSS1 Test Suite: 2.3 first-line

CSS1 Test Suite: 2.3 first-line


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {color: green;}.two:first-line {font-size: 200%;}.three:first-line {font-variant: small-caps;}

The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line.

TABLE Testing Section
 

The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec24.htm ##### CSS1 Test Suite: 2.4 first-letter

CSS1 Test Suite: 2.4 first-letter


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-letter {color: maroon;}.two:first-letter {font-size: 200%;}P.three:first-letter {font-size: 350%;}

The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 3.5 times bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended.

TABLE Testing Section
 

The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 3.5 times bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec25.htm ##### CSS1 Test Suite: 2.5 Pseudo-elements in Selectors

CSS1 Test Suite: 2.5 Pseudo-elements in Selectors


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {font-weight: bold;}P.two:first-line {color: green;}P:first-line.three {color: red;}

The first line of this paragraph, and only that line, should be boldfaced. This test is included simply to establish a baseline for the following tests, since if this test fails, then the rest of the tests on this page are expected to fail as well.

The first line of this paragraph, and only that line, should be boldfaced and green, thanks to its selector. If this is not the case, then the user agent may have failed to properly parse the selector, or it may simply not support the :first-line pseudo-element.

The first line of this paragraph, and only that line, should be boldfaced. If it is red, then the user agent has violated the specification in allowing pseudo-elements at a point other than the end of a selector. If neither is the case, then the user agent has correctly ignored the incorrect selector, but has suppressed other styles which are valid, and therefore must be considered to have failed the test.

TABLE Testing Section
 

The first line of this paragraph, and only that line, should be boldfaced. This test is included simply to establish a baseline for the following tests, since if this test fails, then the rest of the tests on this page are expected to fail as well.

The first line of this paragraph, and only that line, should be boldfaced and green, thanks to its selector. If this is not the case, then the user agent may have failed to properly parse the selector, or it may simply not support the :first-line pseudo-element.

The first line of this paragraph, and only that line, should be boldfaced. If it is red, then the user agent has violated the specification in allowing pseudo-elements at a point other than the end of a selector. If neither is the case, then the user agent has correctly ignored the incorrect selector, but has suppressed other styles which are valid, and therefore must be considered to have failed the test.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec26.htm ##### CSS1 Test Suite: 2.6 Multiple Pseudo-Elements

CSS1 Test Suite: 2.6 Multiple Pseudo-Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P:first-line {color: green;}P:first-letter {color: maroon;}.two:first-line {font-size: 200%;}.two:first-letter {font-size: 350%;}P.three:first-letter {font-size: 350%;}P.three:first-line {font-variant: small-caps;}

The first letter of this paragraph, and only that one, should be maroon (dark red), while the entire first line should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be 350% bigger than the rest of the first line of this paragraph and maroon (dark red), while the entire first line should be 200% bigger than normal and green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon (dark red). Note that the inclusion of both the quotation mark and the 'W' in the first-letter style is not required under CSS1, but it is recommended. In addition, the entire first line should be in a small-caps font and green.

TABLE Testing Section
 

The first letter of this paragraph, and only that one, should be maroon (dark red), while the entire first line should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be 350% bigger than the rest of the first line of this paragraph and maroon (dark red), while the entire first line should be 200% bigger than normal and green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon (dark red). Note that the inclusion of both the quotation mark and the 'W' in the first-letter style is not required under CSS1, but it is recommended. In addition, the entire first line should be in a small-caps font and green.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec30.htm ##### CSS1 Test Suite: 3.0 The Cascade

CSS1 Test Suite: 3.0 The Cascade


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec31.htm ##### CSS1 Test Suite: 3.1 important

CSS1 Test Suite: 3.1 important


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {color: green ! important;}P {color: red;}P#id1 {color: purple;}

This paragraph should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet.

This paragraph should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than delcarations which use ID selectors.

This paragraph should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.

TABLE Testing Section
 

This paragraph should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet.

This paragraph should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than delcarations which use ID selectors.

This paragraph should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec32.htm ##### CSS1 Test Suite: 3.2 Cascading Order

CSS1 Test Suite: 3.2 Cascading Order


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" HREF="linktest.css">LI {color: purple;}UL LI {color: blue;}UL LI LI {color: gray;}LI.red {color: green;}UL LI.mar {color: #660000;}UL LI#gre {color: green;}.test {color: blue;}.test {color: purple;}.one {text-decoration: line-through;}

This sentence should be blue (STYLE attr.).

This sentence should be purple [class="test"].

This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported).

TABLE Testing Section
 
  • This list item should be blue...
  • ...and so should this; neither should be purple.
    • This list item should be gray...
    • ...as should this....
    • ...but this one should be green.
  • This ought to be dark red...
  • ...this green...
  • ...and this blue.

This sentence should be blue (STYLE attr.).

This sentence should be purple [class="test"].

This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec40.htm ##### CSS1 Test Suite: 4.0 Formatting Model

CSS1 Test Suite: 4.0 Formatting Model


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec411.htm ##### CSS1 Test Suite: 4.1.1 Vertical Formatting

CSS1 Test Suite: 4.1.1 Vertical Formatting


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {margin-bottom: 2cm; padding-bottom: 0;}P.two {margin-top: 2cm; padding-top: 0;}P.three {margin-top: 0; padding-top: 0;}P.four {margin-top: -1cm; margin-bottom: 0;        padding-top: 0; padding-bottom: 0;}DIV.five {margin-top: 1cm; margin-bottom: 1cm;          padding-top: 1cm; padding-bottom: 0;}P.six {margin-top: 1cm; margin-bottom: 1cm;       padding-top: 0; padding-bottom: 0;}P.seven {margin-top: 1cm; padding-top: 0;}P.eight {margin-bottom: -1cm; padding-bottom: 2cm;}P.nine {margin-top: -1cm; padding-top: 1cm;        padding-bottom: 0; margin-bottom: 1cm;}P.ten {margin-top: 1cm;padding-top: 0;       float: left;width: 50%;}P.eleven {margin-top: 1cm; padding-top: 0; clear: none;}P.twelve {margin-bottom: 0; padding-bottom: 1cm; clear: both;}P.thirteen {margin-top: 0; padding-top: 1cm;}TABLE {clear: both;}

There should be a two-centimeter margin between this paragraph and the next, because adjacent vertical margins should collapse to the maximum of the margins.

This is another paragraph.

There should be a two-centimeter margin between this paragraph and the next.

This is another paragraph.

There should be a one-centimeter margin between this paragraph and the next, because when there is one negative margin, the two margins should be added (the minus sign should be kept).

This is another paragraph.

There should be three centimeters between this text and the text above, but only one centimeter between this text and the text below, because vertical margins of nested elements should collapse only if there is no border or padding between the margins.

This is more text.

There should be two centimeters between this paragraph and the one below, because negative margins collapse to a negative margin with the largest absolute value of the margins collapsed.

This is a paragraph, which I should make very long so that you can easily see how much space there is between it and the one below it and to the right.

There should be two centimeters between this paragraph and the one above it, since margins do not collapse on floating elements.

There should be one centimeter between this paragraph and the (non-floating) one above it, since the float should not effect the paragraph spacing.

There should be two centimeters of padding between this paragraph and the one below. Padding does not collapse, and there is 1cm of padding on each side.

This is the next paragraph.

TABLE Testing Section
 

There should be a two-centimeter margin between this paragraph and the next, because adjacent vertical margins should collapse to the maximum of the margins.

This is another paragraph.

There should be a two-centimeter margin between this paragraph and the next.

This is another paragraph.

There should be a one-centimeter margin between this paragraph and the next, because when there is one negative margin, the two margins should be added (the minus sign should be kept).

This is another paragraph.

There should be three centimeters between this text and the text above, but only one centimeter between this text and the text below, because vertical margins of nested elements should collapse only if there is no border or padding between the margins.

This is more text.

There should be two centimeters between this paragraph and the one below, because negative margins collapse to a negative margin with the largest absolute value of the margins collapsed.

This is a paragraph, which I should make very long so that you can easily see how much space there is between it and the one below it and to the right.

There should be two centimeters between this paragraph and the one above it, since margins do not collapse on floating elements.

There should be one centimeter between this paragraph and the (non-floating) one above it, since the float should not effect the paragraph spacing.

There should be two centimeters of padding between this paragraph and the one below. Padding does not collapse, and there is 1cm of padding on each side.

This is the next paragraph.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec412.htm ##### CSS1 Test Suite: 4.1.2 Horizontal Formatting

CSS1 Test Suite: 4.1.2 Horizontal Formatting


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.ruler {padding: 0px; margin: 0px; border-width: 0px;}P#ruled {background-color: aqua; width: 400px;     border-style: solid; border-color: silver;     border-top-width: 0px; border-bottom-width: 0px;     border-left-width: 40px; border-right-width: 40px;     padding-left: 40px; padding-right: 40px;     margin-top: 0px; margin-bottom: 0px; margin-left: 40px; margin-right: 40px;}P.one {margin-left: 10px;}DIV.two {margin-left: 10px;}P.three {margin-left: 0; width: 50%; margin-right: auto;         background-color: gray;}P.four {margin-left: auto; width: 50%; margin-right: auto;        background-color: gray;}P.five {margin-left: auto; width: 50%; margin-right: 0;        background-color: gray;}P.six {margin-left: auto; width: auto; margin-right: 0;       background-color: gray; }P.seven {margin-left: 0; width: auto; margin-right: auto;         background-color: gray;}P.eight {margin-left: auto; width: auto; margin-right: auto;         background-color: gray;}P.nine {padding-left: auto; padding-right: auto; margin-left: 0; margin-right: 0;        width: 50%; background-color: gray;}P.ten {margin-left: auto; width: 100%; margin-right: auto;       background-color: gray;}

[ruler]

This text is inside a P element. The border, padding, and margins for this paragraph should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

[labels]

This paragraph should be indented ten pixels.

This paragraph should be indented twenty pixels, since horizontal margins do not collapse.

This element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified.

Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport.

Because this paragraph has width 100%, the auto margins become zero, so it should not be centered.

TABLE Testing Section
 
[ruler]

This text is inside a P element. The border, padding, and margins for this paragraph should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

[labels]

This paragraph should be indented ten pixels.

This paragraph should be indented twenty pixels, since horizontal margins do not collapse.

This element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified.

Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport.

Because this paragraph has width 100%, the auto margins become zero, so it should not be centered.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec414.htm ##### CSS1 Test Suite: 4.1.4 Floating Elements

CSS1 Test Suite: 4.1.4 Floating Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

HR.minor {clear: both; width: 5%;}HR.major {clear: both; width: 75%; margin: 1.5em;}DIV {border: 5px solid purple; padding: 0; margin: 0.125em;}P.left, P.right {width: 10em; padding: 1em; margin: 0;   border: 1px solid lime; background-color: silver;}IMG.left, IMG.right {margin: 0; border: 3px solid black;}.left {float: left;}.right {float: right;}

On this test page, each test is performed once with floating paragraphs, and then again with floating images. Other than the substitution of images for pargraphs, the structure of the test is exactly the same, including the direction of the floats.


This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV.

This is the first left-floating paragraph.

This is the second left-floating paragraph.

This is the third left-floating paragraph.

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated elements should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated images should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is a right-floating paragraph (first in source).

This is a left-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating box should not be higher than the top of the right-floating box.

This is text within the DIV. The floating images within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating image should not be higher than the top of the right-floating image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated element.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be,*

This is a left-floating paragraph (third in source).

at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. *

This is a left-floating paragraph (fourth in source).

In order to mark these points clearly, an asterisk has been inserted just before each floated element. If a line has room for a floated element, then the element should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, * at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. * In order to mark these points clearly, an asterisk has been inserted just before each floated image. If a line has room for a floated image, then the image should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is *

This is a left-floating paragraph (first in source).

*

This is a right-floating paragraph (second in source).

text within the DIV. Under CSS1, the left floating element should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. Similarly, the right floating element should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. The text of the DIV element should flow between and under the two floating elements. The two asterisk characters mark the insertion points of the floating elements. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

This is * * text within the DIV. Under CSS1, the left floating image should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. Similarly, the right floating image should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. The text of the DIV element should flow between and under the two floating image. The two asterisk characters mark the insertion points of the floating image. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

TABLE Testing Section
 

On this test page, each test is performed once with floating paragraphs, and then again with floating images. Other than the substitution of images for pargraphs, the structure of the test is exactly the same, including the direction of the floats.


This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV.

This is the first left-floating paragraph.

This is the second left-floating paragraph.

This is the third left-floating paragraph.

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other. The first two should be side by side, whereas the third should be on the next "line."

This is a left-floating paragraph (first in source).

This is a right-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated elements should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is text within the DIV. The floating images within this DIV should not go beyond the left or right inner edge of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, they should not overlap each other in any way, nor should the floated elements be overwritten by the DIV text. In addition, the floated images should not be side-by-side, but instead the first should be floated left, and the second floated to the right below the first.

This is a right-floating paragraph (first in source).

This is a left-floating paragraph (second in source).

This is text within the DIV. The floating elements within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating elements should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating box should not be higher than the top of the right-floating box.

This is text within the DIV. The floating images within this DIV should not go beyond the top side of this DIV, which means that the borders of the floating images should not overlap the top or side borders of the DIV in any way. In addition, the top of the left-floating image should not be higher than the top of the right-floating image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated element.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. In order to mark these points clearly, an asterisk has been inserted just before each floated image.

This is text within the DIV. *

This is a left-floating paragraph (first in source).

The floating elements within this DIV should not go any higher than the line-box containing the inline content which precedes them. *

This is a right-floating paragraph (second in source).

This means that the top side of each float can be,*

This is a left-floating paragraph (third in source).

at most, as high as the top edge of the inline element containing the content just before the floating elements occur in the source. *

This is a left-floating paragraph (fourth in source).

In order to mark these points clearly, an asterisk has been inserted just before each floated element. If a line has room for a floated element, then the element should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is text within the DIV. * The floating images within this DIV should not go any higher than the line-box containing the inline content which precedes them. * This means that the top side of each float can be, * at most, as high as the top edge of the inline element containing the content just before the floating images occur in the source. * In order to mark these points clearly, an asterisk has been inserted just before each floated image. If a line has room for a floated image, then the image should float so that its top is aligned with the top of the line-box in which the asterisk appears. Otherwise, its top should align with the top of the next line-box.

This is *

This is a left-floating paragraph (first in source).

*

This is a right-floating paragraph (second in source).

text within the DIV. Under CSS1, the left floating element should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. Similarly, the right floating element should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating element. The text of the DIV element should flow between and under the two floating elements. The two asterisk characters mark the insertion points of the floating elements. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.

This is * * text within the DIV. Under CSS1, the left floating image should be placed in the upper left corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. Similarly, the right floating image should be placed in the upper right corner of the DIV, and the purple border of the DIV should abut the green border of the floating image. The text of the DIV element should flow between and under the two floating image. The two asterisk characters mark the insertion points of the floating image. It is expected that, under future specifications, it may be acceptable for the top of floated elements to align with the top of the line-box following the insertion point of the floated element to avoid floating elements appearing before text which precedes it in the source document.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec42.htm ##### CSS1 Test Suite: 4.2 Inline Elements

CSS1 Test Suite: 4.2 Inline Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {line-height: 200%;}SPAN.two {border-style: solid; border-width: 10px; border-color: red;          padding: 2pt; margin: 30pt;}P.three {font-size: 10pt; line-height: 12pt;}SPAN.four {border-style: solid; border-width: 12px; border-color: red;          padding: 2pt;}

This is a paragraph that has a very long span in it, and the span has a 10px red border separated from the span by 2pt, and a margin of 30pt. The padding and border should be present on all sides of the span (although vertical lines should appear only at the beginning and the end of the whole span, not on each line). The padding, border, and margin should all be noticeable at the beginning and end of the span. However, the line height should not be changed by any of them, so the margin should be unnoticeable and the border should overlap text on other lines. The line spacing in the whole paragraph should be 200% of the font size.

This is a paragraph that has a very long span in it, and the span has a 12px red border separated from the span by 2pt of padding (the difference between the line-height and the font-size), which should overlap with the lines of text above and below the span, since the padding and border should not effect the line height. The span's border should have vertical lines only at the beginning and end of the whole span, not on each line. The line spacing in the whole paragraph should be 12pt, with font-size 10pt.

TABLE Testing Section
 

This is a paragraph that has a very long span in it, and the span has a 10px red border separated from the span by 2pt, and a margin of 30pt. The padding and border should be present on all sides of the span (although vertical lines should appear only at the beginning and the end of the whole span, not on each line). The padding, border, and margin should all be noticeable at the beginning and end of the span. However, the line height should not be changed by any of them, so the margin should be unnoticeable and the border should overlap text on other lines. The line spacing in the whole paragraph should be 200% of the font size.

This is a paragraph that has a very long span in it, and the span has a 12px red border separated from the span by 2pt of padding (the difference between the line-height and the font-size), which should overlap with the lines of text above and below the span, since the padding and border should not effect the line height. The span's border should have vertical lines only at the beginning and end of the whole span, not on each line. The line spacing in the whole paragraph should be 12pt, with font-size 10pt.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec43.htm ##### CSS1 Test Suite: 4.3 Replaced Elements

CSS1 Test Suite: 4.3 Replaced Elements


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

IMG.one {display: inline;}IMG.two {display: block;}IMG.three {display: block;           margin-right: auto; margin-left: auto; width: auto;}IMG.four {display: block;          margin-right: auto; margin-left: auto; width: 50%;}IMG.five {display: block;          margin-right: 0; margin-left: auto; width: 50%;}

[Image]The image at the beginning of this sentence should be a 15px square.

[Image]

The above image should be a 15px square with the same left edge as this text.

[Image]

The above image should be a 15px square aligned at the center.

[Image]

The above image should be a square resized so its width is 50% of the its parent element, and centered horizontally within the parent element: the document body in the first half, and the table cell in the second.

[Image]

The above image should be a square resized so its width is 50% of its parent element, and aligned at the right edge of the parent element: the document body in the first half, and the table cell in the second.

TABLE Testing Section
 

[Image]The image at the beginning of this sentence should be a 15px square.

[Image]

The above image should be a 15px square with the same left edge as this text.

[Image]

The above image should be a 15px square aligned at the center.

[Image]

The above image should be a square resized so its width is 50% of the its parent element, and centered horizontally within the parent element: the document body in the first half, and the table cell in the second.

[Image]

The above image should be a square resized so its width is 50% of its parent element, and aligned at the right edge of the parent element: the document body in the first half, and the table cell in the second.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec44.htm ##### CSS1 Test Suite: 4.4 The Height of Lines

CSS1 Test Suite: 4.4 The Height of Lines


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {font-size: 14px; line-height: 20px;}IMG.onea {vertical-align: text-bottom;     width: 200px; height: 200px;}IMG.oneb {vertical-align: text-top; width: 200px; height: 200px;}P.two {font-size: 14px; line-height: 20px;}IMG.twoa {vertical-align: text-bottom; width: 100px; height: 100px;     padding: 5px; border-style: solid;     border-width: 10px; margin: 15px;}IMG.twob {vertical-align: text-top;          width: 100px; height: 100px;     padding: 5px; border-style: solid;     border-width: 10px; margin: 15px;}IMG.twoc {vertical-align: middle; width: 50px; height: 50px;     padding: 5px; border-style: solid;     border-width: 10px; margin: -10px;}

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels, three of which are part of the line-box of each line. Any images within the paragraph should increase the height of the line-box so that they fit within the line box, such as [Image] and . This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned.

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels. Any images within the paragraph should increase the height of the line-box so that they fit, including their padding (5px), border (10px) and margins (15px) within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned. It is the outer edge of the margin that should be text-bottom and text-top aligned in this paragraph, so for the first image the bottom border of the image should begin 15px above the bottom of the text, and for the second image the top border should begin 15px below the top of the text [Image]. The last image in this paragraph has -10px margins set on it, so that should pull the text in toward the image in the vertical direction, and also in the horizontal direction.

TABLE Testing Section
 

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels, three of which are part of the line-box of each line. Any images within the paragraph should increase the height of the line-box so that they fit within the line box, such as [Image] and . This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned.

This paragraph should have a font size of 14px and a line height of 20px. This means that the lines of text within it should be separated by six pixels. Any images within the paragraph should increase the height of the line-box so that they fit, including their padding (5px), border (10px) and margins (15px) within the line box, such as [Image] and [Image]. This is additional text to make sure that there is enough room left below the image so that this line does not hit the image that is text-top aligned. It is the outer edge of the margin that should be text-bottom and text-top aligned in this paragraph, so for the first image the bottom border of the image should begin 15px above the bottom of the text, and for the second image the top border should begin 15px below the top of the text [Image]. The last image in this paragraph has -10px margins set on it, so that should pull the text in toward the image in the vertical direction, and also in the horizontal direction.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec45.htm ##### CSS1 Test Suite: 4.5 The Canvas

CSS1 Test Suite: 4.5 The Canvas


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

HTML {background-color: aqua;}BODY {background-color: green; background-image: none; margin: 25px;}

The body of this document should have a green background. It also has a margin of 25 pixels, so the light blue background set for the HTML element should surround the BODY. If the BODY content is significantly shorter than the browser's window height, then the bottom border may be larger than 25 pixels.

TABLE Testing Section
 

The body of this document should have a green background. It also has a margin of 25 pixels, so the light blue background set for the HTML element should surround the BODY. If the BODY content is significantly shorter than the browser's window height, then the bottom border may be larger than 25 pixels.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec52.htm ##### CSS1 Test Suite: 5.2 Font Properties

CSS1 Test Suite: 5.2 Font Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec522.htm ##### CSS1 Test Suite: 5.2.2 font-family

CSS1 Test Suite: 5.2.2 font-family


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

DIV.a {font-family: serif;}DIV.b {font-family: monospace;}.one {font-family: serif;}.two {font-family: sans-serif;}.three {font-family: cursive;}.four {font-family: fantasy;}.five {font-family: monospace;}.six {font-family: sans-serif,cursive;}.seven {font-family: monospace,serif;}

This sentence is normal for the first division, which is the next five sentences; it should be a serif font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


This sentence should be in a sans-serif font, not cursive.

This sentence should be in a monospace font, not serif.


This sentence is normal for the first division, which is the next five sentences; it should be a monospace font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.

TABLE Testing Section
 

This sentence is normal for the first division, which is the next five sentences; it should be a serif font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


This sentence should be in a sans-serif font, not cursive.

This sentence should be in a monospace font, not serif.


This sentence is normal for the first division, which is the next five sentences; it should be a monospace font.

This sentence should be in a serif font.

This sentence should be in a sans-serif font.

This sentence should be in a cursive font.

This sentence should be in a fantasy font.

This sentence should be in a monospace font.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec523.htm ##### CSS1 Test Suite: 5.2.3 font-style

CSS1 Test Suite: 5.2.3 font-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-style: italic;}.two {font-style: oblique;}.three, I {font-style: normal;}

This paragraph should be in italics, but the last word of the sentence should be normal.

This paragraph should be oblique.

This paragraph should be normal.

TABLE Testing Section
 

This paragraph should be in italics, but the last word of the sentence should be normal.

This paragraph should be oblique.

This paragraph should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec524.htm ##### CSS1 Test Suite: 5.2.4 font-variant

CSS1 Test Suite: 5.2.4 font-variant


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-variant: small-caps;}.two {font-variant: normal;}

This Paragraph should be in Small Caps.

This Paragraph should be in Small Caps, but the Last Word in the Sentence should be Normal.

TABLE Testing Section
 

This Paragraph should be in Small Caps.

This Paragraph should be in Small Caps, but the Last Word in the Sentence should be Normal.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec525.htm ##### CSS1 Test Suite: 5.2.5 font-weight

CSS1 Test Suite: 5.2.5 font-weight


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-weight: bold;}.two {font-weight: bolder;}.three {font-weight: lighter;}.four {font-weight: 100;}.five {font-weight: 300;}.six {font-weight: 500;}.seven {font-weight: 700;}.eight {font-weight: 900;}.nine {font-weight: normal;}B {font-weight: lighter;}

This sentence should be bold.

This sentence should be bolder than normal.

This is a heading-4.

This is a bolder heading-4.

This sentence should be normal (boldface made lighter).

This sentence should be weight 100.

This sentence should be weight 300.

This sentence should be weight 500.

This sentence should be weight 700.

This sentence should be weight 900.

This sentence should be bold, but the last word in the sentence should be normal.

TABLE Testing Section
 

This sentence should be bold.

This sentence should be bolder than normal.

This is a heading-4.

This is a bolder heading-4.

This sentence should be normal (boldface made lighter).

This sentence should be weight 100.

This sentence should be weight 300.

This sentence should be weight 500.

This sentence should be weight 700.

This sentence should be weight 900.

This sentence should be bold, but the last word in the sentence should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec526.htm ##### CSS1 Test Suite: 5.2.6 font-size

CSS1 Test Suite: 5.2.6 font-size


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {font-size: medium;}.two {font-size: larger;}.three {font-size: smaller;}.four {font-size: xx-small;}.five {font-size: x-small;}.six {font-size: small;}.seven {font-size: large;}.eight {font-size: x-large;}.nine {font-size: xx-large;}.a {font-size: 0.5in;}.b {font-size: 1cm;}.c {font-size: 10mm;}.d {font-size: 18pt;}.e {font-size: 1.5pc;}.f {font-size: 2em;}.g {font-size: 3ex;}.h {font-size: 25px;}.i {font-size: 200%;}.j {font-size: -0.5in;}

This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent.

This sentence has been set to medium, which may or may not be the same size as unstyled text.

This sentence should be larger than unstyled text.

This sentence should be smaller than unstyled text.

This sentence should be very small, but the last word in the sentence should be medium.

This sentence should be rather small, but the last word in the sentence should be medium.

This sentence should be small, but the last word in the sentence should be medium.

This sentence should be large, but the last word in the sentence should be medium.

This sentence should be rather large, but the last word in the sentence should be medium.

This sentence should be very large, but the last word in the sentence should be medium.

This sentence should be half an inch tall.

This sentence should be one centimeter tall.

This sentence should be ten millimeters tall.

This sentence should be eighteen points tall.

This sentence should be one and one half picas tall.

This sentence should be two em tall.

This sentence should be three ex tall.

This sentence should be twenty-five pixels tall.

This sentence should be twice normal size.

This sentence should be normal size, since no negative values are allowed and therefore should be ignored.

TABLE Testing Section
 

This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent.

This sentence has been set to medium, which may or may not be the same size as unstyled text.

This sentence should be larger than unstyled text.

This sentence should be smaller than unstyled text.

This sentence should be very small, but the last word in the sentence should be medium.

This sentence should be rather small, but the last word in the sentence should be medium.

This sentence should be small, but the last word in the sentence should be medium.

This sentence should be large, but the last word in the sentence should be medium.

This sentence should be rather large, but the last word in the sentence should be medium.

This sentence should be very large, but the last word in the sentence should be medium.

This sentence should be half an inch tall.

This sentence should be one centimeter tall.

This sentence should be ten millimeters tall.

This sentence should be eighteen points tall.

This sentence should be one and one half picas tall.

This sentence should be two em tall.

This sentence should be three ex tall.

This sentence should be twenty-five pixels tall.

This sentence should be twice normal size.

This sentence should be normal size, since no negative values are allowed and therefore should be ignored.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec527.htm ##### CSS1 Test Suite: 5.2.7 font

CSS1 Test Suite: 5.2.7 font


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {font-size: 12px;}.one {font: italic small-caps 13pt Helvetica;}.two {font: 150%/150% serif;}.three {font: 150%/150% sans-serif;}.four {font: small/200% cursive;}.five {font: italic small-caps 900 150%/150% sans-serif;}.six {font: italic small-caps 100 150%/300% sans-serif;}.seven {font: italic small-caps 900 150%/2em monospace;}.eight {font: italic small-caps 500 150%/1in sans-serif;}.nine {font: oblique normal 700 18px/200% sans-serif;}.ten {font: normal 400 80%/2.5 sans-serif;}SPAN.color {background-color: silver;}

This element is unstyled, and should inherit a font-size of 12px from the BODY element. This is the "base font size" referred to in the following tests.

This element should be 13pt. Helvetica which is in small-cap italics.

This element should be in a serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a cursive font, 'small' in size, with a line-height 200% the height of the text's actual size. For example, if the font-size value small is calculated at 10px, then the line-height should be 20px. The actual value of the font-size is UA-dependent. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a monospace font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 2em, or twice the element's font size (18px and 36px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 500. Its font-size should be 150% the base font size, or 18px, and its line-height should be 1in. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, oblique and not small-caps, with a weight of 700. Its font-size should be 18 pixels, and its line-height should be 36px (200% this element's font size). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, with a weight of 400. Its font-size should be 80% of 12px, or 9.6px, and its line-height shoud be 2.5 times that, or 24px. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). The text should have a silver background. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.

TABLE Testing Section
 

This element is unstyled, and should inherit a font-size of 12px from the BODY element. This is the "base font size" referred to in the following tests.

This element should be 13pt. Helvetica which is in small-cap italics.

This element should be in a serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font. Its font-size should be 150% the base font size, and its line-height should 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a cursive font, 'small' in size, with a line-height 200% the height of the text's actual size. For example, if the font-size value small is calculated at 10px, then the line-height should be 20px. The actual value of the font-size is UA-dependent. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 150% of that value (18px and 27px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a monospace font, italicized and small caps, with a weight of 900. Its font-size should be 150% the base font size, and its line-height should be 2em, or twice the element's font size (18px and 36px, respectively). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 500. Its font-size should be 150% the base font size, or 18px, and its line-height should be 1in. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, oblique and not small-caps, with a weight of 700. Its font-size should be 18 pixels, and its line-height should be 36px (200% this element's font size). Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, with a weight of 400. Its font-size should be 80% of 12px, or 9.6px, and its line-height shoud be 2.5 times that, or 24px. Extra text is included for the purposes of testing this more effectively.

This element should be in a sans-serif font, italicized and small caps, with a weight of 100. Its font-size should be 150% the base font size, and its line-height should be 300% of that value (18px and 54px, respectively). The text should have a silver background. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec53.htm ##### CSS1 Test Suite: 5.3 Color and Background Properties

CSS1 Test Suite: 5.3 Color and Background Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec531.htm ##### CSS1 Test Suite: 5.3.1 color

CSS1 Test Suite: 5.3.1 color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {color: green;}

This sentence should be green.

This sentence should be green.

TABLE Testing Section
 

This sentence should be green.

This sentence should be green.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec532.htm ##### CSS1 Test Suite: 5.3.2 background-color

CSS1 Test Suite: 5.3.2 background-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {background-color: green;}.one {background-color: lime;}.two {background-color: transparent;}

This element's background should be green.

This element's background should be lime (light green).

This element's background should be green, and the last word in this sentence should also have a green background. This is because the background color of the parent element (the paragraph) should "shine through" the SPANned word "background," which was set to transparent. If the document background is visible, the browser is in error.

This element should allow the document background to "shine through." There should be no green backgrounds here!

TABLE Testing Section
 

This element's background should be green.

This element's background should be lime (light green).

This element's background should be green, and the last word in this sentence should also have a green background. This is because the background color of the parent element (the paragraph) should "shine through" the SPANned word "background," which was set to transparent. If the document background is visible, the browser is in error.

This element should allow the document background to "shine through." There should be no green backgrounds here!


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec533.htm ##### CSS1 Test Suite: 5.3.3 background-image

CSS1 Test Suite: 5.3.3 background-image


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {background-image: url(bg.gif);}.one {background-image: none;}

This sentence should be backed by an image-- a green grid pattern, in this case. The background image should also tile along both axes, because no repeat direction is specified (specific tests for repeating are found elsewhere).

This sentence should be backed by a repeated green-grid image, as should the last three words in this sentence. If it is not, then none is interpreted incorrectly. (none means that the element has no background image, allowing the parent to "shine through" by default; since the parent of the words "in this sentence" is the paragraph, then the paragraph's image should be visible.)

This sentence should NOT be backed by a repeated green-grid image, allowing the page's background to "shine through" instead.

TABLE Testing Section
 

This sentence should be backed by an image-- a green grid pattern, in this case. The background image should also tile along both axes, because no repeat direction is specified (specific tests for repeating are found elsewhere).

This sentence should be backed by a repeated green-grid image, as should the last three words in this sentence. If it is not, then none is interpreted incorrectly. (none means that the element has no background image, allowing the parent to "shine through" by default; since the parent of the words "in this sentence" is the paragraph, then the paragraph's image should be visible.)

This sentence should NOT be backed by a repeated green-grid image, allowing the page's background to "shine through" instead.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec534.htm ##### CSS1 Test Suite: 5.3.4 background-repeat

CSS1 Test Suite: 5.3.4 background-repeat


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {background-image: url(oransqr.gif); background-repeat: repeat-y;}.two {background-image: url(oransqr.gif); background-repeat: repeat-x;}.three {background-image: url(oransqr.gif); background-repeat: no-repeat;}.four {background-image: url(bg.gif); background-position: 50% 50%; background-repeat: repeat-y;}.five {background-image: url(crosshair2.gif); background-position: 50% 50%;       background-color: red;}.six {background-image: url(crosshair2.gif); background-position: center top;      background-color: red;}.seven {background-image: url(crosshair2.gif); background-position: top left;        background-color: red;}.eight {background-image: url(crosshair2.gif); background-position: bottom right;        background-color: red;}.nine {background-image: url(crosshair2.gif); background-position: 50% 50%;       background-color: red;}

This sentence should have an orange stripe repeated in the "y" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have an orange stripe repeated in the "x" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a single orange square behind it, placed at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a green-hatch stripe running vertically down the center of the paragraph, with the origin image exactly centered in the paragraph. This is because repeat-y specifies tiling in both directions on the y-axis. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious.

This paragraph should have a tiled background, with the origin image exactly centered in the paragraph. This is because background-repeat specifies tiling in all directions, regardless of the position of the origin image. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible then the image has not bee correctly tiled.

This sentence should have a fully tiled background which starts at its center top; that is, the background's origin should be the exact center of the top of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its top left. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its bottom right; in other words, a complete instance of the image should be anchored in the bottom right corner, with the tiled background extending out from there. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its center and is tiled in all directions; that is, the background's origin should be the exact center of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. In fact, a lot of extra text will be necessary to make this at all obvious. This is true because I am not able to increase the text size without resorting to either headings or other CSS properties, neither of which I want to use in this circumstance. This ought to be enough text, though. A background color is present, although if it is visible, then the image may not have been tiled correctly.

TABLE Testing Section
 

This sentence should have an orange stripe repeated in the "y" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have an orange stripe repeated in the "x" direction, starting at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a single orange square behind it, placed at the upper left corner (since the default for background-position is '0% 0%' and that property is not declared here). This is extra text included for the sole purpose of making the paragraph longer. Thank you for your understanding.

This sentence should have a green-hatch stripe running vertically down the center of the paragraph, with the origin image exactly centered in the paragraph. This is because repeat-y specifies tiling in both directions on the y-axis. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious.

This paragraph should have a tiled background, with the origin image exactly centered in the paragraph. This is because background-repeat specifies tiling in all directions, regardless of the position of the origin image. Note that this test is only valid if the user agent supports background-position (see test 5.3.6). I'll fill the paragraph with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible then the image has not bee correctly tiled.

This sentence should have a fully tiled background which starts at its center top; that is, the background's origin should be the exact center of the top of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its top left. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its bottom right; in other words, a complete instance of the image should be anchored in the bottom right corner, with the tiled background extending out from there. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. A background color is present, although if it is visible, then the image may not have been tiled correctly.

This sentence should have a fully tiled background which starts at its center and is tiled in all directions; that is, the background's origin should be the exact center of the paragraph. I'll fill it with extra text to make the conformance (or lack thereof) more obvious. In fact, a lot of extra text will be necessary to make this at all obvious. This is true because I am not able to increase the text size without resorting to either headings or other CSS properties, neither of which I want to use in this circumstance. This ought to be enough text, though. A background color is present, although if it is visible, then the image may not have been tiled correctly.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec535.htm ##### CSS1 Test Suite: 5.3.5 background-attachment

CSS1 Test Suite: 5.3.5 background-attachment


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background-image: url(bg.gif); background-repeat: repeat-x; background-attachment: fixed;}

This document should have a green grid-pattern line across the top of the page (or at least a tiled background) which does NOT scroll with the document. It should, instead, appear to be a fixed pattern past which the content scrolls, even when the end of the page is reached. In addition, the default Test Suite background should NOT appear, as it's been overridden by the styles shown above. I'll have to add a lot of extra text to the page in order to make all this something we can actually check. Don't worry, I'll think of something.

In fact, why not the relevant section from the CSS1 specification? A capital idea.



5.3.5    'background-attachment'

Value: scroll | fixed
Initial: scroll
Applies to: all elements
Inherited: no
Percentage values: N/A

If a background image is specified, the value of 'background-attachment' determines if it is fixed with regard to the canvas or if it scrolls along with the content.

  BODY {     background: red url(pendant.gif);    background-repeat: repeat-y;    background-attachment: fixed;  }

CSS1 core: UAs may treat 'fixed' as 'scroll'. However, it is recommended they interpret 'fixed' correctly, at least on the HTML and BODY elements, since there is no way for an author to provide an image only for those browsers that support 'fixed'.

TABLE Testing Section
 

This document should have a green grid-pattern line across the top of the page (or at least a tiled background) which does NOT scroll with the document. It should, instead, appear to be a fixed pattern past which the content scrolls, even when the end of the page is reached. In addition, the default Test Suite background should NOT appear, as it's been overridden by the styles shown above. I'll have to add a lot of extra text to the page in order to make all this something we can actually check. Don't worry, I'll think of something.

In fact, why not the relevant section from the CSS1 specification? A capital idea.



5.3.5    'background-attachment'

Value: scroll | fixed
Initial: scroll
Applies to: all elements
Inherited: no
Percentage values: N/A

If a background image is specified, the value of 'background-attachment' determines if it is fixed with regard to the canvas or if it scrolls along with the content.

  BODY {     background: red url(pendant.gif);    background-repeat: repeat-y;    background-attachment: fixed;  }

CSS1 core: UAs may treat 'fixed' as 'scroll'. However, it is recommended they interpret 'fixed' correctly, at least on the HTML and BODY elements, since there is no way for an author to provide an image only for those browsers that support 'fixed'.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec536.htm ##### CSS1 Test Suite: 5.3.6 background-position

CSS1 Test Suite: 5.3.6 background-position


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background-image: url(bg.gif); background-position: right top;      background-repeat: no-repeat;}.one {background-image: url(bg.gif); background-position: center;      background-repeat: no-repeat; background-color: aqua;}.two {background-image: url(bg.gif); background-position: 50% 50%;      background-repeat: no-repeat; background-color: aqua;}.three {background-image: url(bg.gif); background-position: bottom right;        background-repeat: no-repeat; background-color: aqua;}.four {background-image: url(bg.gif); background-position: 100% 100%;       background-repeat: no-repeat; background-color: aqua;}.five {background-image: url(bg.gif); background-position: 0% 50%;       background-repeat: no-repeat; background-color: aqua;}.six {background-image: url(bg.gif); background-position: 75% 25%;       background-repeat: no-repeat; background-color: aqua;}.seven {background-image: url(bg.gif); background-position: 20px 20px;       background-repeat: no-repeat; background-color: aqua;}

This document should have a single, small green image in its upper right corner.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image exactly at the left center; that is, the left center of the image should be fixed at the left center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image positioned 75% of the way across the element, and 25% down. The background color will make it easier to determine the edges of the paragraph, which should help in determining if all this is so, and the extra text should make the element long enough for this test to be simpler to evaluate.

This paragraph should have a single, small green image positioned 20 pixels down and to the left of the upper left-hand corner; that is, the upper left-hand corner of the image should be 20 pixels down and to the left of the upper-left corner of the element. The background color will make it easier to determine the edges of the paragraph, which should assist in evaluating this test.

TABLE Testing Section
 

This document should have a single, small green image in its upper right corner.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image exactly in its center; that is, the center of the image should be fixed at the center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image in its lower-right corner; that is, the lower right corner of the image should be fixed at the lower right corner of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to see its corners.

This paragraph should have a single, small green image exactly at the left center; that is, the left center of the image should be fixed at the left center of the paragraph. The background color will make it easier to determine the edges of the paragraph, and therefore allow you to calculate its center.

This paragraph should have a single, small green image positioned 75% of the way across the element, and 25% down. The background color will make it easier to determine the edges of the paragraph, which should help in determining if all this is so, and the extra text should make the element long enough for this test to be simpler to evaluate.

This paragraph should have a single, small green image positioned 20 pixels down and to the left of the upper left-hand corner; that is, the upper left-hand corner of the image should be 20 pixels down and to the left of the upper-left corner of the element. The background color will make it easier to determine the edges of the paragraph, which should assist in evaluating this test.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec537.htm ##### CSS1 Test Suite: 5.3.7 background

CSS1 Test Suite: 5.3.7 background


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {background: green url(oransqr.gif) repeat-x center top fixed;}.one {background: lime url(oransqr.gif) repeat-y 100% 0%;}.two {background: lime url(oransqr.gif) repeat-y center top;}.three {background: lime url(oransqr.gif) repeat-x left top;}

This document should have a green background with an orange strip running across the entire top of the page, since repeat-x indicates tiling in both directions of the x-axis. Furthermore, the strip should be fixed in place. I'll have to add extra text at the end of this page to make it long enough to scroll conveniently.

This paragraph should have a lime background and an orange strip which starts at the top right and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the center top and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the top left and runs to the top right. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

TABLE Testing Section
 

This document should have a green background with an orange strip running across the entire top of the page, since repeat-x indicates tiling in both directions of the x-axis. Furthermore, the strip should be fixed in place. I'll have to add extra text at the end of this page to make it long enough to scroll conveniently.

This paragraph should have a lime background and an orange strip which starts at the top right and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the center top and runs to the bottom. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?

This paragraph should have a lime background and an orange strip which starts at the top left and runs to the top right. Therefore, extra text would be in order, so that we can intelligently evaluate the performance of your browser in handling these declarations. Hey, I didn't say the page would be pretty, did I?


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec54.htm ##### CSS1 Test Suite: 5.4 Text Properties

CSS1 Test Suite: 5.4 Text Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec541.htm ##### CSS1 Test Suite: 5.4.1 word-spacing

CSS1 Test Suite: 5.4.1 word-spacing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {word-spacing: 0.3in;}.two {word-spacing: 0.5cm;}.three {word-spacing: 5mm;}.four {word-spacing: 3pt;}.five {word-spacing: 0.25pc;}.six {word-spacing: 1em;}.seven {word-spacing: 1ex;}.eight {word-spacing: 5px;}.nine {word-spacing: normal;}.ten {word-spacing: 300%;}.eleven {word-spacing: -0.2em;}

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them, but the last few words in the sentence should have normal spacing.

This sentence should have normal word-spacing, since percentage values are not allowed on this property.

This words in this sentence should have reduced space between them, since negative values are allowed on this property.

TABLE Testing Section
 

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them.

This words in this sentence should have extra space between them, but the last few words in the sentence should have normal spacing.

This sentence should have normal word-spacing, since percentage values are not allowed on this property.

This words in this sentence should have reduced space between them, since negative values are allowed on this property.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec542.htm ##### CSS1 Test Suite: 5.4.2 letter-spacing

CSS1 Test Suite: 5.4.2 letter-spacing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {letter-spacing: 0.3in;}.two {letter-spacing: 0.5cm;}.three {letter-spacing: 5mm;}.four {letter-spacing: 3pt;}.five {letter-spacing: 0.25pc;}.six {letter-spacing: 1em;}.seven {letter-spacing: 1ex;}.eight {letter-spacing: 5px;}.nine {letter-spacing: normal;}.ten {letter-spacing: 300%;}.eleven {letter-spacing: -0.1em;}

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them, but the last few words in the sentence should show normal spacing.

This letters in this sentence should have normal space between them, since percentage values are not allowed on this property.

This letters in this sentence should have reduced space between them, since negative values are allowed on this property.

TABLE Testing Section
 

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them.

This letters in this sentence should have extra space between them, but the last few words in the sentence should show normal spacing.

This letters in this sentence should have normal space between them, since percentage values are not allowed on this property.

This letters in this sentence should have reduced space between them, since negative values are allowed on this property.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec543.htm ##### CSS1 Test Suite: 5.4.3 text-decoration

CSS1 Test Suite: 5.4.3 text-decoration


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-decoration: underline;}.two {text-decoration: overline;}.three {text-decoration: line-through;}.four {text-decoration: blink;}B.five {text-decoration: none;}.six {text-decoration: underline overline;}.seven {text-decoration: underline overline line-through;}

This sentence should be underlined.

This sentence should be overlined.

This sentence should have stricken text (linethrough).

This element should be blinking. (It is not required, however, that UAs support this behavior.)

The text in this element should be underlined. The boldfaced text in this element should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own.

This sentence should be underlined and overlined.

This sentence should be underlined, overlined, and stricken.

There should be nothing visible between this sentence and the one above (there is an empty paragraph element with class of seven).

Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements.

The underlining in this sentence should be green, no matter what the text color may be.

The colors of the underlining in this sentence should be the same as that of the parent text (that is, the first word in the sentence, which should be black).

TABLE Testing Section
 

This sentence should be underlined.

This sentence should be overlined.

This sentence should have stricken text (linethrough).

This element should be blinking. (It is not required, however, that UAs support this behavior.)

The text in this element should be underlined. The boldfaced text in this element should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own.

This sentence should be underlined and overlined.

This sentence should be underlined, overlined, and stricken.

There should be nothing visible between this sentence and the one above (there is an empty paragraph element with class of seven).

Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements.

The underlining in this sentence should be green, no matter what the text color may be.

The colors of the underlining in this sentence should be the same as that of the parent text (that is, the first word in the sentence, which should be black).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec544.htm ##### CSS1 Test Suite: 5.4.4 vertical-align

CSS1 Test Suite: 5.4.4 vertical-align


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {font-size: 12pt;}.one {vertical-align: sub;}.two {vertical-align: super;}.three {vertical-align: top; font-size: 12pt;}.four {vertical-align: text-top; font-size: 12pt;}.five {vertical-align: middle; font-size: 12pt;}.six {vertical-align: bottom; font-size: 12pt;}.seven {vertical-align: text-bottom; font-size: 12pt;}.eight {vertical-align: baseline; font-size: 12pt;}.nine {vertical-align: 50%; font-size: 12px; line-height: 16px;}P.example {font-size: 14pt;}BIG {font-size: 16pt;}SMALL {font-size: 12pt;}.ttopalign {vertical-align: text-top;}.topalign {vertical-align: top;}.midalign {vertical-align: middle;}

[Image]The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle).

[Image] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line.

[Image] The image at the beginning of this sentence should be middle-aligned, which should align its middle with the point defined as the text baseline plus half the x-height.

[Image] The first four words in this sentence should be 12pt in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line.

[Image] The first eight words ("eight" has a descender) in this sentence should be 12pt in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line.

[Image] The first four words in this sentence should be 12pt in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line.

[Image]The first four words in this sentence should have a font-size of 12px and a line-height of 16px; they are also 50%-aligned, which should raise them 8px relative to the natural baseline.

In the following paragraph, all images should be aligned with the top of the 14-point text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the middle of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been SPANned appropriately in order to cause this to happen.

This paragraph [Image] contains many images [Image] and some text [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] the tallest element in [Image] whichever line the elements appear. [Image]

TABLE Testing Section
 

[Image]The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element.

[Image]The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle).

[Image] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line.

[Image] The image at the beginning of this sentence should be middle-aligned, which should align its middle with the point defined as the text baseline plus half the x-height.

[Image] The first four words in this sentence should be 12pt in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line.

[Image] The first eight words ("eight" has a descender) in this sentence should be 12pt in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line.

[Image] The first four words in this sentence should be 12pt in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line.

[Image]The first four words in this sentence should have a font-size of 12px and a line-height of 16px; they are also 50%-aligned, which should raise them 8px relative to the natural baseline.

In the following paragraph, all images should be aligned with the top of the 14-point text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value).

This paragraph [Image] contains many images [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the middle of [Image] a 14-point text element [Image] regardless of the line in which [Image] the images appear. [Image]

In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been SPANned appropriately in order to cause this to happen.

This paragraph [Image] contains many images [Image] and some text [Image] of varying heights [Image] and widths [Image] all of which [Image] should be aligned [Image] with the top of [Image] the tallest element in [Image] whichever line the elements appear. [Image]


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec545.htm ##### CSS1 Test Suite: 5.4.5 text-transform

CSS1 Test Suite: 5.4.5 text-transform


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.ttn {text-transform: none;}.cap {text-transform: capitalize;}.upp {text-transform: uppercase;}.low {text-transform: lowercase;}

This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal.

This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence.

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital letter.

This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, the last eight words should not be uppercase.

This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase.

TABLE Testing Section
 

This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal.

This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence.

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital letter.

This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, the last eight words should not be uppercase.

This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec546.htm ##### CSS1 Test Suite: 5.4.6 text-align

CSS1 Test Suite: 5.4.6 text-align


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-align: left;}.two {text-align: right;}.three {text-align: center;}.four {text-align: justify;}

This sentence should be left-justified.

This sentence should be right-justified.

This sentence should be centered.

This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages.

TABLE Testing Section
 

This sentence should be left-justified.

This sentence should be right-justified.

This sentence should be centered.

This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec547.htm ##### CSS1 Test Suite: 5.4.7 text-indent

CSS1 Test Suite: 5.4.7 text-indent


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {text-indent: 0.5in; background: aqua;}.two {text-indent: 2cm; background: aqua;}.three {text-indent: 20mm; background: aqua;}.four {text-indent: 24pt; background: aqua;}.five {text-indent: 2pc; background: aqua;}.six {text-indent: 2em; background: aqua;}.seven {text-indent: 2ex; background: aqua;}.eight {text-indent: 50%; background: aqua;}.nine {text-indent: 25px; background: aqua;}blockquote {text-indent: 50%; background: aqua;}

The first line of this sentence should be indented half an inch.

The first line of this sentence should be indented two centimeters.

The first line of this sentence should be indented twenty millimeters.

The first line of this sentence should be indented twenty-four points.

The first line of this sentence should be indented two picas.

The first line of this sentence should be indented two em.

The first line of this sentence should be indented two ex.

The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page.

The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page.

Only the first line of this sentence should be indented half an inch,
no matter where the lines might start, and
regardless of any other markup which may be present.

In the first half of the test page, this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY; in the second half, it is a child of TABLE.
TABLE Testing Section
 

The first line of this sentence should be indented half an inch.

The first line of this sentence should be indented two centimeters.

The first line of this sentence should be indented twenty millimeters.

The first line of this sentence should be indented twenty-four points.

The first line of this sentence should be indented two picas.

The first line of this sentence should be indented two em.

The first line of this sentence should be indented two ex.

The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page.

The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page.

Only the first line of this sentence should be indented half an inch,
no matter where the lines might start, and
regardless of any other markup which may be present.

In the first half of the test page, this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY; in the second half, it is a child of TABLE.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec548.htm ##### CSS1 Test Suite: 5.4.8 line-height

CSS1 Test Suite: 5.4.8 line-height


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {line-height: 0.5in; font-size: 12px;}.two {line-height: 2cm; font-size: 12px;}.three {line-height: 20mm; font-size: 12px;}.four {line-height: 24pt; font-size: 12px;}.five {line-height: 2pc; font-size: 12px;}.six {line-height: 2em; font-size: 12px;}.seven {line-height: 3ex; font-size: 12px;}.eight {line-height: 200%; font-size: 12px;}.nine {line-height: 2; font-size: 12px;}.ten {line-height: 50px; font-size: 12px;}.eleven {line-height: -1em; font-size: 12px;}TABLE .ten {line-height: normal; font-size: 12px;}DIV {background-color: silver;}SPAN.color {background-color: silver;}

This sentence should have a line-height of half an inch, which should cause extra spacing between the lines.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty millimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty-four points, which should cause extra spacing between the lines.

This sentence should have a line-height of two picas, which should cause extra spacing between the lines.

This sentence should have a line-height of two em, which should cause extra spacing between the lines.

This sentence should have a line-height of three ex, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the DIV's font size, or 28px; this should not cause extra spacing between the lines, since the line-height and font-size should have the same value.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which is 200% normal thanks to an inline style; this should cause extra spacing between the lines, as the font-size will be 28px and the line-height will be 56px.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This paragraph should have a line-height of 50 pixels in the first section, which should cause extra spacing between the lines. In the second section (within the table) its line-height should be normal.

This sentence should have a normal line-height, because negative values are not permitted for this property.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines. The text has a background color of silver, but no padding or border. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.

TABLE Testing Section
 

This sentence should have a line-height of half an inch, which should cause extra spacing between the lines.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty millimeters, which should cause extra spacing between the lines.

This sentence should have a line-height of twenty-four points, which should cause extra spacing between the lines.

This sentence should have a line-height of two picas, which should cause extra spacing between the lines.

This sentence should have a line-height of two em, which should cause extra spacing between the lines.

This sentence should have a line-height of three ex, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the DIV's font size, or 28px; this should not cause extra spacing between the lines, since the line-height and font-size should have the same value.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which should cause extra spacing between the lines.

This first part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This sentence should have a line-height of twice the font size, which is 200% normal thanks to an inline style; this should cause extra spacing between the lines, as the font-size will be 28px and the line-height will be 56px.

This second part of the DIV should have a line-height of twice the font size, which should cause extra spacing between the lines.

This paragraph should have a line-height of 50 pixels in the first section, which should cause extra spacing between the lines. In the second section (within the table) its line-height should be normal.

This sentence should have a normal line-height, because negative values are not permitted for this property.

This sentence should have a line-height of two centimeters, which should cause extra spacing between the lines. The text has a background color of silver, but no padding or border. The background color has been set on an inline element and should therefore only cover the text, not the interline spacing.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec55.htm ##### CSS1 Test Suite: 5.5 Box Properties

CSS1 Test Suite: 5.5 Box Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec5501.htm ##### CSS1 Test Suite: 5.5.01 margin-top

CSS1 Test Suite: 5.5.01 margin-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-top: 0;}.one {margin-top: 0.5in; background-color: aqua;}.two {margin-top: 25px; background-color: aqua;}.three {margin-top: 5em; background-color: aqua;}.four {margin-top: 25%; background-color: aqua;}.five {margin-top: 25px;}.six {margin-top: -10px; background-color: aqua;}P, UL {margin-bottom: 0;}

This element has a class of zero.

This element also has a class of zero.

This element should have a top margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

This element has a top margin of -10px, which should cause it to be shifted "upward" on the page, and no bottom margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

TABLE Testing Section
 

This element has a class of zero.

This element also has a class of zero.

This element should have a top margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a top margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

  • This list has a margin-top of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a top margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This element has a class of zero.

This element has a top margin of -10px, which should cause it to be shifted "upward" on the page, and no bottom margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5501b.htm ##### CSS1 Test Suite: 5.5.01 margin-top

CSS1 Test Suite: 5.5.01 margin-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-top: 0;}.one {margin-top: 25px; background-color: aqua;}.two {margin-top: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving the inline element an aqua background and a -10px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving the inline element an aqua background and a -10px top margin. Margins on inline elements do not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5502.htm ##### CSS1 Test Suite: 5.5.02 margin-right

CSS1 Test Suite: 5.5.02 margin-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-right: 0; text-align: right;}.one {margin-right: 0.5in; text-align: right; background-color: aqua;}.two {margin-right: 25px; text-align: right; background-color: aqua;}.three {margin-right: 5em; text-align: right; background-color: aqua;}.four {margin-right: 25%; text-align: right; background-color: aqua;}.five {margin-right: -10px; background-color: aqua;}

This element has a class of zero.

This sentence should have a right margin of half an inch.

This sentence should have a right margin of 25 pixels.

This sentence should have a right margin of 5 em.

This sentence should have a right margin of 25%, which is calculated with respect to the width of the parent element.

This element has a class of zero.

This paragraph has a right margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative right margin and the background color.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a right margin of half an inch.

This sentence should have a right margin of 25 pixels.

This sentence should have a right margin of 5 em.

This sentence should have a right margin of 25%, which is calculated with respect to the width of the parent element.

  • The right margin on this unordered list has been set to 25 pixels, and the background color has been set to gray.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its right margin also set to 25 pixels, which should combine with the list's margin to make 50 pixels of margin, and its background-color has been set to white.
  • This is an unclassed list item

This element has a class of zero.

This paragraph has a right margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative right margin and the background color.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5502b.htm ##### CSS1 Test Suite: 5.5.02 margin-right

CSS1 Test Suite: 5.5.02 margin-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-right: 25px; text-align: right; background-color: aqua;}.two {margin-right: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right margin only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px right margin only in the last line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right margin only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px right margin only in the last line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5503.htm ##### CSS1 Test Suite: 5.5.03 margin-bottom

CSS1 Test Suite: 5.5.03 margin-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-bottom: 0;}.one {margin-bottom: 0.5in; background-color: aqua;}.two {margin-bottom: 25px; background-color: aqua;}.three {margin-bottom: 5em; background-color: aqua;}.four {margin-bottom: 25%; background-color: aqua;}.five {margin-bottom: 25px;}.six {margin-bottom: -10px; background-color: aqua;}P, UL {margin-top: 0;}

This element has a class of zero.

This sentence should have a bottom margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a bottom margin of 25%, which will require extra text in order to make sure that the margin isn't applied to each line.

This element has a class of zero.

This element also has a class of zero.

This paragraph has a bottom margin of -10px, which should cause elements after it to be shifted "upward" on the page, and no top margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

This element has a class of zero.

This element also has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a bottom margin of half an inch, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 25 pixels, which will require extra text in order to make sure that the margin isn't applied to each line.

This sentence should have a bottom margin of 5 em, which will require extra text in order to make sure that the margin isn't applied to each line.

This element should have a bottom margin of 25%, which will require extra text in order to make sure that the margin isn't applied to each line.

This element has a class of zero.

This element also has a class of zero.

  • This list has a margin-bottom of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a bottom margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This paragraph has a bottom margin of -10px, which should cause elements after it to be shifted "upward" on the page, and no top margin. No other styles have been applied to it besides a light blue background color. In all other respects, the element should be normal.

This element has a class of zero.

This element also has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5503b.htm ##### CSS1 Test Suite: 5.5.03 margin-bottom

CSS1 Test Suite: 5.5.03 margin-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-bottom: 25px; background-color: aqua;}.two {margin-bottom: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px bottom margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5504.htm ##### CSS1 Test Suite: 5.5.04 margin-left

CSS1 Test Suite: 5.5.04 margin-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin-left: 0;}.one {margin-left: 0.5in; background-color: aqua;}.two {margin-left: 25px; background-color: aqua;}.three {margin-left: 5em; background-color: aqua;}.four {margin-left: 25%; background-color: aqua;}.five {margin-left: -10px; background-color: aqua;}

This element has a class of zero.

This sentence should have a left margin of half an inch.

This sentence should have a left margin of 25 pixels.

This sentence should have a left margin of 5 em.

This sentence should have a left margin of 25%, which is calculated with respect to the width of the parent element.

This element has a class of zero.

This paragraph has a left margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative left margin and the background color.

TABLE Testing Section
 

This element has a class of zero.

This sentence should have a left margin of half an inch.

This sentence should have a left margin of 25 pixels.

This sentence should have a left margin of 5 em.

This sentence should have a left margin of 25%, which is calculated with respect to the width of the parent element.

  • The left margin on this unordered list has been set to 25 pixels, and its background color has been set to gray.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its left margin also set to 25 pixels, which should combine with the list's margin to make 50 pixels of margin, and its background color has been set to white.
  • This is an unclassed list item

This element has a class of zero.

This paragraph has a left margin of -10px, which should cause it to be wider than it might otherwise be, and it has a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative left margin and the background color.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5504b.htm ##### CSS1 Test Suite: 5.5.04 margin-left

CSS1 Test Suite: 5.5.04 margin-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {margin-left: 25px; background-color: aqua;}.two {margin-left: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel left margin only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px left margin only in the first line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel left margin only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in -10px left margin only in the first line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5505.htm ##### CSS1 Test Suite: 5.5.05 margin

CSS1 Test Suite: 5.5.05 margin


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin: 0;}.one {margin: 0.5in; background-color: aqua;}.two {margin: 25px; background-color: aqua;}.three {margin: 5em; background-color: aqua;}.four {margin: 25%; background-color: aqua;}.five {margin: 25px;}.six {margin: -10px; background-color: aqua;}

NOTE: The following tests are separated by class-zero paragraphs, so as to prevent margin-collapsing as described in section 4.1.1 of the CSS1 specification.

This element has a class of zero.

This sentence should have an overall margin of half an inch, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25 pixels, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 5 em, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

This element has a class of zero.

This paragraph has an overall margin of -10px, which should make it wider than usual as well as shift it upward and pull subsequent text up toward it, and a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative margin and the background color.

This element has a class of zero.

TABLE Testing Section
 

NOTE: The following tests are separated by class-zero paragraphs, so as to prevent margin-collapsing as described in section 4.1.1 of the CSS1 specification.

This element has a class of zero.

This sentence should have an overall margin of half an inch, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25 pixels, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 5 em, which will require extra text in order to test.

This element has a class of zero.

This sentence should have an overall margin of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test.

This element has a class of zero.

  • This list has a margin of 25px, and a light blue background.
  • Therefore, it ought to have such a margin.
  • This list item has a margin of 25px, which should cause it to be offset in some fashion.
  • This list item has no special styles applied to it.

This element has a class of zero.

This paragraph has an overall margin of -10px, which should make it wider than usual as well as shift it upward and pull subsequent text up toward it, and a light blue background. In all other respects, however, the element should be normal. No styles have been applied to it besides the negative margin and the background color.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5505b.htm ##### CSS1 Test Suite: 5.5.05 margin

CSS1 Test Suite: 5.5.05 margin


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; margin: 0;}.one {margin: 25px; background-color: aqua;}.two {margin: -10px; background-color: aqua;}

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a 25px margin to the left side of the inline box in the first line it appears, and a 25px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a -10px margin to the left side of the inline box in the first line it appears, and a -10px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class one, giving it an aqua background and a 25px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a 25px margin to the left side of the inline box in the first line it appears, and a 25px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray.. It contains an inline element of class two, giving it an aqua background and a -10px margin. Margins on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. However, there should be a -10px margin to the left side of the inline box in the first line it appears, and a -10px margin to the right side of the inline element box in the last line where it appears.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5506.htm ##### CSS1 Test Suite: 5.5.06 padding-top

CSS1 Test Suite: 5.5.06 padding-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-top: 0;}.one {padding-top: 0.5in; background-color: aqua;}.two {padding-top: 25px; background-color: aqua;}.three {padding-top: 5em; background-color: aqua;}.four {padding-top: 25%; background-color: aqua;}.five {padding-top: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a top padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). This will require extra text in order to test.

This element should have no top padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a top padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a top padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). This will require extra text in order to test.

This element should have no top padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5506b.htm ##### CSS1 Test Suite: 5.5.06 padding-top

CSS1 Test Suite: 5.5.06 padding-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-top: 25px; background-color: aqua;}.two {padding-top: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no top padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px top padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no top padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5507.htm ##### CSS1 Test Suite: 5.5.07 padding-right

CSS1 Test Suite: 5.5.07 padding-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-right: 0;}.one {padding-right: 0.5in; text-align: right; background-color: aqua;}.two {padding-right: 25px; text-align: right; background-color: aqua;}.three {padding-right: 5em; text-align: right; background-color: aqua;}.four {padding-right: 25%; text-align: right; background-color: aqua;}.five {padding-right: -20px; text-align: right; background-color: aqua;}

This element has a class of zero.

This element should have a right padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have no right padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue). The text has been right-aligned in order to make the lack of right padding easier to see.

TABLE Testing Section
 

This element has a class of zero.

This element should have a right padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

This element should have a right padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue). The text has been right-aligned in order to make the right padding easier to see.

  • The right padding on this unordered list has been set to 25 pixels, which will require some extra text in order to test.
  • This list item has a right padding of 25 pixels, which will appear to the left of the gray padding of the UL element.

This element should have no right padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue). The text has been right-aligned in order to make the lack of right padding easier to see.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5507b.htm ##### CSS1 Test Suite: 5.5.07 padding-right

CSS1 Test Suite: 5.5.07 padding-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-right: 25px; text-align: right; background-color: aqua;}.two {padding-right: -10px; text-align: right; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right padding (which should also be light blue) only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in no right padding, since negative padding values are not allowed, in the last line in which the inline box appears.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one, which should result in 25-pixel right padding (which should also be light blue) only in the last line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, which should result in no right padding, since negative padding values are not allowed, in the last line in which the inline box appears.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5508.htm ##### CSS1 Test Suite: 5.5.08 padding-bottom

CSS1 Test Suite: 5.5.08 padding-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-bottom: 0;}.one {padding-bottom: 0.5in; background-color: aqua;}.two {padding-bottom: 25px; background-color: aqua;}.three {padding-bottom: 5em; background-color: aqua;}.four {padding-bottom: 25%; background-color: aqua;}.five {padding-bottom: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a bottom padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element has a class of zero.

This element should have no bottom padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a bottom padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a bottom padding of 25%, which is calculated with respect to the width of the parent element. This will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element has a class of zero.

This element should have no bottom padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5508b.htm ##### CSS1 Test Suite: 5.5.08 padding-bottom

CSS1 Test Suite: 5.5.08 padding-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-bottom: 25px; background-color: aqua;}.two {padding-bottom: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px bottom padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px bottom padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5509.htm ##### CSS1 Test Suite: 5.5.09 padding-left

CSS1 Test Suite: 5.5.09 padding-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding-left: 0;}.one {padding-left: 0.5in; background-color: aqua;}.two {padding-left: 25px; background-color: aqua;}.three {padding-left: 5em; background-color: aqua;}.four {padding-left: 25%; background-color: aqua;}.five {padding-left: -20px; background-color: aqua;}

This element has a class of zero.

This element should have a left padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 5em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no left padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have a left padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 5em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have a left padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

  • The left padding on this unordered list has been set to 25 pixels, which will require some extra test in order to test.
  • Another list item might not be such a bad idea, either, considering that such things do need to be double-checked. This list item has its left padding also set to 25 pixels, which should combine with the list's padding to make 50 pixels of margin.

This element should have no left padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5509b.htm ##### CSS1 Test Suite: 5.5.09 padding-left

CSS1 Test Suite: 5.5.09 padding-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {padding-left: 25px; background-color: aqua;}.two {padding-left: -10px; background-color: aqua;}

This element is unstyled save for a background color of gray. However, it contains an inline element of class one which should result in 25-pixel left padding (which should also be a light blue) only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

TABLE Testing Section
 

This element is unstyled save for a background color of gray. However, it contains an inline element of class one which should result in 25-pixel left padding (which should also be a light blue) only in the first line in which the inline box appears.

This element is unstyled save for a background color of gray. However, it contains an inline element of class two, giving it an aqua background and no bottom padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5510.htm ##### CSS1 Test Suite: 5.5.10 padding

CSS1 Test Suite: 5.5.10 padding


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding: 0;}.one {padding: 0.5in; background-color: aqua;}.two {padding: 25px; background-color: aqua;}.three {padding: 5em; background-color: aqua;}.four {padding: 25%; background-color: aqua;}.five {padding: -20px; background-color: aqua;}

This element has a class of zero.

This element should have an overall padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).

TABLE Testing Section
 

This element has a class of zero.

This element should have an overall padding of half an inch, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25 pixels, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 5 em, which will require extra text in order to test. Both the content background and the padding should be aqua (light blue).

This element should have an overall padding of 25%, which is calculated with respect to the width of the parent element. Both the content background and the padding should be aqua (light blue).

This element should have no padding, since negative padding values are not allowed. Both the content background and the normal padding should be aqua (light blue).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5510b.htm ##### CSS1 Test Suite: 5.5.10 padding

CSS1 Test Suite: 5.5.10 padding


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; padding: 0;}.one {padding: 25px; background-color: aqua;}.two {padding: -10px; background-color: aqua;}

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display above and below each line. However, there should be at least 25px of padding to the left side of the inline box in the first line it appears, and 25px of padding to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element has a class of zero.

TABLE Testing Section
 

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class one, giving it an aqua background and a 25px padding. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height. There may be implementation-specific limits on how much of the padding the user agent is able to display above and below each line. However, there should be at least 25px of padding to the left side of the inline box in the first line it appears, and 25px of padding to the right side of the inline element box in the last line where it appears.

This element has a class of zero.

This element is unstyled save for a background color of gray. It contains an inline element of class two, giving it an aqua background and no padding, since negative padding values are not allowed. Padding on inline elements does not affect line-height calculations, so all lines in this element should have the same line-height.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5511.htm ##### CSS1 Test Suite: 5.5.11 border-top-width

CSS1 Test Suite: 5.5.11 border-top-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-top-width: 0;}.one {border-top-width: 25px; border-style: solid;}.two {border-top-width: thick; border-style: solid;}.three {border-top-width: medium; border-style: solid;}.four {border-top-width: thin; border-style: solid;}.five {border-top-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This paragraph should have a top border width of 25 pixels.

This paragraph should have a thick top border width.

This paragraph should have a medium top border width.

This paragraph should have a thin top border width.

This paragraph should have no border and no extra "padding" on its top side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This paragraph should have a top border width of 25 pixels.

This paragraph should have a thick top border width.

This paragraph should have a medium top border width.

This paragraph should have a thin top border width.

This paragraph should have no border and no extra "padding" on its top side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5511b.htm ##### CSS1 Test Suite: 5.5.11 border-top-width

CSS1 Test Suite: 5.5.11 border-top-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top-width: 25px; border-style: solid;}.two {border-top-width: thin; border-style: solid;}.three {border-top-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the top side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no top border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the top side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no top border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5512.htm ##### CSS1 Test Suite: 5.5.12 border-right-width

CSS1 Test Suite: 5.5.12 border-right-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-right-width: 0;}.one {border-right-width: 25px; border-style: solid;}.two {border-right-width: thick; border-style: solid;}.three {border-right-width: medium; border-style: solid;}.four {border-right-width: thin; border-style: solid;}.five {border-right-width: 100px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a right border width of 25 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick right border width, which will be more obvious if the element is more than one line long.

This element should have a medium right border width, which will be more obvious if the element is more than one line long.

This element should have a thin right border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its right side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a right border width of 25 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick right border width, which will be more obvious if the element is more than one line long.

This element should have a medium right border width, which will be more obvious if the element is more than one line long.

This element should have a thin right border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its right side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5512b.htm ##### CSS1 Test Suite: 5.5.12 border-right-width

CSS1 Test Suite: 5.5.12 border-right-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-right-width: 25px; border-style: solid;}.two {border-right-width: thin; border-style: solid;}.three {border-right-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the right side of the last box of the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no right border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the right side of the last box of the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no right border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5513.htm ##### CSS1 Test Suite: 5.5.13 border-bottom-width

CSS1 Test Suite: 5.5.13 border-bottom-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-bottom-width: 0;}.one {border-bottom-width: 50px; border-style: solid;}.two {border-bottom-width: thick; border-style: solid;}.three {border-bottom-width: medium; border-style: solid;}.four {border-bottom-width: thin; border-style: solid;}.five {border-bottom-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a bottom border width of 50 pixels.

This element should have a thick bottom border width.

This element should have a medium bottom border width.

This element should have a thin bottom border width.

This element should have no border and no extra "padding" on its bottom side, as no border-style was set.

This element has a class of zero.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a bottom border width of 50 pixels.

This element should have a thick bottom border width.

This element should have a medium bottom border width.

This element should have a thin bottom border width.

This element should have no border and no extra "padding" on its bottom side, as no border-style was set.

This element has a class of zero.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5513b.htm ##### CSS1 Test Suite: 5.5.13 border-bottom-width

CSS1 Test Suite: 5.5.13 border-bottom-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom-width: 25px; border-style: solid;}.two {border-bottom-width: thin; border-style: solid;}.three {border-bottom-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the bottom side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no bottom border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the bottom side of each box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no bottom border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5514.htm ##### CSS1 Test Suite: 5.5.14 border-left-width

CSS1 Test Suite: 5.5.14 border-left-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-left-width: 0;}.one {border-left-width: 50px; border-style: solid;}.two {border-left-width: thick; border-style: solid;}.three {border-left-width: medium; border-style: solid;}.four {border-left-width: thin; border-style: solid;}.five {border-left-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a left border width of 50 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick left border width, which will be more obvious if the element is more than one line long.

This element should have a medium left border width, which will be more obvious if the element is more than one line long.

This element should have a thin left border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its left side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have a left border width of 50 pixels, which will be more obvious if the element is more than one line long.

This element should have a thick left border width, which will be more obvious if the element is more than one line long.

This element should have a medium left border width, which will be more obvious if the element is more than one line long.

This element should have a thin left border width, which will be more obvious if the element is more than one line long.

This element should have no border and no extra "padding" on its left side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5514b.htm ##### CSS1 Test Suite: 5.5.14 border-left-width

CSS1 Test Suite: 5.5.14 border-left-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-left-width: 25px; border-style: solid;}.two {border-left-width: thin; border-style: solid;}.three {border-left-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the left side of the first box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no left border width or visible border because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on the left side of the first box in the inline element (and the UA's default border on the other three sides). There is also an inline element of class three, which should have no left border width or visible border because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5515.htm ##### CSS1 Test Suite: 5.5.15 border-width

CSS1 Test Suite: 5.5.15 border-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {background-color: silver; border-width: 0;}.one {border-width: 50px; border-style: solid;}.two {border-width: thick; border-style: solid;}.three {border-width: medium; border-style: solid;}.four {border-width: thin; border-style: solid;}.five {border-width: 25px;}

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have an overall border width of 50 pixels.

This element should have a thick overall border width.

This element should have a medium overall border width.

This element should have a thin overall border width.

This element should have no border and no extra "padding" on any side, as no border-style was set.

TABLE Testing Section
 

(These will only work if border-style is supported.)

This element has a class of zero.

This element should have an overall border width of 50 pixels.

This element should have a thick overall border width.

This element should have a medium overall border width.

This element should have a thin overall border width.

This element should have no border and no extra "padding" on any side, as no border-style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5515b.htm ##### CSS1 Test Suite: 5.5.15 border-width

CSS1 Test Suite: 5.5.15 border-width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-width: 25px; border-style: solid;}.two {border-width: thin; border-style: solid;}.three {border-width: 25px;}

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on each side of each box in the inline element. There is also an inline element of class three, which should have no border width because no border style was set.

TABLE Testing Section
 

This element has a class of one. However, it contains an inline element of class two, which should result in a thin solid border on each side of each box in the inline element. There is also an inline element of class three, which should have no border width because no border style was set.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5516.htm ##### CSS1 Test Suite: 5.5.16 border-color

CSS1 Test Suite: 5.5.16 border-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-color: purple; border-style: solid;}.two {border-color: purple; border-width: medium; border-style: solid;}.three {border-color: purple green blue yellow; border-width: medium; border-style: solid;}

This element should have a purple border surrounding it.

This element should have a medium-width purple border surrounding it.

This element should be surrounded by a medium width border which is purple on top, green on the right side, blue on the bottom, and yellow on the left side.

TABLE Testing Section
 

This element should have a purple border surrounding it.

This element should have a medium-width purple border surrounding it.

This element should be surrounded by a medium width border which is purple on top, green on the right side, blue on the bottom, and yellow on the left side.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5516b.htm ##### CSS1 Test Suite: 5.5.16 border-color

CSS1 Test Suite: 5.5.16 border-color


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-color: purple; border-style: solid;}.two {border-color: purple; border-width: medium; border-style: solid;}.three {border-color: purple green blue yellow; border-width: medium; border-style: solid;}

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, class two, and class three. The effect for each inline element should be to have a purple medium-width solid border in the first and second cases, and a purple-green-blue-yellow medium-width solid border in the third. The line-height of the parent element should not change at all, on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, class two, and class three. The effect for each inline element should be to have a purple medium-width solid border in the first and second cases, and a purple-green-blue-yellow medium-width solid border in the third. The line-height of the parent element should not change at all, on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5517.htm ##### CSS1 Test Suite: 5.5.17 border-style

CSS1 Test Suite: 5.5.17 border-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-style: dotted; border-color: black; border-width: thick;}.two {border-style: dashed; border-color: black; border-width: thick;}.three {border-style: solid; border-color: black; border-width: thick;}.four {border-style: double; border-color: black; border-width: thick;}.five {border-style: groove; border-color: olive; border-width: thick;}.six {border-style: ridge; border-color: olive; border-width: thick;}.seven {border-style: inset; border-color: olive; border-width: thick;}.eight {border-style: outset; border-color: olive; border-width: thick;}.nine {border-style: double groove; border-color: purple; border-width: thick;}.ten {border-style: double groove ridge inset;   border-color: purple; border-width: thick;}.eleven {border-style: none; border-color: red; border-width: thick;}

This paragraph should have a thick black dotted border all the way around.

This paragraph should have a thick black dashed border all the way around.

This paragraph should have a thick black solid border all the way around.

This paragraph should have a thick black double border all the way around.

This paragraph should have a thick olive groove border all the way around.

This paragraph should have a thick olive ridge border all the way around.

This paragraph should have a thick olive inset border all the way around.

This paragraph should have a thick olive outset border all the way around.

This paragraph should have thick double top and bottom borders, and thick grooved side borders. The color of all four sides should be based on purple.

This paragraph should have, in clockwise order from the top, a double, grooved, ridged, and inset thick border. The color of all four sides should be based on purple.

This paragraph should have no border at all.

TABLE Testing Section
 

This paragraph should have a thick black dotted border all the way around.

This paragraph should have a thick black dashed border all the way around.

This paragraph should have a thick black solid border all the way around.

This paragraph should have a thick black double border all the way around.

This paragraph should have a thick olive groove border all the way around.

This paragraph should have a thick olive ridge border all the way around.

This paragraph should have a thick olive inset border all the way around.

This paragraph should have a thick olive outset border all the way around.

This paragraph should have thick double top and bottom borders, and thick grooved side borders. The color of all four sides should be based on purple.

This paragraph should have, in clockwise order from the top, a double, grooved, ridged, and inset thick border. The color of all four sides should be based on purple.

This paragraph should have no border at all.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5517b.htm ##### CSS1 Test Suite: 5.5.17 border-style

CSS1 Test Suite: 5.5.17 border-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-style: dashed; border-color: black; border-width: thick;}.two {border-style: groove; border-color: purple; border-width: thick;}.three {border-style: none; border-color: purple; border-width: thick;}

This is an unstyled element, save for the background color, and it contains inline elements with classes of class one, which will result in a dashed thick black border; class two, which should result in a grooved thick purple border, and class three, which should result in no border at all. The line-height of the parent element should not change, on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and it contains inline elements with classes of class one, which will result in a dashed thick black border; class two, which should result in a grooved thick purple border, and class three, which should result in no border at all. The line-height of the parent element should not change, on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5518.htm ##### CSS1 Test Suite: 5.5.18 border-top

CSS1 Test Suite: 5.5.18 border-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top: purple double 10px;}.two {border-top: purple thin solid;}.three {border-top: black medium solid;}TD {border-top: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their top sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel top border.

This paragraph should have a thin purple top border.

Every cell in this table should have a 2-pixel solid green top border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their top sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel top border.

This paragraph should have a thin purple top border.

Every cell in this table should have a 2-pixel solid green top border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this list should have a medium-width black border at its top.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5518b.htm ##### CSS1 Test Suite: 5.5.18 border-top

CSS1 Test Suite: 5.5.18 border-top


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-top: purple double 10px;}.two {border-top: purple thin solid;}

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double top border; and class two, which should have a thin solid purple top border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double top border; and class two, which should have a thin solid purple top border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5519.htm ##### CSS1 Test Suite: 5.5.19 border-right

CSS1 Test Suite: 5.5.19 border-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-right: 20px;}.one {border-right: purple double 10px;}.two {border-right: purple thin solid;}.threea {border-right: black medium solid;}.threeb {border-right: purple medium solid;}.threec {border-right: blue medium solid;}TD {border-right: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their right sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel right border.

This paragraph should have a thin purple right border.

Every cell in this table should have a 2-pixel solid green right border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their right sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel right border.

This paragraph should have a thin purple right border.

Every cell in this table should have a 2-pixel solid green right border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this 'parent' list should have a medium-width border along its right side, in each of three colors. The first item's border should travel the entire height the nested list (to end near the baseline of the line "...nested within the list item."), even though the nested list does not have any border styles set. The borders should line up together at the right edge of the document's body, as each list element has a default width of 100%.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5519b.htm ##### CSS1 Test Suite: 5.5.19 border-right

CSS1 Test Suite: 5.5.19 border-right


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-right: 20px;}.one {border-right: purple double 10px;}.two {border-right: purple thin solid;}

This paragraph has a background color of silver and a 20-pixel right margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double right border; and class two, which should have a thin solid purple right border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This paragraph has a background color of silver and a 20-pixel right margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double right border; and class two, which should have a thin solid purple right border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5520.htm ##### CSS1 Test Suite: 5.5.20 border-bottom

CSS1 Test Suite: 5.5.20 border-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom: purple double 10px;}.two {border-bottom: purple thin solid;}.three {border-bottom: black medium solid;}TD {border-bottom: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their bottom sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel bottom border.

This paragraph should have a thin purple bottom border.

Every cell in this table should have a 2-pixel solid green bottom border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their bottom sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel bottom border.

This paragraph should have a thin purple bottom border.

Every cell in this table should have a 2-pixel solid green bottom border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this list should have a medium-width black border at its bottom, which for the first item means that it should appear beneath the nested list (below the line "...nested within the list item.").

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5520b.htm ##### CSS1 Test Suite: 5.5.20 border-bottom

CSS1 Test Suite: 5.5.20 border-bottom


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border-bottom: purple double 10px;}.two {border-bottom: purple thin solid;}

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double bottom border; and class two, which should have a thin solid purple bottom border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with classes of class one, which should have a 10-pixel purple double bottom border; and class two, which should have a thin solid purple bottom border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5521.htm ##### CSS1 Test Suite: 5.5.21 border-left

CSS1 Test Suite: 5.5.21 border-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-left: 20px;}.one {border-left: purple double 10px;}.two {border-left: purple thin solid;}.threea {border-left: black medium solid;}.threeb {border-left: purple medium solid;}.threec {border-left: blue medium solid;}TD {border-left: green 2px solid;}

Note that all table cells on this page should have a two-pixel solid green border along their left sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel left border.

This paragraph should have a thin purple left border.

Every cell in this table should have a 2-pixel solid green left border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along their left sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a purple, double, 10-pixel left border.

This paragraph should have a thin purple left border.

Every cell in this table should have a 2-pixel solid green left border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!
  • This is a list item...
    • ...and this...
    • ...is a second list...
    • ...nested within the list item.
  • This is a second list item.
  • Each list item in this 'parent' list should have a medium-width border along its left side, in each of three colors. The first item's border should travel the entire height the nested list (to end near the baseline of the line "...nested within the list item."), even though the nested list does not have any border styles set.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5521b.htm ##### CSS1 Test Suite: 5.5.21 border-left

CSS1 Test Suite: 5.5.21 border-left


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P {margin-left: 20px;}.one {border-left: purple double 10px;}.two {border-left: purple thin solid;}

This paragraph has a background color of silver and a 20-pixel left margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double left border; and class two, which should have a thin solid purple left border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This paragraph has a background color of silver and a 20-pixel left margin, and it contains inline elements with classes of class one, which should have a 10-pixel purple double left border; and class two, which should have a thin solid purple left border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5522.htm ##### CSS1 Test Suite: 5.5.22 border

CSS1 Test Suite: 5.5.22 border


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border: medium black solid;}.two {border: thin maroon ridge;}.three {border: 10px teal outset;}.four {border: 10px olive inset;}.five {border: 10px maroon;}.six {border: maroon double;}.seven {border: left red solid;}.eight {border: 0px;}TD {border: 2px solid green;}

Note that all table cells on this page should have a two-pixel solid green border along all four sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a medium black solid border all the way around.

This paragraph should have a thin maroon ridged border all the way around.

This paragraph should have a ten-pixel-wide teal outset border all the way around.

This paragraph should have a ten-pixel-wide olive inset border all the way around.

This paragraph should have no border around it, as the border-style was not set, and it should not be offset in any way.

This paragraph should have a medium maroon double border around it, even though border-width was not explicitly set.

This paragraph should have no border around it, as its declaration is invalid and should be ignored.

The following image is also an anchor which points to a target on this page, but it should not have a border around it: [Image].

Every cell in this table should have a 2-pixel solid green border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!

This is an unstyled element.

TABLE Testing Section
 

Note that all table cells on this page should have a two-pixel solid green border along all four sides. This border applies only to the cells, not the rows which contain them.

This paragraph should have a medium black solid border all the way around.

This paragraph should have a thin maroon ridged border all the way around.

This paragraph should have a ten-pixel-wide teal outset border all the way around.

This paragraph should have a ten-pixel-wide olive inset border all the way around.

This paragraph should have no border around it, as the border-style was not set, and it should not be offset in any way.

This paragraph should have a medium maroon double border around it, even though border-width was not explicitly set.

This paragraph should have no border around it, as its declaration is invalid and should be ignored.

The following image is also an anchor which points to a target on this page, but it should not have a border around it: [Image].

Every cell in this table should have a 2-pixel solid green border. This is also true of the table-testing section in the second half of the test page.
Cell oneCell two
Nested single-cell table!

This is an unstyled element.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5522b.htm ##### CSS1 Test Suite: 5.5.22 border

CSS1 Test Suite: 5.5.22 border


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {border: 10px teal outset;}.two {border: 10px olive inset;}

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, which should result in a 10-pixel outset teal border; and class two, which should result in a 10-pixel inset olive border. The line-height of the parent element should not change on any line.

TABLE Testing Section
 

This is an unstyled element, save for the background color, and containing inline elements with a classes of class one, which should result in a 10-pixel outset teal border; and class two, which should result in a 10-pixel inset olive border. The line-height of the parent element should not change on any line.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5523.htm ##### CSS1 Test Suite: 5.5.23 width

CSS1 Test Suite: 5.5.23 width


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {width: 50px;}.two {width: 50%;}TABLE {width: 50%;}

[Image]

The square above should be fifty pixels wide.

[Image]

The square above should be half as wide as the image's parent element (either the BODY or the table cell).

This paragraph should be half the width of its parent element (either the BODY or the table, which should itself be half as wide as the BODY element). This is extra text included to ensure that this will be a fair test of the width property without the need for the user to resize the viewing window.

TABLE Testing Section
 [Image]

The square above should be fifty pixels wide.

[Image]

The square above should be half as wide as the image's parent element (either the BODY or the table cell).

This paragraph should be half the width of its parent element (either the BODY or the table, which should itself be half as wide as the BODY element). This is extra text included to ensure that this will be a fair test of the width property without the need for the user to resize the viewing window.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5524.htm ##### CSS1 Test Suite: 5.5.24 height

CSS1 Test Suite: 5.5.24 height


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {height: 50px;}.two {height: 100px;}

[Image]

The square above should be fifty pixels tall.

[Image]

The square above should be 100 pixels tall and wide.

[Image]

The rectangular image above should be 100 pixels tall and 30 pixels wide (the original image is 50x15, and the size has been doubled using the height property).

TABLE Testing Section
 [Image]

The square above should be fifty pixels tall.

[Image]

The square above should be 100 pixels tall and wide.

[Image]

The rectangular image above should be 100 pixels tall and 30 pixels wide (the original image is 50x15, and the size has been doubled using the height property).


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5525.htm ##### CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {float: left;}.two {float: right;}

[Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window. In this case, it is the image which has been floated to the left.



[Image]

This text should be flowing past a tall orange rectangle on the right side of the browser window. In this case, it is the image which has been floated to the right.

TABLE Testing Section
 [Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window. In this case, it is the image which has been floated to the left.



[Image]

This text should be flowing past a tall orange rectangle on the right side of the browser window. In this case, it is the image which has been floated to the right.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5525b.htm ##### CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.test {background: white; font-size: 20px;        margin-left: 30px; margin-right: 10px; padding: 0; border: 0;}IMG {padding: 0; border: 0; margin: 0;}P.test IMG {float: left;}#img2 {margin-top: 30px; margin-left: 30px;}#img3 {margin-top: -30px; margin-left: -30px;}#img4 {margin-right: 30px; margin-bottom: 30px;}#img5 {margin-right: -30px; margin-bottom: -30px;}

This paragraph should have a white background which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever. If the background of the entire box is not white, this may cause problems with the following tests; at any rate, it must be taken into account.

[Image] The image in the upper left corner of this paragraph should be floated left, and nothing more. The edges of the white background should line up with the top and left edges of the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed down and to the right 30 pixels each from the upper left corner of the paragraph's box, and displace the paragraph text accordingly. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed up and to the left 30 pixels each from the upper left corner of the paragraph's box, thus causing the edges of the white background to align with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, there should be 30 pixels of space between the right and bottom edges of the image and the paragraph text around it. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, the text should overlap the image's right and bottom sides, lining up with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

TABLE Testing Section
 

This paragraph should have a white background which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever. If the background of the entire box is not white, this may cause problems with the following tests; at any rate, it must be taken into account.

[Image] The image in the upper left corner of this paragraph should be floated left, and nothing more. The edges of the white background should line up with the top and left edges of the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed down and to the right 30 pixels each from the upper left corner of the paragraph's box, and displace the paragraph text accordingly. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be pushed up and to the left 30 pixels each from the upper left corner of the paragraph's box, thus causing the edges of the white background to align with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, there should be 30 pixels of space between the right and bottom edges of the image and the paragraph text around it. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.

[Image] The image in the upper left corner of this paragraph should be floated left, and the edges of the white background should line up with the top and left edges of the image. However, the text should overlap the image's right and bottom sides, lining up with the thick gray lines in the image. This paragraph should have a white background, first of all, which extends to the edges of the element's box. There is no padding set on this paragraph whatsoever.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5525c.htm ##### CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align: justify;}.one {float: left; width: 50%; background-color: yellow; padding: 0; margin: 0;}.two {float: left; background-color: yellow; width: 100%;      margin: 0; padding: 0; border-width: 0;}.three {float: none;}.four {float: left; font-size: 200%; font-weight: bold;    width: 1.5em; background-color: silver;}.five {float: right; width: 20em;      background-color: yellow; border: 3px solid red;      padding: 5px; margin: 10px;}.six {float: right; width: 20em;      background-color: yellow; border: none;      padding: 5px; margin: 10px;}.seven {float: right; width: 50%;       background-color: yellow; border: 1px solid gray;}.eight {float: left; width: 25%;        background-color: #66CCFF;        padding: 0; margin: 0}.nine {float: right; width: 25%;       background-color: yellow;       padding: 0; margin: 0}

This paragraph is of class "one". It has a width of 50% and is floated to the left.

This paragraph should start on the right side of a yellow box which contains the previous paragraph. Since the text of this element is much longer than the text in the previous element, the text will wrap around the yellow box. There is no padding, border or margins on this and the previous element, so the text of the two elements should be very close to each other.



This paragraph is of class "two". Since the width has been set to 100%, it should automatically be as wide as its parent element allows it to be. Therefore, even though the element is floated, there is no room for other content on the sides and a orange square image should be seen AFTER the paragraph, not next to it. A yellow background has been added to this paragraph for diagnostic purposes.

[Image]

This paragraph is floated to the left and the orange square image should appear to the right of the paragraph. This paragraph has a yellow background and no padding, margin or border. The right edge of this yellow box should be horizontally aligned with the left edge of the yellow box undernearth.

[Image]

This paragraph is floated to the right (using a STYLE attribute) and the orange square image should appear to the left of the paragraph. This paragraph has a yellow background and no padding, margin or border. The left edge of this yellow box should be horizonally aligned with the right edge of the yellow box above.

[Image]

The first letter (a "T") of this paragraph should float left and be twice the font-size of the rest of the paragraph, as well as bold, with a content width of 1.5em and a background-color of silver. The top of the big letter "T" should be vertically aligned with the top of the first line of this paragraph. This is commonly known as "drop-cap".



This paragraph should be floated to the right, sort of like a 'sidebar' in a magazine article. Its width is 20em so the box should not be reformatted when the size of the viewport is changed (e.g. when the window is resized). The background color of the element is yellow, and there should be a 3px solid red border outside a 5px wide padding. Also, the element has a 10px wide margin around it where the blue background of the paragraph in the normal flow should shine through.

This paragraph is not floating. If there is enough room, the textual content of the paragraph should appear on the left side of the yellow "sidebar" on the right. The content of this element should flow around the floated element. However, the floated element may or may not be obscured by the blue background of this element, as the specification does not say which is drawn "on top." Even if the floated element is obscured, it still forces the content of this element to flow around it. If the floated element is not obscured, then the blue rectangle of this paragraph should extend 10px above and to the right of the sidebar's red border, due to the margin styles set for the floated element.



This paragraph is placed inside a DIV element which is floated to the right. The width of the DIV element is 20em. The background is yellow and there is a 5px padding, a 10px margin and no border. Since it is floated, the yellow box should be rendered on top of the background and borders of adjacent non-floated elements. To the left of this yellow box there should be a short paragraph with a blue background and a red border. The yellow box should be rendered on top of the bottom red border. I.e., the bottom red border will appear broken where it's overlaid by the yellow rectangle.

See description in the box on the right side



This paragraph is inside a DIV which is floated left. Its background is blue and the width is 25%.

This paragraph is inside a DIV which is floated right. Its background is yellow and the width is 25%.

This paragraph should appear between a blue box (on the left) and a yellow box (on the right).



See description in the box on the left side.

This paragraph is inside a DIV which is floated left. The background of the DIV element is blue and its width is 75%. This text should all be inside the blue rectangle. The blue DIV element has another DIV element as a child. It has a yellow background color and is floated to the right. Since it is a child of the blue DIV, the yellow DIV should appear inside the blue rectangle. Due to it being floated to the right and having a 10px right margin, the yellow rectange should have a 10px blue stripe on its right side.



TABLE Testing Section
 

This paragraph is of class "one". It has a width of 50% and is floated to the left.

This paragraph should start on the right side of a yellow box which contains the previous paragraph. Since the text of this element is much longer than the text in the previous element, the text will wrap around the yellow box. There is no padding, border or margins on this and the previous element, so the text of the two elements should be very close to each other.



This paragraph is of class "two". Since the width has been set to 100%, it should automatically be as wide as its parent element allows it to be. Therefore, even though the element is floated, there is no room for other content on the sides and a orange square image should be seen AFTER the paragraph, not next to it. A yellow background has been added to this paragraph for diagnostic purposes.

[Image]

This paragraph is floated to the left and the orange square image should appear to the right of the paragraph. This paragraph has a yellow background and no padding, margin or border. The right edge of this yellow box should be horizontally aligned with the left edge of the yellow box undernearth.

[Image]

This paragraph is floated to the right (using a STYLE attribute) and the orange square image should appear to the left of the paragraph. This paragraph has a yellow background and no padding, margin or border. The left edge of this yellow box should be horizonally aligned with the right edge of the yellow box above.

[Image]

The first letter (a "T") of this paragraph should float left and be twice the font-size of the rest of the paragraph, as well as bold, with a content width of 1.5em and a background-color of silver. The top of the big letter "T" should be vertically aligned with the top of the first line of this paragraph. This is commonly known as "drop-cap".



This paragraph should be floated to the right, sort of like a 'sidebar' in a magazine article. Its width is 20em so the box should not be reformatted when the size of the viewport is changed (e.g. when the window is resized). The background color of the element is yellow, and there should be a 3px solid red border outside a 5px wide padding. Also, the element has a 10px wide margin around it where the blue background of the paragraph in the normal flow should shine through.

This paragraph is not floating. If there is enough room, the textual content of the paragraph should appear on the left side of the yellow "sidebar" on the right. The content of this element should flow around the floated element. However, the floated element may or may not be obscured by the blue background of this element, as the specification does not say which is drawn "on top." Even if the floated element is obscured, it still forces the content of this element to flow around it. If the floated element is not obscured, then the blue rectangle of this paragraph should extend 10px above and to the right of the sidebar's red border, due to the margin styles set for the floated element.



This paragraph is placed inside a DIV element which is floated to the right. The width of the DIV element is 20em. The background is yellow and there is a 5px padding, a 10px margin and no border. Since it is floated, the yellow box should be rendered on top of the background and borders of adjacent non-floated elements. To the left of this yellow box there should be a short paragraph with a blue background and a red border. The yellow box should be rendered on top of the bottom red border. I.e., the bottom red border will appear broken where it's overlaid by the yellow rectangle.

See description in the box on the right side



This paragraph is inside a DIV which is floated left. Its background is blue and the width is 25%.

This paragraph is inside a DIV which is floated right. Its background is yellow and the width is 25%.

This paragraph should appear between a blue box (on the left) and a yellow box (on the right).



See description in the box on the left side.

This paragraph is inside a DIV which is floated left. The background of the DIV element is blue and its width is 75%. This text should all be inside the blue rectangle. The blue DIV element has another DIV element as a child. It has a yellow background color and is floated to the right. Since it is a child of the blue DIV, the yellow DIV should appear inside the blue rectangle. Due to it being floated to the right and having a 10px right margin, the yellow rectange should have a 10px blue stripe on its right side.




[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5525d.htm ##### CSS1 Test Suite: 5.5.25 float

CSS1 Test Suite: 5.5.25 float


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align:  justify;}DIV.yellow, DIV.blue, DIV.red, DIV.green { width: 60px; padding: 20px; margin: 10px; border: 20px solid black; float: left; text-align: center; font-family: "Times New Roman",Times,serif;}DIV.yellow {margin-left: 0px; background: yellow; color: black;}DIV.blue {background: blue; color: white;}DIV.red {background: red; color: black;}DIV.green {background: green; color: white;}DIV.below {clear: both;}TABLE {margin: 20px 0px;}

The four floating DIV elements below should appear next to each other horizontally. The table at the bottom of this page indicates how the DIV elements should be laid out horizontally. They should align with each other.

Yellow

Blue

Red

Green

;
TABLE Testing Section
 

The four floating DIV elements below should appear next to each other horizontally. The table at the bottom of this page indicates how the DIV elements should be laid out horizontally. They should align with each other.

Yellow

Blue

Red

Green

;

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5526.htm ##### CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {clear: left;}.two {clear: right;}.three {clear: both;}.four {clear: none;}

[Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window.


[Image]

This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it.


[Image]

This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it.


[Image] [Image]

This paragraph should appear below the two tall orange rectangles, and not flow between them.

[Image] [Image]

This paragraph should be between both tall orange rectangles.


TABLE Testing Section
 [Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window.


[Image]

This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it.


[Image]

This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it.


[Image] [Image]

This paragraph should appear below the two tall orange rectangles, and not flow between them.

[Image] [Image]

This paragraph should be between both tall orange rectangles.



[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5526b.htm ##### CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P { margin: 0; padding: 0; text-align:  justify;}DIV.menu {float: left; clear: left; width: 11em;          margin: 0; margin-bottom: 10px; padding: 0.5em;}DIV.menu H1 {font-size: 1.2em; margin: 0; padding: 0;}DIV.menu UL {margin: 0.2em 0.3em 0.2em 1em; padding: 0;}DIV.article {padding: 0.5em; margin: 0; margin-left: 14em; margin-right: 2em;             color: black; background: yellow; clear: none;}

The 'clear' property

This page has two floating "menus" on the side; one has a green background, and the other a blue background. Due to settings on the 'float' and 'clear' properties, the two menus should appear on the left side of the page, the blue below the green. There should be a 10px gap between the two menus. There should also be a 10px gap between the top menu and the top of the page.

The top of the yellow rectangle (to which this paragraph belongs) should be vertically aligned with the top of the green rectangle.

TABLE Testing Section
 

The 'clear' property

This page has two floating "menus" on the side; one has a green background, and the other a blue background. Due to settings on the 'float' and 'clear' properties, the two menus should appear on the left side of the page, the blue below the green. There should be a 10px gap between the two menus. There should also be a 10px gap between the top menu and the top of the page.

The top of the yellow rectangle (to which this paragraph belongs) should be vertically aligned with the top of the green rectangle.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec5526c.htm ##### CSS1 Test Suite: 5.5.26 clear

CSS1 Test Suite: 5.5.26 clear


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the linked page are:

html { font: 10px/1 Verdana, sans-serif;background-color: blue; color: white; }body { margin: 1.5em; border: .5em solid black;padding: 0; width: 48em; background-color: white; }dl { margin: 0; border: 0; padding: .5em; }dt { background-color: rgb(204,0,0); margin: 0; padding: 1em;width: 10.638%; /* refers to parent element's width of 47em. = 5em or 50px */height: 28em; border: .5em solid black; float: left; }dd { float: right; margin: 0 0 0 1em; border: 1em solid black;padding: 1em; width: 34em; height: 27em; }ul { margin: 0; border: 0; padding: 0; }li { display: block; /* i.e., suppress marker */ color: black;height: 9em; width: 5em; margin: 0; border: .5em solid black;padding: 1em; float: left; background-color: #FC0; }#bar { background-color: black; color: white; width: 41.17%; /* = 14em */border: 0; margin: 0 1em; } #baz { margin: 1em 0; border: 0; padding: 1em; width: 10em;height: 10em; background-color: black; color: white; }form { margin: 0; display: inline; }p { margin: 0; }form p { line-height: 1.9; }blockquote { margin: 1em 1em 1em 2em; border-width: 1em 1.5em 2em .5em;border-style: solid; border-color: black; padding: 1em 0; width: 5em;height: 9em; float: left; background-color: #FC0; color: black; }address { font-style: normal; }h1 { background-color: black; color: white; float: left; margin: 1em 0;border: 0; padding: 1em; width: 10em; height: 10em; font-weight: normal;font-size: 1em; }

The test itself is on a separate page.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec56.htm ##### CSS1 Test Suite: 5.6 Classification Properties

CSS1 Test Suite: 5.6 Classification Properties


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec561.htm ##### CSS1 Test Suite: 5.6.1 display

CSS1 Test Suite: 5.6.1 display


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {display: block;}.two {display: inline;}.three {display: list-item; list-style-type: square; margin-left: 3em;}.four {display: none; color: red;}I {display: block;}

This sentence should be a block-level element.

This sentence should be part of an inline element, as are the next three.

This sentence and the next two are part of a second inline element. They should therefore appear, along with the sentence above, to be all one paragraph which is four sentences long. If this is not the case, then the keyword inline is being ignored.

This sentence should be treated as a list-item, and therefore be rendered however this user agent displays list items (if list-style-type is supported, there will be a square for the item marker). A 3em left margin has been applied in order to ensure that there is space for the list-item marker.

The next paragraph should be invisible (if it's visible, you'll see red text).

This paragraph should be invisible.

There should be no text after the colon: fnord.

The italicized text in this paragraph should be a block-level element.

TABLE Testing Section
 

This sentence should be a block-level element.

This sentence should be part of an inline element, as are the next three.

This sentence and the next two are part of a second inline element. They should therefore appear, along with the sentence above, to be all one paragraph which is four sentences long. If this is not the case, then the keyword inline is being ignored.

This sentence should be treated as a list-item, and therefore be rendered however this user agent displays list items (if list-style-type is supported, there will be a square for the item marker). A 3em left margin has been applied in order to ensure that there is space for the list-item marker.

The next paragraph should be invisible (if it's visible, you'll see red text).

This paragraph should be invisible.

There should be no text after the colon: fnord.

The italicized text in this paragraph should be a block-level element.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec562.htm ##### CSS1 Test Suite: 5.6.2 white-space

CSS1 Test Suite: 5.6.2 white-space


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {white-space: pre;}.two {white-space: nowrap;}.three {white-space: normal;}

This sentence should show extra space where there would ordinarily not be any. There should also be preservation of returns as this sentence very clearly demonstrates.

This sentence should not word-wrap, no matter how long the sentence is, as it has been set to nowrap and that should have the obvious effect.

This sentence should show extra space, except in the second half.

TABLE Testing Section
 

This sentence should show extra space where there would ordinarily not be any. There should also be preservation of returns as this sentence very clearly demonstrates.

This sentence should not word-wrap, no matter how long the sentence is, as it has been set to nowrap and that should have the obvious effect.

This sentence should show extra space, except in the second half.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec563.htm ##### CSS1 Test Suite: 5.6.3 list-style-type

CSS1 Test Suite: 5.6.3 list-style-type


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-type: disc;}.two {list-style-type: circle;}.three {list-style-type: square;}.four {list-style-type: lower-roman;}.five {list-style-type: upper-roman;}.six {list-style-type: lower-alpha;}.seven {list-style-type: upper-alpha;}.eight {list-style-type: decimal;}.nine {list-style-type: none;}

  1. This list...
  2. ...should feature...
  3. ...lowercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase letters for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase letters for each item.
  1. This list should feature...
  2. ...letters for each item...
  3. ...except this one.
TABLE Testing Section
 
  • This list...
  • ...should feature...
  • ...discs for each item.
  • This list...
  • ...should feature...
  • ...circles for each item.
  • This list...
  • ...should feature...
  • ...squares for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase Roman numerals for each item.
  1. This list...
  2. ...should feature...
  3. ...lowercase letters for each item.
  1. This list...
  2. ...should feature...
  3. ...uppercase letters for each item.
  1. This list should feature...
  2. ...letters for each item...
  3. ...except this one.
  • This list...
  • ...should feature...
  • ...nothing for each item.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec564.htm ##### CSS1 Test Suite: 5.6.4 list-style-image

CSS1 Test Suite: 5.6.4 list-style-image


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-image: url(orancirc.gif);}.two {list-style-image: none;}

TABLE Testing Section
 
  • This list...
  • ...should feature...
  • ...orange circle images for each item.
  • This list...
  • ...should feature...
  • ...standard list markers for each item.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec565.htm ##### CSS1 Test Suite: 5.6.5 list-style-position

CSS1 Test Suite: 5.6.5 list-style-position


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style-position: outside;}.two {list-style-position: inside;}

TABLE Testing Section
 
  • The text in this item should behave as expected; that is, it should line up with itself on the left margin, leaving blank space beneath the bullet.
  • The text in this item should not behave as expected; that is, it should line up with the bullet on the left margin, leaving no blank space beneath the bullet.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec566.htm ##### CSS1 Test Suite: 5.6.6 list-style

CSS1 Test Suite: 5.6.6 list-style


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.one {list-style: upper-alpha inside;}.two {list-style: url(oransqr.gif) disc outside;}

TABLE Testing Section
 
  • The text in this item should not behave as expected; that is, it should line up with the capital-A on the left margin, leaving no blank space beneath the capital-A.
  • The text in this item have an orange square for its bullet; failing that, a disc. Also, the bullet should be outside the text block, as the list has been set to 'outside'.

[Previous] [Next] [Section] [Contents] [Specification]
+##### sec60.htm ##### CSS1 Test Suite: 6.0 Units

CSS1 Test Suite: 6.0 Units


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec61.htm ##### CSS1 Test Suite: 6.1 Length Units

CSS1 Test Suite: 6.1 Length Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero {margin-left: 0;}.one {margin-left: 3em;}.two {margin-left: 3ex;}.three {margin-left: 36px;}.four {margin-left: 0.5in;}.five {margin-left: 1.27cm;}.six {margin-left: 12.7mm;}.seven {margin-left: 36pt;}.eight {margin-left: 3pc;}.nine {margin-left: +3pc;}.ten {font-size: 40px; border-left: 1ex solid purple; background-color: aqua;}

This paragraph has no left margin. The following paragraphs have all been given a left margin and their left (outer) edges should therefore be appropriately shifted to the right of this paragraph's left edge.

This paragraph should have a left margin of 3em.

This paragraph should have a left margin of 3ex.

This paragraph should have a left margin of 36 pixels.

This paragraph should have a left margin of half an inch.

This paragraph should have a left margin of 1.27cm.

This paragraph should have a left margin of 12.7mm.

This paragraph should have a left margin of 36 points.

This paragraph should have a left margin of 3 picas.

This paragraph should have a left margin of 3 picas (the plus sign should make no difference).

This element has a font-size of 40px and a border-left of 1ex solid purple. This should make the left border the same number of pixels as the lower-case 'x' in this element's font, as well as solid purple.

TABLE Testing Section
 

This paragraph has no left margin. The following paragraphs have all been given a left margin and their left (outer) edges should therefore be appropriately shifted to the right of this paragraph's left edge.

This paragraph should have a left margin of 3em.

This paragraph should have a left margin of 3ex.

This paragraph should have a left margin of 36 pixels.

This paragraph should have a left margin of half an inch.

This paragraph should have a left margin of 1.27cm.

This paragraph should have a left margin of 12.7mm.

This paragraph should have a left margin of 36 points.

This paragraph should have a left margin of 3 picas.

This paragraph should have a left margin of 3 picas (the plus sign should make no difference).

This element has a font-size of 40px and a border-left of 1ex solid purple. This should make the left border the same number of pixels as the lower-case 'x' in this element's font, as well as solid purple.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec62.htm ##### CSS1 Test Suite: 6.2 Percentage Units

CSS1 Test Suite: 6.2 Percentage Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

.zero { background: yellow }.one { margin-left: 25%; margin-right: 25%; background: white }.two { margin-left: 50%; margin-right: 0%; background: white }.three {margin-left: 25%;}

This paragraph should be centered within its yellow containing block and its width should be half of the containing block.

This paragraph should be right-aligned within its yellow containing block and its width should be half of the containing block.

This paragraph should have a left margin of 25% the width of its parent element, which should require some extra text in order to test effectively.

TABLE Testing Section
 

This paragraph should be centered within its yellow containing block and its width should be half of the containing block.

This paragraph should be right-aligned within its yellow containing block and its width should be half of the containing block.

This paragraph should have a left margin of 25% the width of its parent element, which should require some extra text in order to test effectively.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec63.htm ##### CSS1 Test Suite: 6.3 Color Units

CSS1 Test Suite: 6.3 Color Units


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

BODY {color: black;}.one {color: #080;}.two {color: #008000;}.three {color: rgb(0,128,0);}.four {color: rgb(0%,50%,0%);}.five {color: rgb(0.0%,50.0%,0.0%);}.six {color: green;}.seven {color: invalidValue;}.eight {color: rgb(0,128,1280);}.nine {color: rgb(0,128,255);}.ten {color: rgb(50%,-500%,60%);}.eleven {color: rgb(50%,0%,60%);}

This sentence should be black.

This sentence should be green, although slightly different from those that follow.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be black, because the value given for class .seven is invalid.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be black.

This sentence should be a slightly different green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

TABLE Testing Section
 

This sentence should be black.

This sentence should be green, although slightly different from those that follow.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be green.

This sentence should be black, because the value given for class .seven is invalid.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of blue-green which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the next paragraph.

This sentence should be a shade of purple which, on a typical RGB computer display, exactly matches the previous paragraph.

This sentence should be black.

This sentence should be a slightly different green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.

This sentence should be green, and used the style attribute.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec64.htm ##### CSS1 Test Suite: 6.4 URLs

CSS1 Test Suite: 6.4 URLs


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

<LINK rel="stylesheet" type="text/css" media="screen" href="folder/sec64.css">@import url(folder/sec642.css);BODY {background: url(bg.gif);}

This page should have a green grid pattern as its background.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

TABLE Testing Section
 

This page should have a green grid pattern as its background.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.

This paragraph should have a white background, but NO image should appear in the background. If an image, in this case a red square-- or, indeed, any red at all-- is seen there, then the browser has incorrectly interpreted a URL in relation to the document's URL, not the stylesheet's URL.


[Previous] [Next] [Section] [Contents] [Specification]
+##### sec70.htm ##### CSS1 Test Suite: 7.0 CSS1 Conformance

CSS1 Test Suite: 7.0 CSS1 Conformance


[Previous] [Next] [Contents] [Specification]

In this section:


[Previous] [Next] [Contents] [Specification]
+##### sec71.htm ##### CSS1 Test Suite: 7.1 Forward-Compatible Parsing

CSS1 Test Suite: 7.1 Forward-Compatible Parsing


[Previous] [Next] [Section] [Contents] [Specification]

The style declarations which apply to the text below are:

P.one {color: green; rotation: 70deg;}P.oneb {color: green;}P.oneb {color: invalidValue;}P.two {background-color: inherit;}H1 + P.three {color: blue;}P.four + H1 {color: red;}P.five {background-color: "red";}P.sixa {border-width: medium; border-style: solid;}P.sixb {border-width: funny; border-style: solid;}P.sixc {border-width: 50zu; border-style: solid;}P.sixd {border-width: px; border-style: solid;}@three-dee { @background-lighting {  azimuth: 30deg;  elevation: 190deg;  } P.seven { color: red } }P.eight {COLOR: GREEN;}OL:wait {color: maroon;}P.ten:first-child {color: maroon;}UL:lang(fr) {color: gray;}BLOCKQUOTE[href] {color: navy;}ACRONYM[href="foo"] {color: purple;}ADDRESS[href~="foo"] {color: purple;}SPAN[lang|="fr"] {color: #c37;}@media tty { H1 {color: red;} P.sixteen {color: red;} }@three-dee { P.seventeen {color: red } }P.eighteena {text-decoration: underline overline line-through diagonal;            font: bold highlighted 100% sans-serif;}P.eighteenb {text-decoration: underline overline line-through diagonal;            font: bold highlighted 100% serif;}EM, P.nineteena ! EM, STRONG {font-size: 200%; }// UL.nineteenb,P.nineteenb {color: red;}P.twentya {rotation-code: "}"; color: blue;} P.twentyb {rotation-code: "\"}\""; color: green;}P.twentyonea {rotation-code: '}'; color: purple;} P.twentyoneb {rotation-code: '\'}\''; color: green;}P.twentytwo { type-display: @threedee {rotation-code: '}';}; color: green; }P.twentythree {text-indent: 0.5in;} color: maroonP.twentyfour {color: red;}

This paragraph should be green, because only the rotation should be ignored.

This paragraph should be green, since error-checking should be done before calculating specificity.

In CSS1-only conforming agents, this paragraph should not have a solid gray background because, in CSS1, inherit is an invalid keyword. If the agent supports CSS2, then a gray background (not a grid) will be inherited in the first half of the document. In the second half (the table-testing section), the element will inherit a transparent background, thus allowing the grid to shine through.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should have a white background, since keywords cannot be quoted.

This paragraph should have a medium-width border around it (the same as the next three paragraphs). This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous and the next two paragraphs), because the border-width is invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the next and the previous two paragraphs), because the border-width units are invalid, and therefore the border-width should be ignored. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous three paragraphs), because the border-width does not have any value to go with its pixel unit, and is therefore invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

This paragraph should be green. CSS is case-insensitive, unless required to be case sensitive due to interaction with other standards (e.g., font names or URLs.)

  1. This ordered list item should be black, because the declaration has an invalid pseudo-class selector.

This paragraph should be black, because, in CSS1, :first-child is an invalid pseudo-class, and in CSS2, this paragraph is not the first child.

This blockquote should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This acronym should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This address should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This span should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule. However, it is valid in CSS2, so if this is being viewed on a tty browser that supports CSS2, it should be red.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the next paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the previous paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal size because the selector is invalid. The emphasized text and the strong text within it should also be normal size, since the entire ruleset should be skipped (since in some future version of CSS, there could be an operator within the selector that has higher precedence than a comma).

This paragraph should be black, because the line before the declaration is not a comment and therefore the selector for P.nineteenb is invalid.

This paragraph should be blue, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be purple, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be indented half an inch, but it should not be maroon. It should be black.

This paragraph should be black, because the color declaration after the previous ruleset should be considered part of the selector for this ruleset, and this ruleset therefore has an invalid selector and should not be applied.

TABLE Testing Section
 

This paragraph should be green, because only the rotation should be ignored.

This paragraph should be green, since error-checking should be done before calculating specificity.

In CSS1-only conforming agents, this paragraph should not have a solid gray background because, in CSS1, inherit is an invalid keyword. If the agent supports CSS2, then a gray background (not a grid) will be inherited in the first half of the document. In the second half (the table-testing section), the element will inherit a transparent background, thus allowing the grid to shine through.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should be black, since in CSS1, the selector is invalid, and in CSS2, it does not apply.

This paragraph should have a white background, since keywords cannot be quoted.

This paragraph should have a medium-width border around it (the same as the next three paragraphs). This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous and the next two paragraphs), because the border-width is invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the next and the previous two paragraphs), because the border-width units are invalid, and therefore the border-width should be ignored. This should cause the user agent to use the default value of 'medium'.

This paragraph should have a medium-width border around it (the same as the previous three paragraphs), because the border-width does not have any value to go with its pixel unit, and is therefore invalid. This should cause the user agent to use the default value of 'medium'.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

This paragraph should be green. CSS is case-insensitive, unless required to be case sensitive due to interaction with other standards (e.g., font names or URLs.)

  1. This ordered list item should be black, because the declaration has an invalid pseudo-class selector.

This paragraph should be black, because, in CSS1, :first-child is an invalid pseudo-class, and in CSS2, this paragraph is not the first child.

  • This unordered list item should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.
This blockquote should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This acronym should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This address should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This span should be black, because, according to CSS1, the selector is invalid, and according to CSS2, the selector should not apply.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule. However, it is valid in CSS2, so if this is being viewed on a tty browser that supports CSS2, it should be red.

This paragraph should be black, because the style declaration that applies to it is within an invalid at-rule.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the next paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal (that is, it should not be underlined, overlined, stricken, or bold), because diagonal is not a valid keyword, making the text-decoration invalid. In addition, highlighted is not a valid part of the font property, making it invalid. Therefore, this paragraph's font should be the UA default, and match the previous paragraph. If this is not the case, then the font declaration is being improperly parsed.

The text of this paragraph should be normal size because the selector is invalid. The emphasized text and the strong text within it should also be normal size, since the entire ruleset should be skipped (since in some future version of CSS, there could be an operator within the selector that has higher precedence than a comma).

This paragraph should be black, because the line before the declaration is not a comment and therefore the selector for P.nineteenb is invalid.

This paragraph should be blue, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be purple, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be green, because only the first declaration is invalid.

This paragraph should be indented half an inch, but it should not be maroon. It should be black.

This paragraph should be black, because the color declaration after the previous ruleset should be considered part of the selector for this ruleset, and this ruleset therefore has an invalid selector and should not be applied.


[Previous] [Next] [Section] [Contents] [Specification]
diff --git a/css2/Globe.ani b/css2/Globe.ani new file mode 100755 index 0000000..3d43df8 Binary files /dev/null and b/css2/Globe.ani differ diff --git a/css2/base.css b/css2/base.css new file mode 100644 index 0000000..b97b01c --- /dev/null +++ b/css2/base.css @@ -0,0 +1 @@ +body {color: black; background: #CCCCCC url(pix/basebg.gif);} a:link {color: blue;} a:visited {color: #006600;} \ No newline at end of file diff --git a/css2/folder/lastlink.css b/css2/folder/lastlink.css new file mode 100644 index 0000000..eed92df --- /dev/null +++ b/css2/folder/lastlink.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(lastlinkimport.css); @import url(lastlinkimportmediascreen.css) screen; @import url(lastlinkimportmediatty.css) tty; /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .folderlastlinkimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/lastlinkimport.css b/css2/folder/lastlinkimport.css new file mode 100644 index 0000000..e2e7eea --- /dev/null +++ b/css2/folder/lastlinkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlastlinkimportimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/link.css b/css2/folder/link.css new file mode 100644 index 0000000..877240c --- /dev/null +++ b/css2/folder/link.css @@ -0,0 +1 @@ +/*Import Test File*/ @import url(linkimport.css); @import url(linkimportmediascreen.css) screen; @import url(linkimportmediatty.css) tty; /* This line rests any browsers that got confused by the @import lines */ .ignored { color: black; } .folderlink { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/linkimport.css b/css2/folder/linkimport.css new file mode 100644 index 0000000..90b167b --- /dev/null +++ b/css2/folder/linkimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/linkmediaall.css b/css2/folder/linkmediaall.css new file mode 100644 index 0000000..76c9f1d --- /dev/null +++ b/css2/folder/linkmediaall.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediaall { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/linkmediascreen.css b/css2/folder/linkmediascreen.css new file mode 100644 index 0000000..755dd2c --- /dev/null +++ b/css2/folder/linkmediascreen.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediascreen { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/linkmediascreenprojection.css b/css2/folder/linkmediascreenprojection.css new file mode 100644 index 0000000..ed72e17 --- /dev/null +++ b/css2/folder/linkmediascreenprojection.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediascreenprojection { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/folder/linkmediatty.css b/css2/folder/linkmediatty.css new file mode 100644 index 0000000..55ee0be --- /dev/null +++ b/css2/folder/linkmediatty.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderlinkmediatty { color: red; background: yellow none; } \ No newline at end of file diff --git a/css2/folder/sec64.css b/css2/folder/sec64.css new file mode 100644 index 0000000..dfe9e57 --- /dev/null +++ b/css2/folder/sec64.css @@ -0,0 +1 @@ +P.one {background: white url(redsqr.gif) center no-repeat;} \ No newline at end of file diff --git a/css2/folder/sec642.css b/css2/folder/sec642.css new file mode 100644 index 0000000..614c3a9 --- /dev/null +++ b/css2/folder/sec642.css @@ -0,0 +1 @@ +P.two {background: white url(redsqr.gif) center no-repeat;} \ No newline at end of file diff --git a/css2/folder/styleimport.css b/css2/folder/styleimport.css new file mode 100644 index 0000000..b61c2c1 --- /dev/null +++ b/css2/folder/styleimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .folderstyleimport { font-weight: bold; color: green; background: silver none; } \ No newline at end of file diff --git a/css2/index.html b/css2/index.html new file mode 100644 index 0000000..66df9a4 --- /dev/null +++ b/css2/index.html @@ -0,0 +1 @@ + CSS2 Test Suite: Index

CSS2 Test Suite: Prototypical Pages

\ No newline at end of file diff --git a/css2/pagedex.html b/css2/pagedex.html new file mode 100644 index 0000000..d506f5c --- /dev/null +++ b/css2/pagedex.html @@ -0,0 +1 @@ +5.2-Selector Syntax 5.2.1-Grouping 5.3-Universal Selector 5.4-Type Selectors 5.5-Descendant Selectors 5.6-Child Selectors 5.7-Adjacent Sibling Selectors 5.8.1-Attribute Selectors 5.8.3-Class Selectors 5.9-ID Selectors 5.10-Pseudo-Class Combinations 5.11.1-:first-child 5.11.2-:link and :visited 5.11.3-:active, :hover, and :focus 5.11.4-:lang 5.12.1-:first-line 5.12.2-:first-letter 5.12.3-:before and :after 6.2.1-inherit 6.3-@import 6.4.1-Cascading Order 6.4.2-!important rules 6.4.3-Calculating specificity 6.4.4-Precedence of non-CSS hints 8.2-Margins, padding, borders 8.3-margin-top 8.3-margin-right 8.3-margin-bottom 8.3-margin-left 8.3-margin 8.4-padding-top 8.4-padding-right 8.4-padding-bottom 8.4-padding-left 8.4-padding 8.5.1-border-top-width 8.5.1-border-right-width 8.5.1-border-bottom-width 8.5.1-border-left-width 8.5.1-border-width 8.5.2-border-top-color 8.5.2-border-right-color 8.5.2-border-bottom-color 8.5.2-border-left-color 8.5.2-border-color 8.5.3-border-top-style 8.5.3-border-right-style 8.5.3-border-bottom-style 8.5.3-border-left-style 8.5.3-border-style 8.5.4-border-top 8.5.4-border-right 8.5.4-border-bottom 8.5.4-border-left 8.5.4-border 9.2.5-display 9.3.1-position 9.3.2-top 9.3.2-right 9.3.2-bottom 9.3.2-left 9.5.1-float 9.5.2-clear 9.8.2-Relative Positioning 9.8.3-Floating a Box 9.8.4-Absolute Positioning 9.9.1-z-index 9.10-direction 9.10-unicode-bidi 10.2-width 10.3.1-Computing widths and margins: inline, non-replaced elements 10.3.2-Computing widths and margins: inline, replaced elements 10.3.3-Computing widths and margins: block-level, non-replaced elements in normal flow 10.3.4-Computing widths and margins: block-level, replaced elements in normal flow 10.3.5-Computing widths and margins: floating, non-replaced elements 10.3.6-Computing widths and margins: floating, replaced elements 10.3.7-Computing widths and margins: absolutely positioned, non-replaced elements 10.3.8-Computing widths and margins: absolutely positioned, replaced elements 10.4-min-width 10.4-max-width 10.5-height 10.6.1-Computing heights and margins: inline, non-replaced elements 10.6.2-Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements 10.6.3-Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements 10.6.4-Computing heights and margins: absolutely positioned, non-replaced elements 10.6.5-Computing heights and margins: absolutely positioned, replaced elements 10.7-min-height 10.7-max-height 10.8-line-height 10.8-vertical-align 11.1.1-overflow 11.1.2-clip 11.2-visibility 12.1-:before and :after 12.2-content 12.4.1-quotes 12.5-counter-reset 12.5-counter-increment 12.6.1-marker-offset 12.6.2-list-style-type 12.6.2-list-style-image 12.6.2-list-style-position 12.6.2-list-style 14.1-color 14.2.1-background-color 14.2.1-background-image 14.2.1-background-repeat 14.2.1-background-attachment 14.2.1-background-position 14.2.1-background 15.2.2-font-family 15.2.3-font-style 15.2.3-font-variant 15.2.3-font-weight 15.2.3-font-stretch 15.2.4-font-size 15.2.4-font-size-adjust 15.2.5-font 16.1-text-indent 16.2-text-align 16.3.1-text-decoration 16.3.2-text-shadow 16.4-letter-spacing 16.4-word-spacing 16.5-text-transform 16.6-white-space 17.4.1-caption-side 17.5.2-table-layout 17.6-border-collapse 17.6.1-border-spacing 17.6.1-empty-cells 18.1-cursor 18.2-User preferences for colors 18.4-outline 18.4-outline-width 18.4-outline-style 18.4-outline-color \ No newline at end of file diff --git a/css2/pix/basebg.gif b/css2/pix/basebg.gif new file mode 100755 index 0000000..26604e6 Binary files /dev/null and b/css2/pix/basebg.gif differ diff --git a/css2/pix/bg.gif b/css2/pix/bg.gif new file mode 100755 index 0000000..a5cabb9 Binary files /dev/null and b/css2/pix/bg.gif differ diff --git a/css2/pix/crosshair.gif b/css2/pix/crosshair.gif new file mode 100755 index 0000000..0e87532 Binary files /dev/null and b/css2/pix/crosshair.gif differ diff --git a/css2/pix/crosshair2.gif b/css2/pix/crosshair2.gif new file mode 100755 index 0000000..5aebcc9 Binary files /dev/null and b/css2/pix/crosshair2.gif differ diff --git a/css2/pix/draftbg.gif b/css2/pix/draftbg.gif new file mode 100755 index 0000000..c8a3893 Binary files /dev/null and b/css2/pix/draftbg.gif differ diff --git a/css2/pix/hblank1.gif b/css2/pix/hblank1.gif new file mode 100755 index 0000000..2f862fb Binary files /dev/null and b/css2/pix/hblank1.gif differ diff --git a/css2/pix/hblank2.gif b/css2/pix/hblank2.gif new file mode 100755 index 0000000..d82a7d1 Binary files /dev/null and b/css2/pix/hblank2.gif differ diff --git a/css2/pix/horiz_description.gif b/css2/pix/horiz_description.gif new file mode 100755 index 0000000..2d9a4ff Binary files /dev/null and b/css2/pix/horiz_description.gif differ diff --git a/css2/pix/horiz_pixel_ruler.gif b/css2/pix/horiz_pixel_ruler.gif new file mode 100755 index 0000000..26ee74b Binary files /dev/null and b/css2/pix/horiz_pixel_ruler.gif differ diff --git a/css2/pix/num1.gif b/css2/pix/num1.gif new file mode 100755 index 0000000..307420e Binary files /dev/null and b/css2/pix/num1.gif differ diff --git a/css2/pix/num2.gif b/css2/pix/num2.gif new file mode 100755 index 0000000..0c6bf68 Binary files /dev/null and b/css2/pix/num2.gif differ diff --git a/css2/pix/num3.gif b/css2/pix/num3.gif new file mode 100755 index 0000000..8770b07 Binary files /dev/null and b/css2/pix/num3.gif differ diff --git a/css2/pix/num4.gif b/css2/pix/num4.gif new file mode 100755 index 0000000..c2e4065 Binary files /dev/null and b/css2/pix/num4.gif differ diff --git a/css2/pix/num5.gif b/css2/pix/num5.gif new file mode 100755 index 0000000..daf4a39 Binary files /dev/null and b/css2/pix/num5.gif differ diff --git a/css2/pix/num6.gif b/css2/pix/num6.gif new file mode 100755 index 0000000..c775128 Binary files /dev/null and b/css2/pix/num6.gif differ diff --git a/css2/pix/num7.gif b/css2/pix/num7.gif new file mode 100755 index 0000000..29e7b0e Binary files /dev/null and b/css2/pix/num7.gif differ diff --git a/css2/pix/num8.gif b/css2/pix/num8.gif new file mode 100755 index 0000000..70a5e38 Binary files /dev/null and b/css2/pix/num8.gif differ diff --git a/css2/pix/num9.gif b/css2/pix/num9.gif new file mode 100755 index 0000000..8341dd3 Binary files /dev/null and b/css2/pix/num9.gif differ diff --git a/css2/pix/orancirc.gif b/css2/pix/orancirc.gif new file mode 100755 index 0000000..6bdd68b Binary files /dev/null and b/css2/pix/orancirc.gif differ diff --git a/css2/pix/oransqr.gif b/css2/pix/oransqr.gif new file mode 100755 index 0000000..bea5f04 Binary files /dev/null and b/css2/pix/oransqr.gif differ diff --git a/css2/pix/redbig.gif b/css2/pix/redbig.gif new file mode 100755 index 0000000..7bf9a36 Binary files /dev/null and b/css2/pix/redbig.gif differ diff --git a/css2/pix/redsqr.gif b/css2/pix/redsqr.gif new file mode 100755 index 0000000..1af1c0e Binary files /dev/null and b/css2/pix/redsqr.gif differ diff --git a/css2/pix/redtall.gif b/css2/pix/redtall.gif new file mode 100755 index 0000000..aed2ed1 Binary files /dev/null and b/css2/pix/redtall.gif differ diff --git a/css2/pix/redwide.gif b/css2/pix/redwide.gif new file mode 100755 index 0000000..8f5adf0 Binary files /dev/null and b/css2/pix/redwide.gif differ diff --git a/css2/pix/smgr-bg.gif b/css2/pix/smgr-bg.gif new file mode 100755 index 0000000..a5cabb9 Binary files /dev/null and b/css2/pix/smgr-bg.gif differ diff --git a/css2/pix/test1.jpg b/css2/pix/test1.jpg new file mode 100755 index 0000000..ce5fd6e Binary files /dev/null and b/css2/pix/test1.jpg differ diff --git a/css2/pix/test2.jpg b/css2/pix/test2.jpg new file mode 100755 index 0000000..eaba586 Binary files /dev/null and b/css2/pix/test2.jpg differ diff --git a/css2/pix/vblank.gif b/css2/pix/vblank.gif new file mode 100755 index 0000000..332034b Binary files /dev/null and b/css2/pix/vblank.gif differ diff --git a/css2/pix/vertical-wave.gif b/css2/pix/vertical-wave.gif new file mode 100755 index 0000000..3a08555 Binary files /dev/null and b/css2/pix/vertical-wave.gif differ diff --git a/css2/pix/zind1.gif b/css2/pix/zind1.gif new file mode 100755 index 0000000..657562b Binary files /dev/null and b/css2/pix/zind1.gif differ diff --git a/css2/pix/zind2.gif b/css2/pix/zind2.gif new file mode 100755 index 0000000..770f7ba Binary files /dev/null and b/css2/pix/zind2.gif differ diff --git a/css2/pre-torchar.txt b/css2/pre-torchar.txt new file mode 100644 index 0000000..75041bc --- /dev/null +++ b/css2/pre-torchar.txt @@ -0,0 +1,8924 @@ +##### sec05-02.htm ##### + + + +5.2 Selector Syntax + + + + + + +

CSS2 Test Suite: 5.2 Selector Syntax

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1:first-line strong {color: red;}
+.cl2em {color: red;}
+.cl2+.cl3 {color: green;}
+.cl3  +  .cl4 {color: green;}
+
+
+

+[cl1] The emphasized text in the first line of this element should NOT be red, but the same color as the text in the element. +

+

+[cl2] The emphasized text in this element should NOT be red, but the same color as the text in the element. +

+

+[cl3] The text in this element should be green. +

+

+[cl4] The text in this element should be green. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-02-01.htm ##### + + + +5.2.1 Grouping + + + + + + +

CSS2 Test Suite: 5.2.1 Grouping

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1, .cl2, .cl3 {color: green;}
+.cl4, %cl5 {color: red;}
+
+
+

+[cl1] This sentence should be green. +

+

+[cl2] This sentence should be green. +

+

+[cl3] This sentence should be green. +

+

+[cl4] This sentence should be black. +

+

+[cl5] This sentence should be black. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-03.htm ##### + + + +5.3 Universal Selector + + + + + + +

CSS2 Test Suite: 5.3 Universal Selector

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
* {text-decoration: overline;}
+*.cl1 {color: purple;}
+.pastoral {color: green;}  /* omitted universal selector should be inferred */
+big {font-size: 133%; color: rgb(60%,60%,40%);}
+
+
+
+

+This is a paragraph element, which should be overlined. In fact, all of the elements on this page should be overlined. The word "all" in this paragraph may therefore appear to have two overlines, one consistent with the normal text and one slightly higher than that. (Other renderings may be possible.) However, the overline for the big element should be a dusky yellow no matter where it appears. +

+ +

This H3 should be black.

+

This H4 should be purple. [cl1]

+ +
+ +

[pastoral] An H3 element which should be green.

+

[pastoral] A paragraph element which should be green.

+
[pastoral] A blockquote element which should be green.
+
[pastoral] A PRE element which should be green.
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-04.htm ##### + + + +5.4 Type Selectors + + + + + + +

CSS2 Test Suite: 5.4 Type Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
H1 {font-family: sans-serif;}
+BODY {color: purple;}
+P {color: green;}
+H3 {color: navy;}
+LI {color: green;}
+
+
+

This H1 should be sans-serif.

+

+This paragraph should be green. +

+

This paragraph should be green despite having a class of 'tester'.

+

This H3 should be navy (dark blue).

+ +
    +
  1. This list item should be green...
  2. +
  3. ...as should this.
  4. +
+
This H5 should be purple.
+

+Another paragraph o' green. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-05.htm ##### + + + +5.5 Descendant Selectors + + + + + + +

CSS2 Test Suite: 5.5 Descendant Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
H1 EM {color: blue;}
+P STRONG {color: maroon;}
+DIV * P {color: green;}
+LI * STRONG {color: green;}
+
+
+

This headline is very important

+

The EM text in the previous H1 element should be blue.

+ +
+ +

+The strongly emphasized text in this paragraph should be maroon. +

+

+The strongly emphasized text in this paragraph should be maroon, despite being the child of an EM element. +

+

+In this paragraph we have an anchor which contains emphasized text, which in turn contains a citation, which in turn contains strongly emphasized text-- and that text should be maroon. Here goes: The W3C Web site contains a great resource called The CSS2 Test Suite (if we do say so ourselves). +

+ +
+ +
+This is anonymous text within a DIV, followed by: +
+...another DIV, with more anonymous text, followed by: +

...a paragraph, which should be green in color.

+
+
+ +
+ + + +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-06.htm ##### + + + +5.6 Child Selectors + + + + + + +

CSS2 Test Suite: 5.6 Child Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
BODY > P {color: green;}
+BODY>P.cl1 {font-family: sans-serif;}
+DIV OL > LI STRONG {color: green;}
+
+
+

+This paragraph, as a direct child of the BODY, should be green. +

+

+[cl1] This paragraph, as a direct child of the BODY and bearing a class of 'cl1', should be green and in a sans-serif font. +

+
+

+This paragraph, which is a child of a DIV, should NOT be green. +

+ +
    +
  1. The STRONG text in this list...
  2. +
  3. ...should be green, since it is a descendant of an LI which is a child of an OL element that's a descendant of the BODY.
  4. +
  5. This item contains an unordered list: +
      +
    • The STRONG text in this list...
    • +
    • ...should be green, since it is also a descendant of an LI which is a child of an OL element that's a descendant of the BODY.
    • +
    +
  6. +
  7. One more list item, just for good measure, containing strongly empahsized text which should be green. +
+

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-07.htm ##### + + + +5.7 Adjacent Sibling Selectors + + + + + + +

CSS2 Test Suite: 5.7 Adjacent Sibling Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
H3 + H4 {color: green;}
+UL+P {border-top: 3px solid green;}  /* lack of whitespace shouldn't matter */
+EM + STRONG {color: green;}
+H3.opener + P {border-top: 3px solid green;}
+
+
+

Here's an H3 element

+

This H4 should be green

+ +
+ +

Here's another H3 element

+this text is not in an element, and so shouldn't affect the adjacency selector; thus: +

This H4 should be green

+ +
+ +

Here's another H3 element

+

This text is contained within a paragraph element, and so should affect the adjacency selector; thus:

+

This H4 should NOT be green

+ +
+ + +

+This paragraph, since it follows a UL element, should have a three-pixel green top border. +

+

+Within this paragraph, there is emphasized text which contains strongly emphasized text which should NOT be green, as well as strongly emphasized text which should be green. +

+ +
+ +

This is an H3 with a class of "opener".

+

+This paragraph should have a three-pixel solid green top border. +

+

+This paragraph should have no border. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-08-01.htm ##### + + + +5.8.1 Attribute Selectors + + + + + + + +

CSS2 Test Suite: 5.8.1 Attribute Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P[class] {color: purple;}
+P[class="one"] {color: green;}
+P[class = "one"] {text-decoration: underline;}
+P[class~="two"] {color: olive;}
+P[class ~= "two"] {text-decoration: overline;}
+P[class|="three"] {color: green;}
+P[class |= "three"] {text-decoration: underline;}
+P[class|="give"] {color: green;}
+P[class~="give"][class~="generously"] {color: red;}
+P[lang|="en"] {color: green;}
+P[lang |= "de"] {color: green;}
+A[HREF] {color: purple;}
+A[HREF="http://www.erehwon.zzz/"] {color: green;}
+A[NAME="hello"] {color: green;}
+P[class="null"] {color: yellow; background: red; font-weight: bold;}
+     /*  catch broken forward-compatible parsing */</STYLE>
+
+
+
+

+This is a paragraph, and should not be green. +

+

+This is a paragraph with a class of 'test', and should be purple. +

+

+This is a paragraph with a class of 'one', and should be green and underlined. +

+

+This is a paragraph with a class of 'one step forward', and should NOT be green (but purple instead), nor should it be underlined. +

+

+This is a paragraph with a class of 'two steps back', and should be olive and overlined. +

+

+This is a paragraph with a class of 'one two three', and should be olive and overlined. +

+

+This is a paragraph with a class of 'world war two', and should be olive and overlined. +

+

+This is a paragraph with a class of 'three-blind-mice', and should be green and underlined. +

+

+This is a paragraph with a class of 'bakers-three', and should NOT be green (but purple instead), nor should it be underlined. +

+

+This is a paragraph with a class of 'give me liberty', and should be green. If it is red, then it has inappropriately matched a rule which contains the classes 'give' and 'generously'; if it is black, it has not matched any attribute selector rules. If it is purple, it has matched the attribute selector [class] but not any of the value-related selectors. +

+

+This is a paragraph with a LANG of 'en', and should be green. +

+

+This is a paragraph with a LANG of 'en-au', and should be green, mate. +

+

+This is a paragraph with a LANG of 'de-test', and should be green, ja? +

+

+The following hyperlinks should have the color indicated for each: +

+ +

+The text between the dashes-- you know, this stuff here-- should be green, as it is contained by an anchor with a NAME of "hello". +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-08-03.htm ##### + + + +5.8.3 Class Selectors + + + + + + +

CSS2 Test Suite: 5.8.3 Class Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.pastoral {color: green;}
+P.cl0 {color: green;}
+P.give.liberty {color: blue; border: 2px solid red; background: white;}
+
+
+

An H3 element which should NOT be green.

+

A paragraph element which should NOT be green.

+
A blockquote element which should NOT be green.
+
A PRE element which should NOT be green.
+ +
+ +

[pastoral] An H3 element which should be green.

+

[pastoral] A paragraph element which should be green.

+
[pastoral] A blockquote element which should be green.
+
[pastoral] A PRE element which should be green.
+ +
+ +

[cl0] An H3 element which should NOT be green.

+

[cl0] A paragraph which should be green.

+
[cl0] A blockquote element which should NOT be green.
+
[cl0] A PRE element which should NOT be green.
+ +
+ +

+This is a paragraph with a class of 'give me liberty', and should be red (border), white (background), and blue (foreground). +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-09.htm ##### + + + +5.9 ID Selectors + + + + + + +

CSS2 Test Suite: 5.9 ID Selectors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
#one {color: green;}
+#1 {color: red;}
+#id1 {color: green;}
+P#id2 {color: blue;}
+P#id3 {color: purple;}
+
+
+

+This sentence should be green. +

+

+[1] This sentence should be black, not red-- ID selectors cannot begin with digits in CSS1. +

+

+[id1] This sentence should be green. +

+

+[id2] This paragraph should be blue. +

+
[id2] This sentence should NOT be blue.
+
+
[id3] This sentence should be black.
+
+ +

+[id11] This paragraph should be black. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-10.htm ##### + + + +5.10 Pseudo-Class Combinations + + + + + + +

CSS2 Test Suite: 5.10 Pseudo-Class Combinations

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 a:hover {background-color: yellow; color: red;}
+.cl2 a:link:hover {background-color: yellow; color: red;}
+.cl3 a:hover:link {background-color: yellow; color: red;}
+.cl4 a:visited:hover {background-color: yellow; color: red;}
+.cl5 a:hover:visited {background-color: yellow; color: red;}
+.cl6 :link:hover {background-color: yellow; color: red;}
+.cl7 :hover:link {background-color: yellow; color: red;}
+.cl8 :visited:hover {background-color: yellow; color: red;}
+.cl9 :hover:visited {background-color: yellow; color: red;}
+.cl10 a:active {background-color: yellow; color: green;}
+.cl11 a:link:active {background-color: yellow; color: green;}
+.cl12 a:active:link {background-color: yellow; color: green;}
+.cl13 a:visited:active {background-color: yellow; color: green;}
+.cl14 a:active:visited {background-color: yellow; color: green;}
+.cl15 :link:active {background-color: yellow; color: green;}
+.cl16 :active:link {background-color: yellow; color: green;}
+.cl17 :visited:active {background-color: yellow; color: green;}
+.cl18 :active:visited {background-color: yellow; color: green;}
+
+
+
+

+Note: Before beginning, ensure that this link has been visited, and this link has not. +

+ +

[cl1] You should see hover effects on both these links: +link, +visited +

+ +

[cl2] You should see hover effects on only the "link": +link, +visited +

+ +

[cl3] You should see hover effects on only the "link": +link, +visited +

+ +

[cl4] You should see hover effects on only the "visited": +link, +visited +

+ +

[cl5] You should see hover effects on only the "visited": +link, +visited +

+ +

[cl6] You should see hover effects on only the "link": +link, +visited +

+ +

[cl7] You should see hover effects on only the "link": +link, +visited +

+ +

[cl8] You should see hover effects on only the "visited": +link, +visited +

+ +

[cl9] You should see hover effects on only the "visited": +link, +visited +

+ +
+ +

[cl10] You should see active effects on both these links: +link, +visited +

+ +

[cl11] You should see active effects on only the "link": +link, +visited +

+ +

[cl12] You should see active effects on only the "link": +link, +visited +

+ +

[cl13] You should see active effects on only the "visited": +link, +visited +

+ +

[cl14] You should see active effects on only the "visited": +link, +visited +

+ +

[cl15] You should see active effects on only the "link": +link, +visited +

+ +

[cl16] You should see active effects on only the "link": +link, +visited +

+ +

[cl17] You should see active effects on only the "visited": +link, +visited +

+ +

[cl18] You should see active effects on only the "visited": +link, +visited +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-11-01.htm ##### + + + +5.11.1 :first-child + + + + + + +

CSS2 Test Suite: 5.11.1 :first-child

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
LI:first-child {color: green;}
+P STRONG:first-child {color: green;}
+DIV > P:first-child {color: purple;}
+
+
+
+ + +

+The first child element of this paragraph is strongly emphasized text, and should be green, as is also the case for the strongly emphasized text which is the first child of the EM element found here.. The STRONG text in this sentence should NOT be green, since it is not the first child of anything. +

+

+In this paragraph, we have some emphasized text, and then a little later, some strongly emphasized text, which should NOT be green, since it is the second child of the paragraph (the EM element is the first). +

+ +
+ +
+Within this DIV... +

There is a paragraph, and as the first child, it should be purple.

+
+
+Within this DIV... +

An H3 element

+

There is a paragraph, and as the second child, it should NOT be either purple or green.

+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-11-02.htm ##### + + + +5.11.2 :link and :visited + + + + + + +

CSS2 Test Suite: 5.11.2 :link and :visited

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
A {color: green;}
+A:link {color: purple;}
+A:visited {color: lime;}
+#id1 {color: #006600;}
+A.external:link {color: olive;}
+A.external:visited {color: maroon;}
+
+
+

The following hyperlinks should be purple if the site is unvisited, lime (light green) if visited:

+ + +

Dark green in any circumstance:

+ + +

+The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A tag are applied to them under CSS1. It also should NOT turn orange when clicked upon. +

+ +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-11-03.htm ##### + + + +5.11.3 :active, :hover, and :focus + + + + + + +

CSS2 Test Suite: 5.11.3 :active, :hover, and :focus

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
A {color: red;}
+A:hover {color: cyan;}
+A:active {color: maroon;}
+A:focus {border: 1px solid red;}
+A:focus:hover {color: lime;}
+
+P.cl1:hover {background: yellow;}
+TD:hover {background: silver;}
+TD A:hover {color: red; background: yellow;}
+
+INPUT:hover {background: yellow;}
+INPUT:focus {background: #FF99FF;}
+INPUT:focus:hover {background: #99FF99;}
+
+
+

The following hyperlinks should become maroon (dark red) while active (being clicked), become cyan (light blue) while being hovered over but not in focus, have a one-pixel solid red border when in focus, and become lime (light green) when in focus and being hovered over:

+ + + +

+This paragraph, and the one at the top of the page, should have no effects applied when the mouse pointer hovers over them. +

+

+[cl1] This paragraph should attain a yellow background when the mouse pointer hovers over it, and have a transparent background in all other circumstances. Extra text has been included in an attempt to have the paragraph display more than one line of text. +

+ + + + + +
This cell contains no anchor.This cell contains an anchor.
+
+

+The elements in the following form should have a yellow background when being hovered over, a purple background when in focus, and a light green background when in focus and being hovered over. +

+
+

+
+
+ +

+

+Input 4.1 +Input 4.2 +Input 4.3 +

+

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-11-04.htm ##### + + + +5.11.4 :lang + + + + + + +

CSS2 Test Suite: 5.11.4 :lang

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P:lang(en) {color: green;}
+P:lang(de) {color: purple;}
+
+
+
+
+

+This paragraph should NOT be any color except black. It (along with all the test statements on this page) has an ancestor element with a lang attribute that has a value of et-kl, which is intended to reset any potentially inherited lang values, either from HTTP headers or the user's language settings. +

+

+[en] This paragraph has been marked English, and should be green. +

+

+[de] This paragraph has been marked Deutsch, despite the fact that it clearly is English, and should be purple. +

+

+[de-ch] This paragraph has been marked as Swiss German, despite the fact that it clearly is English, and should be purple. +

+

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-12-01.htm ##### + + + +5.12.1 :first-line + + + + + + +

CSS2 Test Suite: 5.12.1 :first-line

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P:first-line {color: green;}
+.cl2:first-line {font-size: 200%;}
+.cl3:first-line {font-variant: small-caps;}
+
+
+
+

+The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. +

+

+The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. [cl2] +

+

+The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line. [cl3] +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-12-02.htm ##### + + + +5.12.2 :first-letter + + + + + + +

CSS2 Test Suite: 5.12.2 :first-letter

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P:first-letter {color: maroon;}
+.cl2:first-letter {font-size: 200%;}
+P.cl3:first-letter {font-size: 350%;}
+
+
+
+

+The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. +

+

+The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. [cl2] +

+

+"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended. [cl3] +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec05-12-03.htm ##### + + + +5.12.3 :before and :after + + + + + + +

CSS2 Test Suite: 5.12.3 :before and :after

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
H3:before {content: "An H3 ";}
+P.special:before {content: "Special! ";}
+P.special:first-letter {color: green;}
+P.special:after {content: " -- The End.";}
+
+
+

This H3 element should have generated content at its beginning.

+

+This paragraph should have no generated content either before or after its content. +

+

+This paragraph should start with the word "Special!" and the first letter "S" should be green. Also, the paragraph should end with the words "The End." preceded by a double-dash composed of two hyphens. That is all. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-02-01.htm ##### + + + +6.2.1 inherit + + + + + + +

CSS2 Test Suite: 6.2.1 inherit

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.cl1 {color: red;}
+A:link {color: inherit; text-decoration: underline; font-weight: bold;}
+
+
+
+

+[cl1] Although this paragraph has a class of 'cl1', it also has an inline STYLE of 'color: inherit', which should cause it to inherit its color from the BODY element. Thus, the color should be black. +

+

+This unclassed paragraph contains a number of anchors which have been underlined and boldfaced, but whose color inherits from the paragraph itself (thus making them black). +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-03.htm ##### + + + +6.3 @import + + + + + + +

CSS2 Test Suite: 6.3 @import

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
@import "styleimport.css";
+@import url(folder/styleimport.css);
+
+/* This line resets any browsers that got confused by the @import lines */
+.ignored { color: black; }
+
+.style { font-weight: bold; color: green; background: silver none; }
+
+
+
+

The style declaration applied in each following case is: {font-weight: bold; color: green; background: silver none;}.

+ +

1. Inline style (style attribute).

+

2. Embedded stylesheet (style element).

+

3. Stylesheet imported by embedded stylesheet.

+

4. Stylesheet in another folder imported by embedded stylesheet.


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-04-01.htm ##### + + + +6.4.1 Cascading Order + + + + + + + +

CSS2 Test Suite: 6.4.1 Cascading Order

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
<LINK rel="stylesheet" type="text/css" HREF="linktest.css">
+LI {color: purple;}
+UL LI {color: blue;}
+UL LI LI {color: gray;}
+LI.red {color: green;}
+UL LI.mar {color: #660000;}
+UL LI#gre {color: green;}
+.test {color: blue;}
+.test {color: purple;}
+.cl1 {text-decoration: line-through;}
+
+
+
+ + +

+This sentence should be blue (STYLE attr.). +

+

+This sentence should be purple [class="test"]. +

+

+[cl1] This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported). +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-04-02.htm ##### + + + +6.4.2 !important rules + + + + + + +

CSS2 Test Suite: 6.4.2 !important rules

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P {color: green ! important;}
+P {color: red;}
+P#id1 {color: purple;}
+
+
+
+

+This sentence should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet. +

+

+[id1] This sentence should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute. +

+

+This sentence should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-04-03.htm ##### + + + +6.4.3 Calculating specificity + + + + + + +

CSS2 Test Suite: 6.4.3 Calculating specificity

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
* {color: red;}  /* a=0 b=0 c=0 -> specificity =   0 */
+LI  {color: maroon;}  /* a=0 b=0 c=1 -> specificity =   1 */
+UL LI {color: green;}  /* a=0 b=0 c=2 -> specificity =   2 */
+H1 + *[REL=up] {color: purple;}  /* a=0 b=1 c=1 -> specificity =  11 */
+UL OL LI.olive {color: olive;}  /* a=0 b=1 c=3 -> specificity =  13 */ 
+LI.olive.level {color: olive; font-weight: bold;}
+   /* a=0 b=2 c=1 -> specificity =  21 */
+#x34y {color: lime;}  /* a=1 b=0 c=0 -> specificity = 100 */ 
+
+
+
+
+
+

+Although this unstyled paragraph, and many other elements on this page, may be red, this is acceptable. For example, the text "No inheritance tests for this property" should be red. +

+ +

+[x34y] This paragraph should be lime. +

+

An H1 element

+

+[rel=up] This paragraph should be purple. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec06-04-04.htm ##### + + + +6.4.4 Precedence of non-CSS hints + + + + + + +

CSS2 Test Suite: 6.4.4 Precedence of non-CSS hints

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: green;}
+
+
+

+This paragraph contains text which is contained by [cl1] a FONT element with a color value of "red". This should be overridden by the CSS rule for class 'cl1', which takes precedence over the non-CSS presentational hint embodied by the FONT element. Therefore, the FONT-enclosed text should be green, not red. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-02.htm ##### + + + +8.2 Margins, padding, borders + + + + + + +

CSS2 Test Suite: 8.2 Margins, padding, borders

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
ul {background: green;
+    margin: 12px 12px 12px 12px;padding: 3px 3px 3px 3px;}
+li{color: black; background: gray;
+    margin: 12px 12px 12px 12px; padding: 12px 0px 12px 12px;
+    list-style: none;}
+li.withborder {border-color: black;
+    border-style: dashed; border-width: medium;}
+
+
+
+ +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-03a.htm ##### + + + +8.3a margin-top + + + + + + +

CSS2 Test Suite: 8.3 margin-top

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin-top: 10px;}
+.cl2 {margin-top: 15px;}
+.cl3 {margin-top: 1em;}
+.cl4 {margin-top: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no margins applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a top margin of 10 pixels. +
+
+[test cl2] This 'div' element should have a top margin of 15 pixels. +
+
+[test cl3] This 'div' element should have a top margin of 1em. +
+
+[test cl4] This 'div' element should have a top margin of -2 pixels, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-03b.htm ##### + + + +8.3b margin-right + + + + + + +

CSS2 Test Suite: 8.3 margin-right

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin-right: 10px;}
+.cl2 {margin-right: 15px;}
+.cl3 {margin-right: 1em;}
+.cl4 {margin-right: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no margins applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a right margin of 10 pixels. +
+
+[test cl2] This 'div' element should have a right margin of 15 pixels. +
+
+[test cl3] This 'div' element should have a right margin of 1em. +
+
+[test cl4] This 'div' element should have a right margin of -2 pixels, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-03c.htm ##### + + + +8.3c margin-bottom + + + + + + +

CSS2 Test Suite: 8.3 margin-bottom

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin-bottom: 10px;}
+.cl2 {margin-bottom: 15px;}
+.cl3 {margin-bottom: 1em;}
+.cl4 {margin-bottom: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no margins applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a bottom margin of 10 pixels. +
+
+[test cl2] This 'div' element should have a bottom margin of 15 pixels. +
+
+[test cl3] This 'div' element should have a bottom margin of 1em. +
+
+[test cl4] This 'div' element should have a bottom margin of -2 pixels, and an aqua background. +

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-03d.htm ##### + + + +8.3d margin-left + + + + + + +

CSS2 Test Suite: 8.3 margin-left

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin-left: 10px;}
+.cl2 {margin-left: 15px;}
+.cl3 {margin-left: 1em;}
+.cl4 {margin-left: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no margins applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a left margin of 10 pixels. +
+
+[test cl2] This 'div' element should have a left margin of 15 pixels. +
+
+[test cl3] This 'div' element should have a left margin of 1em. +
+
+[test cl4] This 'div' element should have a left margin of -2 pixels, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-03e.htm ##### + + + +8.3e margin + + + + + + +

CSS2 Test Suite: 8.3 margin

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin: 10px;}
+.cl2 {margin: 15px;}
+.cl3 {margin: 1em;}
+.cl4 {margin: -2px; background-color: aqua;}
+.cl5 {margin: 10px 20px 0 -5px;}
+.cl6 {margin: 10px 20px 0;}
+.cl7 {margin: 10px 20px;}
+
+
+
+
+[test] This 'div' element has no margins applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have an overall margin of 10 pixels. +
+
+[test cl2] This 'div' element should have an overall margin of 15 pixels. +
+
+[test cl3] This 'div' element should have an overall margin of 1em. +
+
+[test cl4] This 'div' element should have an overall margin of -2 pixels, and an aqua background. +
+
+[test cl5] This 'div' element should have margins of 10px top, 20px right, 0 bottom, and -5px left. +
+
+[test cl6] This 'div' element should have margins of 10px top, 20px right, 0 bottom, and 20px left. +
+
+[test cl7] This 'div' element should have margins of 10px top, 20px right, 10px bottom, and 20px left. +
+
+[test] This 'div' element contains a 'span' element with a class of 'cl5' that should appear to have no top or bottom margins, but a 20px right margin and a -5px left margin. If there is [cl5]any increase of line separation in the 'div' element due to the top and bottom margins on the 'span' element, the test has been failed; margins do not affect the height of lines. +

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-04a.htm ##### + + + +8.4a padding-top + + + + + + +

CSS2 Test Suite: 8.4 padding-top

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; margin: 0.5em 0;}
+.cl1 {padding-top: 10px;}
+.cl2 {padding-top: 15px;}
+.cl3 {padding-top: 1em;}
+.cl4 {padding-top: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no top padding applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a top padding of 10 pixels. +
+
+[test cl2] This 'div' element should have a top padding of 15 pixels. +
+
+[test cl3] This 'div' element should have a top padding of 1em. +
+
+[test cl4] This 'div' element should have a top padding of zero, as negative padding values are not permitted, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-04b.htm ##### + + + +8.4b padding-right + + + + + + +

CSS2 Test Suite: 8.4 padding-right

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; margin: 0.5em 0;}
+.cl1 {padding-right: 10px;}
+.cl2 {padding-right: 15px;}
+.cl3 {padding-right: 1em;}
+.cl4 {padding-right: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no right padding applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a right padding of 10 pixels. +
+
+[test cl2] This 'div' element should have a right padding of 15 pixels. +
+
+[test cl3] This 'div' element should have a right padding of 1em. +
+
+[test cl4] This 'div' element should have a right padding of zero, as negative padding values are not permitted, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-04c.htm ##### + + + +8.4c padding-bottom + + + + + + +

CSS2 Test Suite: 8.4 padding-bottom

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; margin: 0.5em 0;}
+.cl1 {padding-bottom: 10px;}
+.cl2 {padding-bottom: 15px;}
+.cl3 {padding-bottom: 1em;}
+.cl4 {padding-bottom: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no bottom padding applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a bottom padding of 10 pixels. +
+
+[test cl2] This 'div' element should have a bottom padding of 15 pixels. +
+
+[test cl3] This 'div' element should have a bottom padding of 1em. +
+
+[test cl4] This 'div' element should have a bottom padding of zero, as negative padding values are not permitted, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-04d.htm ##### + + + +8.4d padding-left + + + + + + +

CSS2 Test Suite: 8.4 padding-left

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; margin: 0.5em 0;}
+.cl1 {padding-left: 10px;}
+.cl2 {padding-left: 15px;}
+.cl3 {padding-left: 1em;}
+.cl4 {padding-left: -2px; background-color: aqua;}
+
+
+
+[test] This 'div' element has no left padding applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have a left padding of 10 pixels. +
+
+[test cl2] This 'div' element should have a left padding of 15 pixels. +
+
+[test cl3] This 'div' element should have a left padding of 1em. +
+
+[test cl4] This 'div' element should have a left padding of zero, as negative padding values are not permitted, and an aqua background. +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-04e.htm ##### + + + +8.4e padding + + + + + + +

CSS2 Test Suite: 8.4 padding

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; margin: 0.5em 0;}
+.cl1 {padding: 10px;}
+.cl2 {padding: 15px;}
+.cl3 {padding: 1em;}
+.cl4 {padding: -2px; background-color: aqua;}
+.cl5 {margin: 10px 20px 0 -5px;}
+.cl6 {margin: 10px 20px 0;}
+.cl7 {margin: 10px 20px;}
+
+
+
+
+[test] This 'div' element has no padding applied to it, and acts as a reference point. +
+
+[test cl1] This 'div' element should have an overall padding of 10 pixels. +
+
+[test cl2] This 'div' element should have an overall padding of 15 pixels. +
+
+[test cl3] This 'div' element should have an overall padding of 1em. +
+
+[test cl4] This 'div' element should have an overall padding of zero, as negative padding values are not permitted, and an aqua background. +
+
+[test cl5] This 'div' element should have padding of 10px top, 20px right, 0 bottom, and 0 left (as negative passing values are not permitted). +
+
+[test cl6] This 'div' element should have padding of 10px top, 20px right, 0 bottom, and 20px left. +
+
+[test cl7] This 'div' element should have padding of 10px top, 20px right, 10px bottom, and 20px left. +
+
+[test] This 'div' element contains a 'span' element with a class of 'cl5' that may or may not appear to have top or bottom padding, but should have a 20px right padding and a no left padding. If there is [cl5]any increase of line separation in the 'div' element due to the top and bottom padding on the 'span' element, the test has been failed; padding does not affect the height of lines. However, the padding may extend into or overlap other lines of text. +

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-01a.htm ##### + + + +8.5.1a border-top-width + + + + + + +

CSS2 Test Suite: 8.5.1 border-top-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid; border-width: 0;}
+.cl1 {border-top-width: thin;}
+.cl2 {border-top-width: medium;}
+.cl3 {border-top-width: thick;}
+.cl4 {border-top-width: 5px;}
+.cl5 {border-top-width: 0;}
+.cl6 {border-top-width: -5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear). +

+

+[test cl1] This 'p' element should have a thin top border. +

+

+[test cl2] This 'p' element should have a medium top border. +

+

+[test cl3] This 'p' element should have a thick top border. +

+

+[test cl4] This 'p' element should have a 5px top border. +

+

+[test cl5] This 'p' element should have no top border. +

+

+[test cl6] This 'p' element should have no top border, as negative border widths are not permitted. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px top border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-01b.htm ##### + + + +8.5.1b border-right-width + + + + + + +

CSS2 Test Suite: 8.5.1 border-right-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid; border-width: 0;}
+.cl1 {border-right-width: thin;}
+.cl2 {border-right-width: medium;}
+.cl3 {border-right-width: thick;}
+.cl4 {border-right-width: 5px;}
+.cl5 {border-right-width: 0;}
+.cl6 {border-right-width: -5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear). +

+

+[test cl1] This 'p' element should have a thin right border. +

+

+[test cl2] This 'p' element should have a medium right border. +

+

+[test cl3] This 'p' element should have a thick right border. +

+

+[test cl4] This 'p' element should have a 5px right border. +

+

+[test cl5] This 'p' element should have no right border. +

+

+[test cl6] This 'p' element should have no right border, as negative border widths are not permitted. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px right border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-01c.htm ##### + + + +8.5.1c border-bottom-width + + + + + + +

CSS2 Test Suite: 8.5.1 border-bottom-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid; border-width: 0;}
+.cl1 {border-bottom-width: thin;}
+.cl2 {border-bottom-width: medium;}
+.cl3 {border-bottom-width: thick;}
+.cl4 {border-bottom-width: 5px;}
+.cl5 {border-bottom-width: 0;}
+.cl6 {border-bottom-width: -5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear). +

+

+[test cl1] This 'p' element should have a thin bottom border. +

+

+[test cl2] This 'p' element should have a medium bottom border. +

+

+[test cl3] This 'p' element should have a thick bottom border. +

+

+[test cl4] This 'p' element should have a 5px bottom border. +

+

+[test cl5] This 'p' element should have no bottom border. +

+

+[test cl6] This 'p' element should have no bottom border, as negative border widths are not permitted. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px bottom border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-01d.htm ##### + + + +8.5.1d border-left-width + + + + + + +

CSS2 Test Suite: 8.5.1 border-left-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid; border-width: 0;}
+.cl1 {border-left-width: thin;}
+.cl2 {border-left-width: medium;}
+.cl3 {border-left-width: thick;}
+.cl4 {border-left-width: 5px;}
+.cl5 {border-left-width: 0;}
+.cl6 {border-left-width: -5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear). +

+

+[test cl1] This 'p' element should have a thin left border. +

+

+[test cl2] This 'p' element should have a medium left border. +

+

+[test cl3] This 'p' element should have a thick left border. +

+

+[test cl4] This 'p' element should have a 5px left border. +

+

+[test cl5] This 'p' element should have no left border. +

+

+[test cl6] This 'p' element should have no left border, as negative border widths are not permitted. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px left border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-01e.htm ##### + + + +8.5.1e border-width + + + + + + +

CSS2 Test Suite: 8.5.1 border-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-width: thin;}
+.cl2 {border-width: medium;}
+.cl3 {border-width: thick;}
+.cl4 {border-width: 5px;}
+.cl5 {border-width: 0;}
+.cl6 {border-width: -5px;}
+
+
+
+

+[test] This 'p' element has no border width applied to it, and acts as a reference point. It should default to the same border width as the result shown for 'medium' (cl2). +

+

+[test cl1] This 'p' element should have a thin overall border. +

+

+[test cl2] This 'p' element should have a medium overall border. +

+

+[test cl3] This 'p' element should have a thick overall border. +

+

+[test cl4] This 'p' element should have a 5px overall border. +

+

+[test cl5] This 'p' element should have no overall border. +

+

+[test cl6] This 'p' element should have a default-width border, as negative border widths are not permitted. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px overall border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-02a.htm ##### + + + +8.5.2a border-top-color + + + + + + +

CSS2 Test Suite: 8.5.2 border-top-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-top-color: green;}
+
+
+
+

+[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element. +

+

+[test cl1] This 'p' element should have a green top border, with the other border sides matching the text color. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green top border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-02b.htm ##### + + + +8.5.2b border-right-color + + + + + + +

CSS2 Test Suite: 8.5.2 border-right-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-right-color: green;}
+
+
+
+

+[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element. +

+

+[test cl1] This 'p' element should have a green right border, with the other border sides matching the text color. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green right border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-02c.htm ##### + + + +8.5.2c border-bottom-color + + + + + + +

CSS2 Test Suite: 8.5.2 border-bottom-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-bottom-color: green;}
+
+
+
+

+[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element. +

+

+[test cl1] This 'p' element should have a green bottom border, with the other border sides matching the text color. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green bottom border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-02d.htm ##### + + + +8.5.2d border-left-color + + + + + + +

CSS2 Test Suite: 8.5.2 border-left-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-left-color: green;}
+
+
+
+

+[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element. +

+

+[test cl1] This 'p' element should have a green left border, with the other border sides matching the text color. +

+

+[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green left border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-02e.htm ##### + + + +8.5.2e border-color + + + + + + +

CSS2 Test Suite: 8.5.2 border-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-style: solid;}
+.cl1 {border-color: green;}
+.cl2 {border-color: green red blue purple;}
+.cl3 {border-color: green red blue;}
+.cl4 {border-color: green red;}
+
+
+
+

+[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element. +

+

+[test cl1] This 'p' element should have a green border. +

+

+[test cl2] This 'p' element should have a green top border, a red right border, a blue bottom border, and a purple left border. +

+

+[test cl3] This 'p' element should have a green top border, a red right border, a blue bottom border, and a red left border. +

+

+[test cl4] This 'p' element should have a green top border, a red right border, a green bottom border, and a red left border. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-03a.htm ##### + + + +8.5.3a border-top-style + + + + + + +

CSS2 Test Suite: 8.5.3 border-top-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-width: 5px; border-color: #753;}
+.cl1 {border-top-style: solid;}
+.cl2 {border-top-style: dotted;}
+.cl3 {border-top-style: dashed;}
+.cl4 {border-top-style: double;}
+.cl5 {border-top-style: groove;}
+.cl6 {border-top-style: ridge;}
+.cl7 {border-top-style: inset;}
+.cl8 {border-top-style: outset;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753. +

+

+[test cl1] This 'p' element should have a solid top border. +

+

+[test cl2] This 'p' element should have a dotted top border. +

+

+[test cl3] This 'p' element should have a dashed top border. +

+

+[test cl4] This 'p' element should have a double top border. +

+

+[test cl5] This 'p' element should have a grooved top border. +

+

+[test cl6] This 'p' element should have a ridged top border. +

+

+[test cl7] This 'p' element should have an inset top border. +

+

+[test cl8] This 'p' element should have an outset top border. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid top text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-03b.htm ##### + + + +8.5.3b border-right-style + + + + + + +

CSS2 Test Suite: 8.5.3 border-right-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-width: 5px; border-color: #753;}
+.cl1 {border-right-style: solid;}
+.cl2 {border-right-style: dotted;}
+.cl3 {border-right-style: dashed;}
+.cl4 {border-right-style: double;}
+.cl5 {border-right-style: groove;}
+.cl6 {border-right-style: ridge;}
+.cl7 {border-right-style: inset;}
+.cl8 {border-right-style: outset;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753. +

+

+[test cl1] This 'p' element should have a solid right border. +

+

+[test cl2] This 'p' element should have a dotted right border. +

+

+[test cl3] This 'p' element should have a dashed right border. +

+

+[test cl4] This 'p' element should have a double right border. +

+

+[test cl5] This 'p' element should have a grooved right border. +

+

+[test cl6] This 'p' element should have a ridged right border. +

+

+[test cl7] This 'p' element should have an inset right border. +

+

+[test cl8] This 'p' element should have an outset right border. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid right text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-03c.htm ##### + + + +8.5.3c border-bottom-style + + + + + + +

CSS2 Test Suite: 8.5.3 border-bottom-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-width: 5px; border-color: #753;}
+.cl1 {border-bottom-style: solid;}
+.cl2 {border-bottom-style: dotted;}
+.cl3 {border-bottom-style: dashed;}
+.cl4 {border-bottom-style: double;}
+.cl5 {border-bottom-style: groove;}
+.cl6 {border-bottom-style: ridge;}
+.cl7 {border-bottom-style: inset;}
+.cl8 {border-bottom-style: outset;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753. +

+

+[test cl1] This 'p' element should have a solid bottom border. +

+

+[test cl2] This 'p' element should have a dotted bottom border. +

+

+[test cl3] This 'p' element should have a dashed bottom border. +

+

+[test cl4] This 'p' element should have a double bottom border. +

+

+[test cl5] This 'p' element should have a grooved bottom border. +

+

+[test cl6] This 'p' element should have a ridged bottom border. +

+

+[test cl7] This 'p' element should have an inset bottom border. +

+

+[test cl8] This 'p' element should have an outset bottom border. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid bottom text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-03d.htm ##### + + + +8.5.3d border-left-style + + + + + + +

CSS2 Test Suite: 8.5.3 border-left-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-width: 5px; border-color: #753;}
+.cl1 {border-left-style: solid;}
+.cl2 {border-left-style: dotted;}
+.cl3 {border-left-style: dashed;}
+.cl4 {border-left-style: double;}
+.cl5 {border-left-style: groove;}
+.cl6 {border-left-style: ridge;}
+.cl7 {border-left-style: inset;}
+.cl8 {border-left-style: outset;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753. +

+

+[test cl1] This 'p' element should have a solid left border. +

+

+[test cl2] This 'p' element should have a dotted left border. +

+

+[test cl3] This 'p' element should have a dashed left border. +

+

+[test cl4] This 'p' element should have a double left border. +

+

+[test cl5] This 'p' element should have a grooved left border. +

+

+[test cl6] This 'p' element should have a ridged left border. +

+

+[test cl7] This 'p' element should have an inset left border. +

+

+[test cl8] This 'p' element should have an outset left border. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid left text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-03e.htm ##### + + + +8.5.3e border-style + + + + + + +

CSS2 Test Suite: 8.5.3 border-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver; border-width: 5px; border-color: #753;}
+.cl1 {border-style: solid;}
+.cl2 {border-style: dotted;}
+.cl3 {border-style: dashed;}
+.cl4 {border-style: double;}
+.cl5 {border-style: groove;}
+.cl6 {border-style: ridge;}
+.cl7 {border-style: inset;}
+.cl8 {border-style: outset;}
+.cl9 {border-style: solid dotted double groove;}
+.cl10 {border-style: solid dotted double;}
+.cl11 {border-style: solid dotted;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753. +

+

+[test cl1] This 'p' element should have a solid overall border. +

+

+[test cl2] This 'p' element should have a dotted overall border. +

+

+[test cl3] This 'p' element should have a dashed overall border. +

+

+[test cl4] This 'p' element should have a double overall border. +

+

+[test cl5] This 'p' element should have a grooved overall border. +

+

+[test cl6] This 'p' element should have a ridged overall border. +

+

+[test cl7] This 'p' element should have an inset overall border. +

+

+[test cl8] This 'p' element should have an outset overall border. +

+

+[test cl9] This 'p' element should have a solid top border, a dotted right border, a double bottom border, and a groove left border. +

+

+[test cl10] This 'p' element should have a solid top border, a dotted right border, a double bottom border, and a dotted left border. +

+

+[test cl11] This 'p' element should have a solid top border, a dotted right border, a solid bottom border, and a dotted left border. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid text-colored medium-width border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-04a.htm ##### + + + +8.5.4a border-top + + + + + + +

CSS2 Test Suite: 8.5.4 border-top

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: silver; border-style: none;}
+.cl1 {border-top: solid;}
+.cl2 {border-top: solid green;}
+.cl3 {border-top: solid green 5px;}
+.cl4 {border-top: green 5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none. +

+

+[test cl1] This 'p' element should have a medium-width solid text-colored top border. +

+

+[test cl2] This 'p' element should have a medium-width solid green top border. +

+

+[test cl3] This 'p' element should have a 5px solid green top border. +

+

+[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored top border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-04b.htm ##### + + + +8.5.4b border-right + + + + + + +

CSS2 Test Suite: 8.5.4 border-right

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: silver; border-style: none;}
+.cl1 {border-right: solid;}
+.cl2 {border-right: solid green;}
+.cl3 {border-right: solid green 5px;}
+.cl4 {border-right: green 5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none. +

+

+[test cl1] This 'p' element should have a medium-width solid text-colored right border. +

+

+[test cl2] This 'p' element should have a medium-width solid green right border. +

+

+[test cl3] This 'p' element should have a 5px solid green right border. +

+

+[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored right border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-04c.htm ##### + + + +8.5.4c border-bottom + + + + + + +

CSS2 Test Suite: 8.5.4 border-bottom

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: silver; border-style: none;}
+.cl1 {border-bottom: solid;}
+.cl2 {border-bottom: solid green;}
+.cl3 {border-bottom: solid green 5px;}
+.cl4 {border-bottom: green 5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none. +

+

+[test cl1] This 'p' element should have a medium-width solid text-colored bottom border. +

+

+[test cl2] This 'p' element should have a medium-width solid green bottom border. +

+

+[test cl3] This 'p' element should have a 5px solid green bottom border. +

+

+[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored bottom border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-04d.htm ##### + + + +8.5.4d border-left + + + + + + +

CSS2 Test Suite: 8.5.4 border-left

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: silver; border-style: none;}
+.cl1 {border-left: solid;}
+.cl2 {border-left: solid green;}
+.cl3 {border-left: solid green 5px;}
+.cl4 {border-left: green 5px;}
+
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none. +

+

+[test cl1] This 'p' element should have a medium-width solid text-colored left border. +

+

+[test cl2] This 'p' element should have a medium-width solid green left border. +

+

+[test cl3] This 'p' element should have a 5px solid green left border. +

+

+[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored left border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec08-05-04e.htm ##### + + + +8.5.4e border + + + + + + +

CSS2 Test Suite: 8.5.4 border

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: silver; border-style: none;}
+.cl1 {border: medium black solid;}
+.cl2 {border: thin maroon ridge;}
+.cl3 {border: 10px teal outset;}
+.cl4 {border: 10px olive inset;}
+.cl5 {border: 10px maroon;}
+.cl6 {border: maroon double;}
+.cl7 {border: left red solid;}
+.cl8 {border: solid 0px;}
+
+
+

+[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none. +

+

+[test cl1] This 'p' element should have an overall medium-width solid black border. +

+

+[test cl2] This 'p' element should have an overall thin ridged maroon border. +

+

+[test cl3] This 'p' element should have an overall 10px outset teal border. +

+

+[test cl4] This 'p' element should have an overall 10px inset olive border. +

+

+[test cl5] This 'p' element should have an overall 10 solid maroon border. +

+

+[test cl6] This 'p' element should have an overall medium-width double maroon border. +

+

+[test cl7] This 'p' element should have no border, as the value supplied is invalid. +

+

+[test cl8] This 'p' element should have no border, as its width has been set to zero. +

+

+[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have an overall medium-width solid black border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-02-05.htm ##### + + + +9.2.5 display + + + + + + +

CSS2 Test Suite: 9.2.5 display

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {display: inline;}
+.cl2 {display: block; background: #FCC;}
+.cl3 {display: list-item; list-style-type: square; margin-left: 3em;}
+.cl4 {display: none; color: red; font-weight: bold; background: yellow;}
+.cl5 {display: run-in;}
+.cl6 {margin-left: 5em;}
+dt {display: compact;}
+
+
+
+

+In this page, each test or set of tests has been separated with an 'hr' element in order to keep them distinct from one another. +

+ +
+ +

[cl1] This 'p' element should be inline, as should the next two.

+

[cl1] This 'p' element should be inline, as should the previous and next paragraph.

+

[cl1] This 'p' element should be inline, as should the previous two.

+ +
+ +
+This 'div' element, which is unstyled, contains a 'span' element [cl2] which is set to class 'cl2' and should therefore be block-level thus breaking up the flow of the 'div' by interrupting it with another block-level element. +
+ +
+ +

[cl3] This paragraph should be rendered as a list-item.

+ +
+ +

The text following the class marker should be invisible: [cl4] you can't see me!

+

If the following paragraph is visible, it will be very obvious. It should not be visible, since it a has a class of "cl4".

+

Hey! I shouldn't be visible!

+ +
+ +

[cl5] A Heading 3.

+

The previous 'h3' element (with a class of 'cl5') should run into this paragraph, which means that it appears as inline content at the beginning of this paragraph.

+ +
+ +
+
[cl6]
+
This is a 'dd' element with a 'dt' element preceding it.
+
Term Number 2
+
This is another 'dd' element with a 'dt' element preceding it.
+
No. 3
+
This is yet another 'dd' element with a 'dt' element preceding it.
+

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-03-01.htm ##### + + + +9.3.1 position + + + + + + +

CSS2 Test Suite: 9.3.1 position

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {position: static; top: -5px; left: 2px;}
+.cl2 {position: relative; top: -5px; left: 2px;}
+.cl3 {position: absolute; top: 25px; left: 2px;}
+.cl4 {position: fixed; top: 0px;  left: 200px;}
+.contain {position: relative; background: yellow; height: 50px;}
+
+
+

+The following paragraph will contain four positioned images. Each image is prefaced by a class marker, and each image is numbered so that it is possible to determine which images have been positioned in which places. The containing 'p' element has a class of 'contain'. The following is what should happen with each image: +

+ +

+[cl1] image +[cl2] image +[cl3] image +[cl4] image +

+ +

+An excerpt from section 9.3.1: +

+ +

The 'position' and 'float' properties determine which +of the CSS2 positioning algorithms is used to calculate +the position of a box. + +

+
+'position' +
+ +
Value:  static | relative | absolute | fixed | inherit + +
Initial:  static +
Applies to:  all elements, but not to generated content +
Inherited:  no +
Percentages:  N/A +
Media:  visual +
+
+
+ + +

The values of this property have the following meanings:

+ +
+
static + +
The box is a normal box, laid out according to the normal flow. The 'left' and 'top' properties do not apply. + +
relative + +
The box's position is calculated according to the normal flow (this is called the position in +normal flow). Then the box is offset relative to its normal position. When +a box B is relatively positioned, the position of the following box is +calculated as though B were not offset. + +
absolute +
The box's position (and possibly size) is specified +with the 'left', +'right', +'top', +and 'bottom' properties. +These properties specify offsets with respect to the box's + +containing block. Absolutely +positioned boxes are taken out of the normal flow. This means +they have no impact on the layout of later siblings. Also, +though absolutely positioned boxes have margins, they +do not collapse +with any other margins. + +
fixed +
The box's position is calculated according to the 'absolute' +model, but in addition, the box is fixed with respect to some reference. In +the case of continuous +media, the box is fixed with respect to the viewport (and doesn't move when scrolled). In +the case of paged media, +the box is fixed with respect to the page, even if that page is seen +through a viewport (in the case of a +print-preview, for example).
+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-03-02a.htm ##### + + + +9.3.2a top + + + + + + +

CSS2 Test Suite: 9.3.2 top

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: purple; position: relative; top: 10px;}
+.img-contain {position: relative; background: yellow; 
+     height: 50px; width: 250px;}
+.img-contain img {position: absolute;}
+
+
+
+

+This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels downward. The space it would have occupied will be preserved. +

+

+The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The top edge of the image should be placed 10 pixels below the top edge of the containing block established by the 'div'. +

+
+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-03-02b.htm ##### + + + +9.3.2b right + + + + + + +

CSS2 Test Suite: 9.3.2 right

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: purple; position: relative; right: 10px;}
+.img-contain {position: relative; background: yellow; 
+     height: 50px; width: 250px;}
+.img-contain img {position: absolute;}
+
+
+
+

+This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels to the left. The space it would have occupied will be preserved. +

+

+The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The right edge of the image should be placed 10 pixels to the left of the right edge of the containing block established by the 'div'. +

+
+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-03-02c.htm ##### + + + +9.3.2c bottom + + + + + + +

CSS2 Test Suite: 9.3.2 bottom

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: purple; position: relative; bottom: 10px;}
+.img-contain {position: relative; background: yellow; 
+     height: 50px; width: 250px;}
+.img-contain img {position: absolute;}
+
+
+
+

+This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels upward. The space it would have occupied will be preserved. +

+

+The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The bottom edge of the image should be placed 10 pixels above the bottom edge of the containing block established by the 'div'. +

+
+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-03-02d.htm ##### + + + +9.3.2d left + + + + + + +

CSS2 Test Suite: 9.3.2 left

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: purple; position: relative; left: 10px;}
+.img-contain {position: relative; background: yellow; 
+     height: 50px; width: 250px;}
+.img-contain img {position: absolute;}
+
+
+
+

+This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels to the right. The space it would have occupied will be preserved. +

+

+The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The left edge of the image should be placed 10 pixels to the right of the left edge of the containing block established by the 'div'. +

+
+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-05-01.htm ##### + + + +9.5.1 float + + + + + + +

CSS2 Test Suite: 9.5.1 float

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
IMG {float: right;}
+IMG.cl1 {float: left;}
+IMG.cl2 {float: right;}
+IMG.cl3 {float: none;}
+P.cl4 {float: left; width: 10em; background: yellow;}
+SPAN.cl5 {float: right; width: 7em; background: yellow;}
+
+
+

+ +[cl1] The image which occurs at the beginning of this paragraph should be floated to the left, and the text is the paragraph should "wrap around" the image. This is the kind of behavior we've come to expect from Web browsers over the years. +

+

+ +[cl2] The image which occurs at the beginning of this paragraph should be floated to the right, and the text is the paragraph should "wrap around" the image. This is the kind of behavior we've come to expect from Web browsers over the years. +

+

+ +[cl3] The image which occurs at the beginning of this paragraph should not be floated at all, and therefore the text is the paragraph should not "wrap around" the image. Instead, the image should appear as an inline element at the beginning of the paragraph. This is the kind of behavior we came to expect from Web browsers in the early years. +

+ +

[cl4] This paragraph has been floated to the left, and has a width of ten (10) em with a yellow background.

+

+This is an ordinary, unstyled paragraph. It should "wrap around" the previous paragraph, the one with a class of 'cl4', due to the floatation of the previous paragraph. In other words, the behavior should be exactly the same as one would expect from the test cases above, or indeed from any surfing done on the Web. +

+
+

+This paragraph contains an inline element [cl5] with a class of 'cl5' which should float to the right, be seven (7) em wide, and have a yellow background. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-05-02.htm ##### + + + +9.5.2 clear + + + + + + +

CSS2 Test Suite: 9.5.2 clear

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {clear: left;}
+.cl2 {clear: right;}
+.cl3{clear: both;}
+.cl4 {clear: none;}
+
+
+[Image] +

+This text should be flowing past a tall orange rectangle on the left side of the browser window. +

+
+[Image] +

+[cl1] This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it. +

+
+[Image] +

+[cl2] This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it. +

+
+[Image] +[Image] +

+[cl3] This paragraph should appear below the two tall orange rectangles, and not flow between them. +

+[Image] +[Image] +

+[cl4] This paragraph should be between both tall orange rectangles. +

+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-08-02.htm ##### + + + +9.8.2 Relative Positioning + + + + + + +

CSS2 Test Suite: 9.8.2 Relative Positioning

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.start {line-height: 24px; font-size: 12px; width: 400px;
+     color: black; background: white;}
+#outer {color: purple; border: 1px solid purple; position: relative; top: -12px;}
+#inner {color: blue; border: 1px solid blue; position: relative; top: 12px;}
+
+DIV {background: yellow; height: 50px; width: 250px; margin: 10px;}
+IMG.cl1 {position: relative; top: 30%;}
+IMG.cl2 {position: relative; right: -30%;}
+IMG.cl3 {position: relative; bottom: 30%;}
+IMG.cl4 {position: relative; left: 30%;}
+IMG.cl5 {position: relative; top: -20px;}
+IMG.cl6 {position: relative; right: -20px;}
+IMG.cl7 {position: relative; bottom: -20px;}
+IMG.cl8 {position: relative; left: -20px;}
+
+SPAN.cl9 {position: relative; top: -1em; left: -5em; color: purple;}
+SPAN.cl10 {position: relative; bottom: -1em; right: -5em; color: purple;}
+
+
+

+[start] The beginning of the paragraph contents. +[outer] The beginning of the outer SPAN. +[inner] The contents of the inner SPAN. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+ +
+ +

+The following DIVs have been engineered to create a context for positioning. The class of each test is noted at the beginning of the DIV. The percentage offsets should be calculated with respect to the width (250px) or height (50px) of the containing block, depending on the property being tested. +

+
+[cl1] +
+
+[cl2] +
+
+[cl3] +
+
+[cl4] +
+
+[cl5] +
+
+[cl6] +
+
+[cl7] +
+
+[cl8] +
+
+

+This paragraph contains a SPAN element [cl9] which has been shifted up, and to the left, which demonstrates relative positioning. +

+

+This paragraph contains a SPAN element [cl10] which has been shifted down, and to the right, which demonstrates relative positioning. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-08-03.htm ##### + + + +9.8.3 Floating a Box + + + + + + +

CSS2 Test Suite: 9.8.3 Floating a Box

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.start {line-height: 24px; font-size: 12px; width: 400px;
+     color: black; background: white;}
+#outer1 {color: purple; border: 1px solid purple;}
+#inner1 {color: blue; border: 1px solid blue; float: right; width: 130px;}
+#outer2 {color: purple; border: 1px solid purple;}
+#inner2 {color: blue; border: 1px solid blue; float: right; width: 130px;}
+#sibling2 {color: maroon; border: 1px solid maroon;}
+#outer3 {color: purple; border: 1px solid purple;}
+#inner3 {color: blue; border: 1px solid blue; float: right; width: 130px;}
+#sibling3 {color: maroon; border: 1px solid maroon; clear: right;}
+
+
+
+

+[start] The beginning of the paragraph contents. +[outer1] The beginning of the outer SPAN. +[inner1] The contents of the inner SPAN. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+ +

+[start] The beginning of the paragraph contents. +[outer2] The beginning of the outer SPAN. +[inner2] The contents of the inner SPAN. +[sibling2] The sibling's contents. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+ +

+[start] The beginning of the paragraph contents. +[outer3] The beginning of the outer SPAN. +[inner3] The contents of the inner SPAN. +[sibling3] The sibling's contents. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-08-04.htm ##### + + + +9.8.4 Absolute Positioning + + + + + + +

CSS2 Test Suite: 9.8.4 Absolute Positioning

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.start {line-height: 24px; font-size: 12px; width: 400px;
+     color: black; background: white; position: relative;}
+#outer1 {color: purple; border: 1px solid purple; position: absolute; top: 100px; left: 100px; width: 200px;}
+#inner1 {color: blue; border: 1px solid blue;}
+#outer2 {color: purple; border: 1px solid purple; position: relative;}
+#inner2 {color: blue; border: 1px solid blue; position: absolute; top: 100px; left: -100px; width: 200px;}
+
+P.barnote {position: relative; margin-right: 2em; left: 2em; width: 50%;}
+SPAN.mark {position: absolute; top: auto; left: -2em; color: maroon;}
+
+DIV {position: relative; background: yellow; height: 50px; width: 250px; margin: 10px;}
+IMG.cl1 {position: absolute; top: 30%;}
+IMG.cl2 {position: absolute; right: 30%;}
+IMG.cl3 {position: absolute; bottom: 30%;}
+IMG.cl4 {position: absolute; left: 30%;}
+IMG.cl5 {position: absolute; top: 0; left: 0;}
+IMG.cl6 {position: absolute; top: 0; right: 100%;}
+IMG.cl7 {position: absolute; bottom: 100%; left: 0;}
+IMG.cl8 {position: absolute; bottom: 100%; right: 100%;}
+
+
+
+

+[start] The beginning of the paragraph contents. +[outer1] The beginning of the outer SPAN. +[inner1] The contents of the inner SPAN. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+ +

+[start] The beginning of the paragraph contents. +[outer2] The beginning of the outer SPAN. +[inner2] The contents of the inner SPAN. +[outer] The end of the outer SPAN. +The end of the paragraph contents. +

+ +
+ +

+[barnote] This paragraph contains an SPAN element (with a class of 'mark') which will cause the SPANned text to be "floated" to the beginning of the line in which it occurs. In other words, a pair of red dashes will appear at the beginning of the line containing THIS -- word. +

+ +
+ +

+The following DIVs have been engineered to create a context for positioning. The class of each test is noted at the beginning of the DIV. The percentage offsets should be calculated with respect to the width (250px) or height (50px) of the containing block, depending on the property being tested. +

+
+[cl1] +
+
+[cl2] +
+
+[cl3] +
+
+[cl4] +
+
+

+The following four images have been absolutely positioned without a containing element, and so are positioned with respect to the BODY element, which is their parent element. The images should be scrolled with the document, should any scrolling occur. +

+[cl5] +[cl6] +[cl7] +[cl8] +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-09-01.htm ##### + + + +9.9.1 z-index + + + + + + +

CSS2 Test Suite: 9.9.1 z-index

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.poswrap {position: relative; border: 1px solid purple;
+     height: 16px; margin-bottom: 16px;}
+.cl1 {position: absolute; left: 0px; top: 0px; z-index: -5;}
+.cl2 {position: absolute; left: 43px; top: 0px; z-index: 5;}
+.cl3 {position: absolute; left: 0px; top: 0px; z-index: 5;}
+.cl4 {position: absolute; left: 43px; top: 0px; z-index: -5;}
+
+
+
+

+The following paragraph will contain two line-break separated images which are absolutely positioned. The first image should be overlapped by the second image. Note that positioning must be supported in order for this test to work, but z-index doesn't do much good without positioning anyway. +

+ +

+
+
+

+ +

+The following paragraph will contain two line-break separated images which are absolutely positioned. The containing paragraph is set to be relatively positioned, so that the image offsets are calculated with respect to the upper left corner of the paragraph. The second image should be overlapped by the first image. Note that positioning must be supported in order for this test to work, but z-index doesn't do much good without positioning anyway. +

+ +

+
+
+

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-10a.htm ##### + + + +9.10a direction + + + + + + +

CSS2 Test Suite: 9.10 direction

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
P.cl1 {direction: ltr;}
+P.cl2 {direction: rtl;}
+
+
+
+

+[cl1] This paragraph should be written left-to-right. +

+

+[cl2] This paragraph should be written right-to-left. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec09-10b.htm ##### + + + +9.10b unicode-bidi + + + + + + +

CSS2 Test Suite: 9.10 unicode-bidi

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div {border: 1px dotted gray; background: white;
+   padding: 0.25em; margin-bottom: 0.5em;}
+span {border: 1px dashed gray; border-color: gray red silver blue;
+   padding: 1px 0.5em;}
+.left {direction: ltr;}
+.right {direction: rtl;}
+.cl1 {unicode-bidi: normal;}
+.cl2 {unicode-bidi: bidi-override;}
+.cl3 {unicode-bidi: embed;}
+
+
+
+

+The characters in the following elements should be ordered according to the value of 'unicode-bidi'. +

+
+[left cl1] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
+[left cl2] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
+[left cl3] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
+[right cl1] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
+[right cl2] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
+[right cl3] 1 2 3 4 5 6 7 8 9 10 11 12 13 +a b c d e f g +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-02.htm ##### + + + +10.2 width + + + + + + +

CSS2 Test Suite: 10.2 width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {width: 50px;}
+.cl2 {width: 25%;}
+.cl3 {width: 150px; background: yellow;}
+
+
+
+

+The following image has no class, and is provided as a reference point for the tests to follow. +

+[image] +

+The following image has a class of 'cl1', and should be 50 pixels wide. Since the source image is square, it should also be 50 pixels tall. +

+[image] +

+The following image has a class of 'cl2', and should be one-quarter the width of its parent element (the 'body'). Since the source image is square, the height of the image should equal its width. +

+[image] +

+This 'p' element contains a 'span' element that has a class of 'cl3'. The 'span' is here: [cl3]. Since width does not apply to inline non-replaced elements, the 'span' should not be 150 pixels wide. If the 'span' is 150 pixels wide, the test has been failed. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-01.htm ##### + + + +10.3.1 Computing widths and margins: inline, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.3.1 Computing widths and margins: inline, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.bookend {background: #FCC;}
+.test {background: #9F9;}
+.cl1 {width: 200px;}
+.cl2 {padding: 0 10px;}
+.cl3 {border: 10px solid green; border-width: 0 10px;}
+.cl4 {margin: 0 10px;}
+.cl5 {padding: 0 10px; border: 10px solid green; border-width: 0 10px; margin: 0 10px;}
+.cl6 {margin: 0 auto;}
+
+
+
+

+This 'p' element contains a 'span' element with a class of 'test cl1', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl1] this is a span[bookend]. The test span's width should be equal to the size of the content, and it should not be 200 pixels wide, as 'width' is ignored for inline non-replaced elements. The left and right padding, borders, and margins should all have zero width. +

+

+This 'p' element contains a 'span' element with a class of 'test cl2', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl2] this is a span[bookend]. The test span's right and left padding should each be 10 pixels wide. +

+

+This 'p' element contains a 'span' element with a class of 'test cl3', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl3] this is a span[bookend]. The test span's right and left borders should each be 10 pixels wide (and solid green). +

+

+This 'p' element contains a 'span' element with a class of 'test cl4', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl4] this is a span[bookend]. The test span's right and left margins should each be 10 pixels wide. +

+

+This 'p' element contains a 'span' element with a class of 'test cl5', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl5] this is a span[bookend]. The test span's right and left padding, borders, and margins should each be 10 pixels wide, and the width should be equal to the size of the content. +

+

+This 'p' element contains a 'span' element with a class of 'test cl6'., surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend][test cl6] this is a span[bookend]. The test span's right and left margins should have zero width. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-02.htm ##### + + + +10.3.2 Computing widths and margins: inline, replaced elements + + + + + + +

CSS2 Test Suite: 10.3.2 Computing widths and margins: inline, replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.bookend {background: #FCC;}
+.test {background: #9F9;}
+.cl1 {width: 30px;}
+.cl2 {padding: 0 10px;}
+.cl3 {border: 10px solid green; border-width: 0 10px;}
+.cl4 {margin: 0 10px;}
+.cl5 {width: 30px; padding: 0 10px; border: 10px solid green; border-width: 0 10px; margin: 0 10px;}
+.cl6 {width: auto;}
+
+
+
+

+This 'p' element contains an 'img' element with a class of 'test cl1', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's width should be 30 pixels. The left and right padding, borders, and margins should all have zero width. +

+

+This 'p' element contains an 'img' element with a class of 'test cl2', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's right and left padding should each be 10 pixels wide. +

+

+This 'p' element contains an 'img' element with a class of 'test cl3', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's right and left borders should each be 10 pixels wide (and solid green). +

+

+This 'p' element contains an 'img' element with a class of 'test cl4', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's right and left margins should each be 10 pixels wide. +

+

+This 'p' element contains an 'img' element with a class of 'test cl5', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's right and left padding, border, and margins should each be 10 pixels wide, and the image's width should be 30 pixels. +

+

+This 'p' element contains an 'img' element with a class of 'test cl6', surrounded by 'span' elements with a class of 'bookend'. These elements are here: +[bookend]image[bookend]. The image's width should be equal to its intrinsic width, which is 20 pixels. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-03.htm ##### + + + +10.3.3 Computing widths and margins: block-level, non-replaced elements in normal flow + + + + + + +

CSS2 Test Suite: 10.3.3 Computing widths and margins: block-level, non-replaced elements in normal flow

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {margin-left: 10px;}
+.cl2 {margin-left: 10px;}
+.cl3 {margin-left: 0;    width: 50%;  margin-right: auto;}
+.cl4 {margin-left: auto; width: 50%;  margin-right: auto;}
+.cl5 {margin-left: auto; width: 50%;  margin-right: 0;}
+.cl6 {margin-left: auto; width: auto; margin-right: 0;}
+.cl7 {margin-left: 0;    width: auto; margin-right: auto;}
+.cl8 {margin-left: auto; width: auto; margin-right: auto;}
+.cl9 {margin-left: auto; width: 100%; margin-right: auto;}
+.cl10 {margin-left: 0; padding-left: auto;
+  width: 50%; 
+  padding-right: auto; margin-right: 0;}
+
+.ruler {padding: 0px; margin: 0px; border-width: 0px;}
+p.ruled {background-color: aqua; width: 400px;
+  border: solid silver 40px; border-width: 0 40px;
+  padding: 0 40px; margin: 0 40px;}
+
+
+
+

+[test cl1] This 'p' element should be offset ten pixels to the left by its 10 pixel left margin. +

+
+[cl2] +

+[test cl1] This 'p' element should be offset twenty pixels to the left by the 10 pixel left margins on itself and the containing 'div' element, since horizontal margins do not collapse. +

+
+

+[test cl3] This 'p' element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered. +

+

+[test cl4] This 'p' element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered. +

+

+[test cl5] This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered. +

+

+[test cl6] Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified. +

+

+[test cl7] Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified. +

+

+[test cl8] Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified. +

+

+[test cl9] Because this paragraph has width 100%, the auto margins become zero, so it should not be centered. +

+

+[test cl10] Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport. +

+ +
an image of a pixel ruler
+

[ruled] The border, padding, and margins for this 'p' element should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

+
an image showing the various boundaries between portions of the test element's element box
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-04.htm ##### + + + +10.3.4 Computing widths and margins: block-level, replaced elements in normal flow + + + + + + +

CSS2 Test Suite: 10.3.4 Computing widths and margins: block-level, replaced elements in normal flow

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
img {display: block; height: 15px;}
+img.cl1 {margin-right: auto; margin-left: auto; width: auto;}
+img.cl2 {margin-right: auto; margin-left: auto; width: 50%;}
+img.cl3 {margin-right: 0; margin-left: auto; width: 25px;}
+
+
+
+

+The following image, which has a class of 'cl1', should be its intrinsic width (15 pixels) and centered in the content area of its parent element. +

+test image +

+The following image, which has a class of 'cl2', should be half the width of its parent element and centered in the content area of its parent element. +

+test image +

+The following image, which has a class of 'cl3', should be 25 pixels wide and its right edge should abut the right edge of the content area of its parent element. +

+test image +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-05.htm ##### + + + +10.3.5 Computing widths and margins: floating, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.3.5 Computing widths and margins: floating, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div {float: right; background: #FDA;}
+hr {clear: right;}
+.cl1 {width: auto; margin-right: auto; margin-left: auto;}
+.cl2 {width: auto; margin-right: 20px; margin-left: 20px;}
+.cl3 {width: 25%; margin-right: auto; margin-left: auto;}
+.cl4 {width: 100%; margin-right: auto; margin-left: auto;}
+
+
+
+

+Note that the horizontal rules are used to keep tests separate, and to "reset" the float environment by providing a handy element to 'clear'. +

+ +
+ +
+[cl1] A floated element.
With two lines.
Okay, three. +
+

+The floated 'div' to the right of this text should be as skinny as possible, as its computed 'width' should be '0', and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space). +

+ +
+ +
+[cl2] A floated element.
With two lines.
Okay, three. +
+

+The floated 'div' to the right of this text should be as skinny as possible, as its computed 'width' should be '0', and have 20-pixel right and left margins. This will cause its right edge to be placed 20 pixels to the left of the right edge of the content area of its parent element, and have 20 pixels of extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of additional space). +

+ +
+ +
+[cl3] A floated element.
With two lines.
Okay, three. +
+

+The floated 'div' to the right of this text should be one-quarter the width of its parent element, and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space). +

+ +
+ +
+[cl4] A floated element.
With two lines.
Okay, three. +
+

+The floated 'div' should not be to the right of this text but instead be the width of its parent element's content area. This paragraph should appear below the float instead of to its left. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-06.htm ##### + + + +10.3.6 Computing widths and margins: floating, replaced elements + + + + + + +

CSS2 Test Suite: 10.3.6 Computing widths and margins: floating, replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
img {float: right; height: 15px;}
+hr {clear: right;}
+.cl1 {width: auto; margin-right: auto; margin-left: auto;}
+.cl2 {width: auto; margin-right: 20px; margin-left: 20px;}
+.cl3 {width: 25%; margin-right: auto; margin-left: auto;}
+.cl4 {width: 100%; margin-right: auto; margin-left: auto;}
+
+
+
+

+Note that the horizontal rules are used to keep tests separate, and to "reset" the float environment by providing a handy element to 'clear'. +

+ +
+ +test image +

+The floated 'img' to the right of this text, which has a class of 'cl1', should be its intrinsic width (15 pixels) and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space). +

+ +
+ +test image +

+The floated 'img' to the right of this text, which has a class of 'cl2', should be its intrinsic width (15 pixels) and have 20-pixel right and left margins. This will cause its right edge to be placed 20 pixels to the left of the right edge of the content area of its parent element, and have 20 pixels of extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of additional space). +

+ +
+ +test image +

+The floated 'img' to the right of this text, which has a class of 'cl3', should be one-quarter the width of its parent element, and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space). +

+ +
+ +test image +

+The floated 'img' should not be to the right of this text but instead be the width of its parent element's content area. This paragraph should appear below the float instead of to its left. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-07.htm ##### + + + +10.3.7 Computing widths and margins: absolutely positioned, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.3.7 Computing widths and margins: absolutely positioned, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div.contain {position: relative; width: auto;
+   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
+div.contain * {color: black;}
+div.contain span {position: absolute; top: 0; background: #FDA;}
+.cl1 {left: 0;}
+.cl2 {left: auto;}
+.cl3 {left: 25%; right: 25%; width: 50%;}
+.cl4 {left: 25%; right: 25%; margin-left: auto; margin-right: auto; width: 25%;}
+.cl5 {left: 0; right: 0; margin-left: 25%; margin-right: auto; width: 25%;}
+.cl6 {left: 0; right: 0;}
+.cl7 {left: 10px; right: 10px;}
+.cl8 {left: 10px; right: -10px;}
+.cl9 {left: 25%; right: 25%; margin-right: 25%; margin-left: 25%; width: 25%;}
+
+
+
+[contain] +

+This paragraph contains a 'span' with a class of 'cl1' ([cl1]) that should appear in the top left corner of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl2' ([cl2]) that should appear at the top of the containing block with its left edge aligned with the position it would have been if the 'span' had not been positioned. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl3' ([cl3]) that should appear at the top of the containing block with a width half that of the containing block, and centered horizontally within the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl4' ([cl4]) that should appear at the top of the containing block with a width one-quarter that of the containing block, and centered horizontally within the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl5' ([cl5]) that should appear at the top of the containing block with a width one-quarter that of the containing block, and with its right edge lined up with the hoizontal midpoint of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl6' ([cl6]) that should appear at the top of the containing block with a width equal to that of the containing block, centered within it. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl7' ([cl7]) that should appear at the top of the containing block with a width 20 pixels less than that of the containing block, and with its right and left edges inset 10 pixels from each edge of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl8' ([cl8]) that should appear at the top of the containing block with a width equal to that of the containing block, but shifted 10 pixels to the right. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl9' ([cl9]) that should appear at the top of the containing block with a width one-quarter that of the containing block, its left edge lined up with the horizontal midpoint of the containing block, and its right edge 25% inset from the right edge of the containing block. +

+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-03-08.htm ##### + + + +10.3.8 Computing widths and margins: absolutely positioned, replaced elements + + + + + + +

CSS2 Test Suite: 10.3.8 Computing widths and margins: absolutely positioned, replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div.contain {position: relative; width: auto;
+   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
+div.contain * {color: black;}
+div.contain img {position: absolute; top: 0; height: 15px;}
+.cl1 {left: 0;}
+.cl2 {left: auto;}
+.cl3 {left: 25%; right: 25%; width: 50%;}
+.cl4 {left: 25%; right: 25%; margin-left: auto; margin-right: auto; width: 25%;}
+.cl5 {left: 0; right: 0; margin-left: 25%; margin-right: auto; width: 25%;}
+.cl6 {left: 0; right: 0;}
+.cl7 {left: 10px; right: 10px;}
+.cl8 {left: 10px; right: -10px;}
+.cl9 {left: 25%; right: 25%; margin-right: 25%; margin-left: 25%; width: 25%;}
+
+
+
+[contain] +

+This paragraph contains an 'img' with a class of 'cl1' (test image) that should appear in the top left corner of the containing block, and have an intrinsic width (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl2' (test image) that should appear at the top of the containing block with its left edge aligned with the position it would have been if the 'img' had not been positioned, and have an intrinsic width (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl3' (test image) that should appear at the top of the containing block with a width half that of the containing block, and centered horizontally within the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl4' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, and centered horizontally within the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl5' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, and with its right edge lined up with the hoizontal midpoint of the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl6' (test image) that should appear in the top left corner of the containing block, and have an intrinsic width (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl7' (test image) that should appear near the top left corner of the containing block, with its left edge inset 10 pixels from the left edge of the containing block, and have an intrinsic width (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl8' (test image) that should appear near the top left corner of the containing block, with its left edge inset 10 pixels from the left edge of the containing block, and have an intrinsic width (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl9' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, its left edge lined up with the horizontal midpoint of the containing block, and its right edge 25% inset from the right edge of the containing block. +

+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-04a.htm ##### + + + +10.4a min-width + + + + + + +

CSS2 Test Suite: 10.4 min-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {width: 50px; min-width: 50%;}
+.cl2 {min-width: 500px;}
+
+
+
+

+[test cl1] This 'p' element has been set to have a width of 50px, but a minimum width of half its parent element's content-width. Thus its width should be half that of its parent element, unless the parent element is 100 pixels or narrower, in which case this element will be 50 pixels wide. +

+

+[test cl2] This 'p' element has been set to have a minimum width of 500px. Thus its width should never be narrower than 500 pixels, no matter how narrow its parent element's content-width may become. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-04b.htm ##### + + + +10.4b max-width + + + + + + +

CSS2 Test Suite: 10.4 max-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {width: 250px; max-width: 50%;}
+.cl2 {max-width: 500px;}
+
+
+
+

+[test cl1] This 'p' element has been set to have a width of 250px, but a maxmum width of half its parent element's content-width. Thus its width should be 250 pixels, unless the parent element is 500 pixels or narrower, in which case this element will be half as wide as its parent's content-width. +

+

+[test cl2] This 'p' element has been set to have a maximum width of 500px. Thus its width should never be wider than 500 pixels, no matter how wide its parent element's content-width may become. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-05.htm ##### + + + +10.5 height + + + + + + +

CSS2 Test Suite: 10.5 height

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {height: 50px;}
+.cl2 {height: 50%;}
+.cl2contain {height: 80px; border: 1px dotted gray;}
+.cl3 {height: 150px; background: yellow;}
+
+
+
+

+The following image has no class, and is provided as a reference point for the tests to follow. +

+[image] +

+The following image has a class of 'cl1', and should be 50 pixels tall. Since the source image is square, it should also be 50 pixels wide. +

+[image] +

+The following image has a class of 'cl2', and should be its intrinsic height, since its parent element (the 'body') does not have an explicitly assigned height. Since the source image is square, the width of the image should equal its height. +

+[image] +

+The following image has a class of 'cl2' and is contained in a 'div' with a class of 'cl2contain'. The image should be half the height of the content-height of 'cl2contain'. Since the source image is square, the width of the image should equal its height. +

+
+[image] +
+

+This 'p' element contains a 'span' element that has a class of 'cl3'. The 'span' is here: [cl3]. Since height does not apply to inline non-replaced elements, the 'span' should not be 150 pixels tall. If the 'span' is 150 pixels tall, the test has been failed. +


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-06-01.htm ##### + + + +10.6.1 Computing heights and margins: inline, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.6.1 Computing heights and margins: inline, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: #9F9;}
+.cl1 {height: 200px;}
+.cl2 {padding: 10px 0;}
+.cl3 {border: 10px solid green; border-width: 10px 0;}
+.cl4 {margin: 10px 0;}
+.cl5 {padding: 10px 0; border: 10px solid green; border-width: 10px 0; margin: 10px 0;}
+.cl6 {margin: auto 0;}
+
+
+
+

+This 'p' element contains a 'span' element with a class of 'test cl1'. This elements is here: +[test cl1] this is a span. The test span's height should be equal to the size of the content, and it should not be 200 pixels tall, as 'height' is ignored for inline non-replaced elements. The top and bottom padding, borders, and margins should all have zero width. +

+

+This 'p' element contains a 'span' element with a class of 'test cl2'. This elements is here: +[test cl2] this is a span. The test span's top and bottom padding should be 10 pixels tall. Padding on non-replaced elements does not increase line height, and so the padding may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." Therefore the top and bottom padding may appear to be zero. +

+

+This 'p' element contains a 'span' element with a class of 'test cl3'. This elements is here: +[test cl3] this is a span. The test span's top and bottom borders should be 10 pixels tall (and solid green). Borders on non-replaced elements do not increase line height, and so the borders may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." Therefore the top and bottom borders may not appear. +

+

+This 'p' element contains a 'span' element with a class of 'test cl4'. This elements is here: +[test cl4] this is a span. The test span's top and bottom margins should be 10 pixels tall. Margins on non-replaced elements do not increase line height, and so the top and bottom margins should have no visible effect on layout. +

+

+This 'p' element contains a 'span' element with a class of 'test cl5'. This elements is here: +[test cl5] this is a span. The test span's top and bottom padding, borders, and margins should be 10 pixels tall. Padding and borders on non-replaced elements do not increase line height, and so they may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." The margins should have no visible effect on layout in either case. +

+

+This 'p' element contains a 'span' element with a class of 'test cl4'. This elements is here: +[test cl4] this is a span. The test span's top and bottom margins should have no height, which means no visible effect on line layout. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-06-02.htm ##### + + + +10.6.2 Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements + + + + + + +

CSS2 Test Suite: 10.6.2 Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.bookend {background: #FCC;}
+.test {background: #9F9;}
+.cl1 {height: 30px;}
+.cl2 {padding: 10px 0;}
+.cl3 {border: 10px solid green; border-width: 10px 0;}
+.cl4 {margin: 10px 0;}
+.cl5 {height: 30px; padding: 10px 0; border: 10px solid green; border-width: 10px 0; margin: 10px 0;}
+.cl6 {height: auto;}
+
+
+
+

+This 'p' element contains an 'img' element with a class of 'test cl1'. The image is here: +image. The image's height should be 30 pixels. The top and bottom padding, borders, and margins should all have zero width. +

+

+This 'p' element contains an 'img' element with a class of 'test cl2'. The image is here: +image. The image's top and bottom padding should each be 10 pixels wide. +

+

+This 'p' element contains an 'img' element with a class of 'test cl3'. The image is here: +image. The image's top and bottomborders should each be 10 pixels wide (and solid green). +

+

+This 'p' element contains an 'img' element with a class of 'test cl4'. The image is here: +image. The image's top and bottom margins should each be 10 pixels wide. This will raise the image 10 pixels, as well as increase the height of the line box to be 10 pixels above the top of the image (assuming the surrounding text is smaller than the image. +

+

+This 'p' element contains an 'img' element with a class of 'test cl5'. The image is here: +image. The image's top and bottom padding, border, and margins should each be 10 pixels wide, and the image's height should be 30 pixels. +

+

+This 'p' element contains an 'img' element with a class of 'test cl6'. The image is here: +image. The image's height should be equal to its intrinsic height, which is 20 pixels. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-06-03.htm ##### + + + +10.6.3 Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.6.3 Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
p {border: 1px dotted gray;}
+.cl1 {margin-top: auto; margin-bottom: auto;}
+.cl2 {margin-top: 10px; margin-bottom: 10px;}
+.cl3 {height: auto;}
+.cl4 {height: 25px; overflow: hidden;}
+hr {clear: right;}
+div {float: right; width: 25%; background: #FDA;}
+
+
+
+

+[cl1] This paragraph should have no top or bottom margins, since the 'auto' values are replaced with '0'. +

+

+[cl1] This paragraph should have no top or bottom margins, since the 'auto' values are replaced with '0'. +

+

+[cl2] This paragraph should have 10-pixel top and bottom margins. Remember that vertically adjacent margins "collapse." +

+

+[cl2] This paragraph should have 10-pixel top and bottom margins. Remember that vertically adjacent margins "collapse." +

+

+[cl3] The height of this paragraph depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be. +

+

+[cl3] The height of this paragraph depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. +

+

+[cl4] The height of this paragraph is 25 pixels. If the content is taller than that, it will be treated according to the value of 'overflow' (which is in this test is set to 'hidden'). Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. +

+ +
+ +
+[cl1] A floated element.
With two lines.
Okay, three. +
+

+The floated 'div' to the right of this text should be one-quarter the width of its parent element's content area. +

+ +
+ +
+[cl2] A floated element. +
+

+The floated 'div' to the right of this text should be one-quarter the width of its parent element's content area, with 10-pixel top and bottom margins. This will push it downaward 10 pixels, and prevent any inline content from appearing less than 10 pixels from the bottom of its content area. note that line layout may cause more than 10 pixels to appear between the bottom edge of the floated element's content area and inline content beneath it. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. +

+ +
+ +
+[cl3] A floated element.
With two lines.
Okay, three. +
+

+The height of the floated 'div' to the right of this text depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be. +

+ +
+ +
+[cl3] A floated element. +
+

+The height of the floated 'div' to the right of this text depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be. +

+ +
+ +
+[cl4] A floated element.
With two lines.
Okay, three. +
+

+The height of the floated 'div' to the right of this text is 25 pixels. It effectively "shrink-wraps" the content, regardless of how short or long it might be. If the content is taller than that, it will be treated according to the value of 'overflow' (which is in this test is set to 'hidden'). +

+ +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-06-04.htm ##### + + + +10.6.4 Computing heights and margins: absolutely positioned, non-replaced elements + + + + + + +

CSS2 Test Suite: 10.6.4 Computing heights and margins: absolutely positioned, non-replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div.contain {position: relative; width: auto; height: 100px;
+   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
+div.contain * {color: black;}
+div.contain p {margin: 0.5em 0 0.5em 3em;}
+div.contain span {position: absolute; left: 0; background: #FDA;}
+.cl1 {top: 0;}
+.cl2 {top: auto;}
+.cl3 {top: 25%; bottom: 25%; height: 50%;}
+.cl4 {top: 25%; bottom: 25%; margin-top: auto; margin-bottom: auto; height: 25%;}
+.cl5 {top: 0; bottom: 0; margin-top: 25px; margin-bottom: auto; height: 25%;}
+.cl6 {top: 0; bottom: 0;}
+.cl7 {top: 10px; bottom: 10px;}
+.cl8 {top: 10px; bottom: -10px;}
+.cl9 {top: 25%; bottom: 25%; margin-top: 25px; margin-bottom: 25px; height: 25%;}
+
+
+
+[contain] +

+This paragraph contains a 'span' with a class of 'cl1' ([cl1]) that should appear in the top left corner of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl2' ([cl2]) that should appear at the left edge of the containing block with its top edge aligned with the position it would have been if the 'span' had not been positioned. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl3' ([cl3]) that should appear at the left edge of the containing block with a height half that of the containing block, and centered vertically within the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl4' ([cl4]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and centered vertically within the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl5' ([cl5]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and with its bottom edge lined up with the vertical midpoint of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl6' ([cl6]) that should appear at the left edge of the containing block with a height equal to that of the containing block, centered within it. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl7' ([cl7]) that should appear at the left edge of the containing block with a height 20 pixels less than that of the containing block, and with its top and bottom edges inset 10 pixels from each edge of the containing block. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl8' ([cl8]) that should appear at the left edge of the containing block with a height equal to that of the containing block, but shifted 10 pixels to downward. +

+
+ +
+[contain] +

+This paragraph contains a 'span' with a class of 'cl9' ([cl9]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, its top edge lined up with the vertical midpoint of the containing block, and its bottom edge 25% inset from the bottom edge of the containing block. +

+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-06-05.htm ##### + + + +10.6.5 Computing heights and margins: absolutely positioned, replaced elements + + + + + + +

CSS2 Test Suite: 10.6.5 Computing heights and margins: absolutely positioned, replaced elements

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div.contain {position: relative; width: auto; height: 100px;
+   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
+div.contain * {color: black;}
+div.contain p {margin: 0.5em 0 0.5em 20px;}
+div.contain img {position: absolute; left: 0; width: 15px;}
+.cl1 {top: 0;}
+.cl2 {top: auto;}
+.cl3 {top: 25%; bottom: 25%; height: 50%;}
+.cl4 {top: 25%; bottom: 25%; margin-top: auto; margin-bottom: auto; height: 25%;}
+.cl5 {top: 0; bottom: 0; margin-top: 25px; margin-bottom: auto; height: 25%;}
+.cl6 {top: 0; bottom: 0;}
+.cl7 {top: 10px; bottom: 10px;}
+.cl8 {top: 10px; bottom: -10px;}
+.cl9 {top: 25%; bottom: 25%; margin-top: 25px;  margin-bottom: 25%;height: 25%;}
+
+
+
+[contain] +

+This paragraph contains an 'img' with a class of 'cl1' (test image) that should appear in the top left corner of the containing block, and have an intrinsic height (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl2' (test image) that should appear at the left edge of the containing block with its top edge aligned with the position it would have been if the 'img' had not been positioned, and have an intrinsic height (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl3' (test image) that should appear at the left edge of the containing block with a height half that of the containing block, and centered vertically within the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl4' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and centered vertically within the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl5' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and with its bottom edge lined up with the vertical midpoint of the containing block. +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl6' (test image) that should appear in the top left corner of the containing block, and have an intrinsic height (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl7' (test image) that should appear near the top left corner of the containing block, with its top edge inset 10 pixels from the top edge of the containing block, and have an intrinsic height (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl8' (test image) that should appear near the top left corner of the containing block, with its top edge inset 10 pixels from the top edge of the containing block, and have an intrinsic height (15 pixels). +

+
+ +
+[contain] +

+This paragraph contains an 'img' with a class of 'cl9' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, its top edge lined up with the vertical midpoint of the containing block, and its bottom edge 25% inset from the bottom edge of the containing block. +

+
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-07a.htm ##### + + + +10.7a min-height + + + + + + +

CSS2 Test Suite: 10.7 min-height

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {height: 50%; min-height: 100px;}
+.cl2 {min-height: 50%;}
+.cl2contain {height: 80px; border: 1px dotted gray;}
+
+
+
+

+[test cl1] This 'p' element has a percentage height, which should be treated as 'auto', and a minimum height of 100 pixels. +

+

+The following 'div' has a class of 'cl2contain', and contains an image with a class of 'cl2'. The image should be a minimum of half the height of the content-height of the 'div' that contains it. +

+
+test image +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-07b.htm ##### + + + +10.7b max-height + + + + + + +

CSS2 Test Suite: 10.7 max-height

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-color: silver;}
+.cl1 {height: 250px; max-height: 100px;}
+.cl2 {max-height: 50%;}
+.cl2contain {height: 10px; border: 1px dotted gray;}
+
+
+
+

+[test cl1] This 'p' element has a height of 250 pixels, and a maximum height of 100 pixels. It should thus be no more than 100 pixels tall. +

+

+The following 'div' has a class of 'cl2contain', and contains an image with a class of 'cl2'. The image should be a maximum of half the height of the content-height of the 'div' that contains it. +

+
+test image +
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-08a.htm ##### + + + +10.8a line-height + + + + + + +

CSS2 Test Suite: 10.8 line-height

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
p span {background-color: #DDD;}
+.cl0 {font-size: 15px;}
+.cl1 {line-height: -1em; font-size: 15px;}
+.cl2 {line-height: 30px; font-size: 15px;}
+.cl3 {line-height: 200%; font-size: 15px;}
+.cl4 {line-height: 2; font-size: 15px;}
+div {border: 1px dotted gray; background: white;
+   margin: 0.5em; padding: 0.25em;}
+.shrink {font-size: 66%;}
+.grow {font-size: 150%;}
+.cl5 {line-height: 1.2em; font-size: 15px;}
+.cl6 {line-height: 1.2; font-size: 15px;}
+.huge {font-size: 200%; border: 1px dotted red; background: none;}
+.cl5 img {height: 30px;}
+
+
+

+[cl0] A 'p' element with browser-default 'line-height'. Its 'font-size' has been set to 15px, the same as the other tests in this page. This element is included largely for reference purposes, and is not intended to demonstrate a particular aspect of the CSS specification. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+

+[cl1] This 'p' element should have a normal line-height, because negative values are not permitted for 'line-height'. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+

+[cl2] This 'p' element should have a 'line-height' of 30 pixels. This will lead to a separation of 30 pixels between each baseline in the element, although the distance between actual character glyphs cannot be predicted. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+

+[cl2] This 'p' element should have a 'line-height' of 30 pixels. This will lead to a separation of 30 pixels between each baseline in the element, and a separation of 15 pixels between the silver-backed areas. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+

+[cl3] This 'p' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+

+[cl4] This 'p' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +

+
+[cl3] This 'div' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+[shrink] This text should have a font-size two-thirds that of the parent element, but the separation between baselines in this element should still be 30 pixels, as the value '200%' on the parent element causes a computed value to be inherited. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+
+[grow] This text should have a font-size half again as large as that of the parent element, but the separation between baselines in this element should still be 30 pixels, as the value '200%' on the parent element causes a computed value to be inherited. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+This is the end of the 'cl3' content. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+ +
+[cl4] This 'div' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+[shrink] This text should have a font-size two-thirds that of the parent element, and the separation between baselines should also be two-thirds the parent; in other words, 20 pixels. This happens because the value '2' is inherited as a "scaling factor" that is multiplied by the value of the element's 'font-size' (in this case, 10px * 2). Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+
+[grow] This text should have a font-size half again as large as that of the parent element, and the separation between baselines should also be half again that of the parent; in other words, 45 pixels. This happens because the value '2' is inherited as a "scaling factor" that is multiplied by the value of the element's 'font-size' (in this case, 22.5px * 2). Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+This is the end of the 'cl4' content. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text. +
+

+[cl5] This 'p' element contains an inline element that is twice the size of the 'p' element's text, but it does not have an increased line-height. Thus, the inline element's content area will overlap other lines in the parent element. The inline element is [huge]. Note that the baselines of both the 'p' and the 'span' are aligned, since that's the default behavior. The overlap can go both upward and downward; that is, preceding and succeeding lines can be overlapped. The height of the line in which the 'span' appears may also be taller than normal due to the inline box of the 'span'. +

+

+[cl6] This 'p' element contains an inline element that is twice the size of the 'p' element's text, and which will inherit the scaling factor for its line-height. Thus, the inline element's content area will not overlap other lines in the parent element. The inline element is [huge]. Note that the line in which the inline element appears is increased in height to account for its presence. This does not increase the content area of the line of text, as the silver background demonstrates. +

+

+[cl5] This 'p' element contains an inline image that is twice the height of the 'p' element's text. Thus, the images will increase the height of the line in which it appears, and will not overlap content in lines above or below it. The inline element is test image. Note that the bottom of the 'img' is aligned with the baseline of the 'p', since that's the default behavior. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec10-08b.htm ##### + + + +10.8b vertical-align + + + + + + +

CSS2 Test Suite: 10.8 vertical-align

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
p {font-size: 15px;}
+p img {height: 50px; width: 15px;}
+.cl1 {vertical-align: sub;}
+.cl2 {vertical-align: super;}
+.cl3 {vertical-align: top; font-size: 15px;}
+.cl4 {vertical-align: text-top; font-size: 15px;}
+.cl5 {vertical-align: middle; font-size: 15px;}
+.cl6 {vertical-align: bottom; font-size: 15px;}
+.cl7 {vertical-align: text-bottom; font-size: 15px;}
+.cl8 {vertical-align: baseline; font-size: 15px;}
+.cl9 {vertical-align: 50%; font-size: 15px; line-height: 20px;}
+p.explain {margin-top: 2em; padding-top: 0.5em; border-top: 2px groove silver;}
+p.ttopalign img, span.ttopalign {vertical-align: text-top;}
+p.topalign img, span.topalign {vertical-align: top;}
+p.midalign img, span.midalign {vertical-align: middle;}
+big {font-size: 20px;}
+small {font-size: 15px;}
+img.px10 {height: 10px;}
+img.px15 {height: 15px;}
+img.px20 {height: 20px;}
+img.px35 {height: 35px;}
+img.px50 {height: 50px;}
+img.px65 {height: 65px;}
+img.px90 {height: 90px;}
+
+
+
+

+test image[cl1] The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element. +

+

+test image[cl2] The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element. +

+

+test image[cl3] The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle). +

+

+test image + +[cl4] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line. + +

+

+test image + +[cl6] The first four words in this sentence should be 15px in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line. + +

+

+test image + +[cl7] The first eight words ("eight" has a descender) in this sentence should be 15px in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line. + +

+

+test image + +[cl8] The first four words in this sentence should be 15px in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line. + +

+

+test image[cl9] The first four words in this sentence should have a font-size of 15px and a line-height of 20px; they are also 50%-aligned, which should raise them 10px relative to the natural baseline. +

+ +

+In the following paragraph, all images should be aligned with the top of the 15-pixel text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value). +

+

+[ttopalign] This paragraph +test image +contains many images +test image +of varying heights +test image +and widths +test image +all of which +test image +should be aligned +test image +with the top of +test image +a 15-pixel text element +test image +regardless of the line in which +test image +the images appear. +test image +

+ +

+In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value). +

+

+[midalign] This paragraph +test image +contains many images +test image +of varying heights +test image +and widths +test image +all of which +test image +should be aligned +test image +with the middle of +test image +a 15-pixel text element +test image +regardless of the line in which +test image +the images appear. +test image +

+ +

+In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been 'span'ned appropriately in order to cause this to happen. +

+

[topalign] +This paragraph +test image +contains many images +test image +and some text +test image +of varying heights +test image +and widths +test image +all of which +test image +should be aligned +test image +with the top of +test image +the tallest element in +test image +whichever line the elements appear. +test image +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec11-01-01.htm ##### + + + +11.1.1 overflow + + + + + + +

CSS2 Test Suite: 11.1.1 overflow

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
div.test {width: 100px; height: 100px; border: thin solid red;}
+blockquote {width: 125px; height: 100px; margin-top: 50px; margin-left: 50px; border: thin dashed black;}
+div.attributed-to {text-align: right; }
+
+div.cl1 {overflow: visible;}
+div.cl2 {overflow: hidden;}
+div.cl3 {overflow: scroll;}
+div.cl4 {overflow: auto;}
+
+
+
+
+
+

[cl1] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

+
- Groucho Marx
+
+
+ +
+
+

[cl2] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

+
- Groucho Marx
+
+
+ +
+
+

[cl3] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

+
- Groucho Marx
+
+
+ +
+
+

[cl4] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

+
- Groucho Marx
+
+
+ +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec11-01-02.htm ##### + + + +11.1.2 clip + + + + + + +

CSS2 Test Suite: 11.1.2 clip

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {clip: rect(5px 10px 10px 5px); padding: 0; border: 1px solid gray; background: #FCC;}
+
+
+
+

+Note: the behavior of 'clip' changed radically in CSS2.1. This test is provided as a historical curiosity. Browsers are not expected to pass it. Even those that pass it under 2.1 may appear to fail this test, and vice versa. The results seen on this page should not be taken as definitive. +

+ +

+[cl1] The content of this 'p' element should be clipped slightly: 5 pixels on the top, 10 pixels to the right, 10 pixels on the bottom, and 5 pixels to the left. This will cause the text to be cut off to a small extent on each side of the element. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec11-02.htm ##### + + + +11.2 visibility + + + + + + +

CSS2 Test Suite: 11.2 visibility

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {visibility: visible;}
+.cl2 {visibility: hidden;}
+.cl3 {visibility: collapse;}
+table {background: silver;}
+table td {background: #FF9;}
+
+
+

+The following image has a class of 'cl1' and so should be visible: image. It should affect layout as normal. +

+

+The following image has a class of 'cl2' and so should not be visible: image. It should affect layout as normal even though it cannot be seen. +

+

+The following image has a class of 'cl3' and so should not be visible: image. It should affect layout as normal even though it cannot be seen. +

+ +

+In the following table, the cells of the second row should be invisible, but the space the row would have occupied should still be held open. The third row should be removed from the table altogether, and its space should not be held open. +

+ + + + + + +
r1c1r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
r4c1r4c2r4c3
r5c1r5c2r5c3

[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-01.htm ##### + + + +12.1 :before and :after + + + + + + +

CSS2 Test Suite: 12.1 :before and :after

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
BODY:after {
+   content: "The End";
+   display: block; margin-top: 2em;
+   text-align: center; color: maroon;
+}
+P.note:before {content: "Note";}
+P.note {color: purple;}
+
+.fox1:before {content: "The quick brown fox ";}
+.fox2:after {content: " jumped over the lazy dog.";}
+.fox3:after {content: " the lazy dog.";}
+
+
+
+

+A plain, unstyled paragraph. Note that, at the bottom of this page, there should be a block-level box containing the words "The End" centered, and colored maroon. +

+

+[note] This paragraph should have generated content inserted at its beginning, and the entire element (including the generated content) should be purple. +

+ +
+ +

[fox1] jumped over the lazy dog.

+

[fox2] The quick brown fox

+

[fox1 fox3] jumped over

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-02.htm ##### + + + +12.2 content + + + + + + +

CSS2 Test Suite: 12.2 content

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
img:before {content: attr(alt);}
+h1:before {
+   display: block;
+   text-align: center;
+   content: "chapter\Ahoofdstuk\Achapitre";
+}
+
+
+

+The 'alt' text of the images on this page should appear before the images themselves. +

+Can you see me? +Can you feel me? +...there has to be a trick. +
+

An H1 element.


[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-04-01.htm ##### + + + +12.4.1 quotes + + + + + + +

CSS2 Test Suite: 12.4.1 quotes

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
q:before {content: open-quote;}
+q:after  {content: close-quote;}
+.cl1 {quotes: '"' '"' "'" "'";}
+.cl2 {quotes: "" "" "<" ">";}
+.cl3 {quotes: "[[[" "]]]" "((" "))" "*-" "-*";}
+.cl4 {quotes: "\201C" "\201D" "\2018" "\2019"; }
+
+
+
+

+This 'p' element contains a quote element, which is provided to determine the user agent's default handling of the element: I hate quotations. (Ralph Waldo Emerson) +

+

+[cl1] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember. I didn't really believe him, but what could I do? +

+

+[cl2] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember. I didn't really believe him, but what could I do? +

+

+[cl3] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember anyone saying, I need some help, or else I would have helped. I didn't really believe him, but what could I do? +

+

+[cl4] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember anyone saying, I need some help, or else I would have helped. I didn't really believe him, but what could I do? +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-05a.htm ##### + + + +12.5a counter-reset + + + + + + +

CSS2 Test Suite: 12.5 counter-reset

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
span:before {content: counter(ct1) "|" counter(ct2) "|" counter(ct3) "... ";}
+li span:before {counter-increment: ct1; counter-reset: 0;}
+li li span:before {counter-increment: ct2 2; counter-reset: 0;}
+li li li span:before {counter-increment: ct3 -3; counter-reset: 0;}
+
+
+
+

+The list items in the following set of lists all have 'span' elements, and each 'span' should be preceded with generated content in the form "a|b|c... " where the letters are incremented numbers. "a" numbers increment in ones, "b" in twos, and "c" in negative threes. Note that counters are reset for each sublist. +

+ + + +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-05b.htm ##### + + + +12.5b counter-increment + + + + + + +

CSS2 Test Suite: 12.5 counter-increment

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
span:before {content: counter(ct1) "|" counter(ct2) "|" counter(ct3) "... ";}
+li span:before {counter-increment: ct1;}
+li li span:before {counter-increment: ct2 2;}
+li li li span:before {counter-increment: ct3 -3;}
+
+
+
+

+The list items in the following set of lists all have 'span' elements, and each 'span' should be preceded with generated content in the form "a|b|c... " where the letters are incremented numbers. "a" numbers increment in ones, "b" in twos, and "c" in negative threes. Note that counters are not reset for each sublist, or at any point, and so should use the default '0' as their base point. +

+ + + +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-06-01.htm ##### + + + +12.6.1 marker-offset + + + + + + +

CSS2 Test Suite: 12.6.1 marker-offset

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
li:before {display: marker; marker-offset: 50px; width: 20px; border: 1px solid gray; background: #FF9;}
+li {margin-left: 100px; padding-left: 0; border: 1px dotted gray; background: silver;}
+
+
+
+ +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-06-02a.htm ##### + + + +12.6.2a list-style-type + + + + + + +

CSS2 Test Suite: 12.6.2 list-style-type

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl0 {list-style-type: none;}
+.cl1 {list-style-type: disc;}
+.cl2 {list-style-type: circle;}
+.cl3 {list-style-type: square;}
+.cl4 {list-style-type: decimal;}
+.cl5 {list-style-type: decimal-leading-zero;}
+.cl6 {list-style-type: lower-roman;}
+.cl7 {list-style-type: upper-roman;}
+.cl8 {list-style-type: lower-greek;}
+.cl9 {list-style-type: lower-alpha;}
+.cl10 {list-style-type: lower-latin;}
+.cl11 {list-style-type: upper-alpha;}
+.cl12 {list-style-type: upper-latin;}
+.cl13 {list-style-type: hebrew;}
+.cl14 {list-style-type: armenian;}
+.cl15 {list-style-type: georgian;}
+.cl16 {list-style-type: cjk-ideographic;}
+.cl17 {list-style-type: hiragana;}
+.cl18 {list-style-type: katakana;}
+.cl19 {list-style-type: hiragana-iroha;}
+.cl20 {list-style-type: katakana-iroha;}
+.parent {list-style-type: square;}
+.inh1 {list-style-type: circle;}
+
+
+
+
    +
  1. [cl0] This ordered list... +
  2. ...should have no markers... +
  3. ...next to its list items. +
+ + + +
    +
  1. [cl4] This ordered list... +
  2. ...should have decimal markers... +
  3. ...next to its list items. +
+
    +
  1. [cl5] This ordered list... +
  2. ...should have decimal-leading-zero markers... +
  3. ...next to its list items. +
+
    +
  1. [cl6] This ordered list... +
  2. ...should have lower-roman markers... +
  3. ...next to its list items. +
+
    +
  1. [cl7] This ordered list... +
  2. ...should have upper-roman markers... +
  3. ...next to its list items. +
+
    +
  1. [cl8] This ordered list... +
  2. ...should have lower-greek markers... +
  3. ...next to its list items. +
+
    +
  1. [cl9] This ordered list... +
  2. ...should have lower-alpha markers... +
  3. ...next to its list items. +
+
    +
  1. [cl10] This ordered list... +
  2. ...should have lower-latin markers... +
  3. ...next to its list items. +
+
    +
  1. [cl11] This ordered list... +
  2. ...should have upper-alpha markers... +
  3. ...next to its list items. +
+
    +
  1. [cl12] This ordered list... +
  2. ...should have upper-latin markers... +
  3. ...next to its list items. +
+
    +
  1. [cl13] This ordered list... +
  2. ...should have hebrew markers... +
  3. ...next to its list items. +
+
    +
  1. [cl14] This ordered list... +
  2. ...should have armenian markers... +
  3. ...next to its list items. +
+
    +
  1. [cl15] This ordered list... +
  2. ...should have georgian markers... +
  3. ...next to its list items. +
+
    +
  1. [cl16] This ordered list... +
  2. ...should have cjk-ideographic markers... +
  3. ...next to its list items. +
+
    +
  1. [cl17] This ordered list... +
  2. ...should have hiragana markers... +
  3. ...next to its list items. +
+
    +
  1. [cl18] This ordered list... +
  2. ...should have katakana markers... +
  3. ...next to its list items. +
+
    +
  1. [cl19] This ordered list... +
  2. ...should have hiragana-iroha markers... +
  3. ...next to its list items. +
+
    +
  1. [cl20] This ordered list... +
  2. ...should have katakana-iroha markers... +
  3. ...next to its list items. +
+

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-06-02b.htm ##### + + + +12.6.2b list-style-image + + + + + + +

CSS2 Test Suite: 12.6.2 list-style-image

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {list-style-image: url(pix/orancirc.gif);}
+.cl2 {list-style-image: none;}
+.parent {list-style-image: none;}
+.inh1 {list-style-image: url(pix/orancirc.gif);}
+
+
+
+ + +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-06-02c.htm ##### + + + +12.6.2c list-style-position + + + + + + +

CSS2 Test Suite: 12.6.2 list-style-position

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {list-style-position: outside;}
+.cl2 {list-style-position: inside;}
+.parent {list-style-position: inside;}
+.inh1 {list-style-position: outside;}
+
+
+
+ +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec12-06-02d.htm ##### + + + +12.6.2d list-style + + + + + + +

CSS2 Test Suite: 12.6.2 list-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {list-style: lower-roman;}
+.cl2 {list-style: inside upper-alpha;}
+.cl3 {list-style: outside url(pix/orancirc.gif) circle;}
+.cl3 .li-test {list-style-image: none;}
+.parent {list-style: inside disc url(pix/orancirc.gif);}
+.inh1 {list-style: square outside;}
+
+
+
+
    +
  1. [cl1] This list items in this ordered list...
  2. +
  3. ...should have lower-roman markers outside the content...
  4. +
  5. ...for each item in the list.
  6. +
+
    +
  1. [cl2] This list items in this ordered list...
  2. +
  3. ...should have upper-alpha markers inside the content...
  4. +
  5. ...for each item in the list.
  6. +
+ +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-01.htm ##### + + + +14.1 color + + + + + + +

CSS2 Test Suite: 14.1 color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: green;}.inh1 {color: red;}
+
+
+
+

+This 'p' element has no styles assign to it, and serves as a reference point. +

+

+This 'p' element should be green. +

+
+[parent] This 'div' element has no explicitly assigned styles. +
+[inh1] This 'div' element should have the same text color as its parent, as it has a style attribute set to inherit the color value. If it is red, the 'inherit' test has been failed. [/inh1] +
+This is the end of the parent 'div' element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01a.htm ##### + + + +14.2.1a background-color + + + + + + +

CSS2 Test Suite: 14.2.1 background-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {background-color: green;}
+.cl2 {background-color: transparent;}
+.parent {background-color: silver;}
+.inh1 {background-color: red;}
+
+
+
+

+[cl1] This 'p' element should have a green background that completely fills its content-area. +

+

+[cl2] This 'p' element should have a transparent background that completely fills its content-area; this will allow the background of any ancestor elements that encompass it to "shine through." +

+

+[cl1] This 'p' element contains a 'span' that has been given a class of 'cl2'. The transparent background of [cl2]the inline 'span' should allow the 'p' element's green background to "shine through." +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a silver background. +
+[inh1] This 'div' element should have the same silver background as its parent, as it has a style attribute set to inherit the background-color value. If the background is red, the 'inherit' test has been failed. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01b.htm ##### + + + +14.2.1b background-image + + + + + + +

CSS2 Test Suite: 14.2.1 background-image

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {background-image: url(pix/smgr-bg.gif);}
+.cl2 {background-image: none;}
+.parent {background-image: url(pix/crosshair2.gif);}
+.inh1 {background-image: url(pix/redsqr.gif);}
+
+
+
+

+[cl1] This 'p' element should have a background that completely fills its content-area. This background is a small green grid image that has been repeatedly "tiled" throughout the background area of the element. +

+

+[cl2] This 'p' element should have a transparent background that completely fills its content-area; this will allow the background of any ancestor elements that encompass it to "shine through." +

+

+[cl1] This 'p' element contains a 'span' that has been given a class of 'cl2'. The transparent background of [cl2]the inline 'span' should allow the 'p' element's green-grid background to "shine through." +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a background pattern of a crosshair image. +
+[inh1] This 'div' element should have the same crosshair-tiled background as its parent, as it has a style attribute set to inherit the background-image value. If the background is red, the 'inherit' test has been failed. If the crosshair pattern does not re-start itself in the top left corner of this child 'div', then the test has also been failed; by inheriting the image, this 'div' has a pattern independent of its parent. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01c.htm ##### + + + +14.2.1c background-repeat + + + + + + +

CSS2 Test Suite: 14.2.1 background-repeat

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-image: url(pix/smgr-bg.gif);}
+.cl1 {background-repeat: no-repeat;}
+.cl2 {background-repeat: repeat-x;}
+.cl3 {background-repeat: repeat-y;}
+.cl4 {background-repeat: repeat;}
+.parent, .inh1 {background-image: url(pix/smgr-bg.gif);}
+.parent {background-repeat: no-repeat;}
+.inh1 {background-repeat: repeat;}
+
+
+
+

+[test] This 'p' element should have a green grid as its background, extending through the content-area of the element. +

+

+[test cl1] This 'p' element should have a green image in the top left corner of the element's background area. +

+

+[test cl2] This 'p' element should have a green stripe running along the top edge of the element's background area. +

+

+[test cl3] This 'p' element should have a green stripe running down the left side of the element's background area. +

+

+[test cl4] This 'p' element should have a green grid throughout the entirety of the element's background area. +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a single small green image in its top left corner. +
+[inh1] This 'div' element should have a single green image in its top left corner, the same as its parent, as it has a style attribute set to inherit the background-image value. If the background is filled with a green grid, the 'inherit' test has been failed. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01d.htm ##### + + + +14.2.1d background-attachment + + + + + + +

CSS2 Test Suite: 14.2.1 background-attachment

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
body {background-image: url(pix/test1.jpg); background-attachment: fixed;}
+.test {background-image: url(pix/test2.jpg); background-attachment: fixed;
+  padding: 50px; border: 1px dotted silver;}
+.cl1 {background-repeat: repeat-x;}
+.cl2 {background-attachment: scroll;}
+.parent, .inh1 {background-image: url(pix/test2.jpg);}
+.parent {background-attachment: fixed;}
+.inh1 {background-attachment: scroll;}
+
+
+

+The background of this document should be a repeated pattern of the word "TEST" at 45-degree angles. This background should fill the entire viewport and not scroll when the document itself is scrolled. This document will be extra-long in order to create a scrolling effect, but consider resizing the browser window if your display area is so large that the entire document can be seen without scrolling. +

+

+[test] The background of this 'p' element should be filled with a tiled "TEST" pattern where the letters in the words "TEST" are filled in. This background should line up precisely with the background of the 'body' element. As the document is scrolled, the effect should be that of a moving window through which the filled-in "TEST" background is visible. The background of this element and that of the 'body' element should always line up precisely, and should never move along with the scrolling document. +

+

+[test cl1] The background of this 'p' element should be transparent on document load, so the 'body' background will "shine through" this element. As the document is scrolled, pay attention when this element reaches the top of the browser window. As it scrolled past the top of the window, the "TEST" pattern should shift to a single horizontal stripe of filled-in letters. Depending on the height of this element, it may be possible that the single row is visible at once, or only portions of it may be visible. +

+

+[test cl1] The background of this 'p' element should be a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in. This tile will start at the top left corner of the element's background area. As the document is scrolled, the pattern will scroll along with it. The pattern may or may not line up with the 'body' element's background, but it is most likely that it will not. If it does, resize the browser window so the patterns do not line up. +

+

+A quotation of the relevant section of the CSS2 specification: +

+
+
+'background-attachment' +
+ + +
Value:  scroll | fixed | inherit +
Initial:  scroll +
Applies to:  all elements +
Inherited:  no +
Percentages:  N/A +
Media:  visual +
+
+
+ +

If a background image is specified, this property specifies +whether it is fixed with regard to the viewport ('fixed') or scrolls along with the +document ('scroll').

+

Even if the image is fixed, it is still only visible when it is in +the background or padding area of the element. Thus, unless the image +is tiled ('background-repeat: repeat'), it may be invisible.

+ +

+Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in. This background should align with the background pattern of the 'body' element at all times. +
+[inh1] This 'div' element should have a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in, the same as its parent, as it has a style attribute set to inherit the background-attachment value. If the background pattern begins at the top left corner of this element's background area, or it scrolls along with the document, or both, the test has been failed. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01e.htm ##### + + + +14.2.1e background-position + + + + + + +

CSS2 Test Suite: 14.2.1 background-position

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background-image: url(pix/smgr-bg.gif); background-repeat: no-repeat;
+  border: 1px dashed gray;}
+.cl1 {background-position: center;}
+.cl2 {background-position: right top;}
+.cl3 {background-position: bottom left;}
+.cl4 {background-position: center left;}
+.cl5 {background-position: center top;}
+.cl6 {background-position: 50% 50%;}
+.cl7 {background-position: 10px 10px;}
+.cl8 {background-position: 10px 50%;}
+.cl9 {background-position: 50% 10px;}
+.cl10 {background-position: top 50%;}
+.parent, .inh1 {background-image: url(pix/smgr-bg.gif); background-repeat: no-repeat;}
+.parent {background-position: top right;}
+.inh1 {background-position: center left;}
+
+
+

+[test] This 'p' element should have a single small green image in the top left corner of its background area. +

+

+[test cl1] This 'p' element should have a single small green image in the center of its background area. +

+

+[test cl2] This 'p' element should have a single small green image in the top right corner of its background area. +

+

+[test cl3] This 'p' element should have a single small green image in the bottom left corner of its background area. +

+

+[test cl4] This 'p' element should have a single small green image in the center left of its background area. +

+

+[test cl5] This 'p' element should have a single small green image top center of its background area. +

+

+[test cl6] This 'p' element should have a single small green image in the center of its background area. +

+

+[test cl7] This 'p' element should have a single small green image whose top left corner is 10 pixels down and 10 pixels to the left of the top left corner of the background area. +

+

+[test cl8] This 'p' element should have a single small green image whose left side is 10 pixels to the right of the left side of the background area, and which is vertically centered within the background area. +

+

+[test cl9] This 'p' element should have a single small green image which is horizontally centered within the background area, and whose top side is 10 pixels down from the top edge of the background area. +

+

+[test cl10] This 'p' element should have a single small green image in the top left corner of the background area, as the value supplied is invalid and must be ignored. +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a single green image in the top right corner of the background area. +
+[inh1] This 'div' element should have a single green image in the top right corner of the background area, the same as its parent, as it has a style attribute set to inherit the background-position value. If the image appears at the center of the left side of the background area, the test has been failed. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec14-02-01f.htm ##### + + + +14.2.1f background + + + + + + +

CSS2 Test Suite: 14.2.1 background

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.test {background: lime;}
+.cl1 {background: green;}
+.cl2 {background: green url(pix/smgr-bg.gif) top center repeat-x;}
+.cl3 {background: silver url(pix/crosshair.gif) center no-repeat;}
+.cl4 {background: url(pix/crosshair.gif) no-repeat;}
+.cl5 {background: transparent url(pix/vertical-wave.gif) center repeat-y fixed;}
+.parent {background: silver url(pix/crosshair2.gif) top right repeat-x;}
+.inh {background: #FCC url(pix/redsqr.gif) repeat-y;}
+
+
+
+

+[test] This 'p' element should have a lime background. +

+

+[test cl1] This 'p' element should have a green background. This is distinct from a lime background. +

+

+test cl2] This 'p' element should have a green background, except along the top, where a green-grid strip should originate at the top center of the background area and repeat to both the right and the left of that point. +

+

+test cl3] This 'p' element should have a silver background and a single crosshair image at the center of the background area. This image should not tile in any direction. +

+

+test cl4] This 'p' element should have a single crosshair image at the top left corner of its background area, and the rest of the background should be transparent. If the rest of the background is lime, then the test has been failed. +

+

+test cl5] This 'p' element should have a wavy stripe down the center of its background area, and this stripe should remain stationary while the document is scrolled. In other words, the element should seem as if it is a moving window through which different parts of the wavy image are visible. In order to make the effect more obvious, extra text is appended to the content of this element in order to increase its height. Also consider resizing the browser window to be more narrow so that the element becomes taller and is (visually) pushed further down in the document. +

+

+A relevant quotation from the CSS2 specification: +

+
+
+'background' +
+ + +
Value:  [<'background-color'> || <'background-image'> || <'background-repeat'> +|| <'background-attachment'> || <'background-position'>] | inherit + +
Initial:  not defined for shorthand properties +
Applies to:  all elements +
Inherited:  no +
Percentages:  allowed on 'background-position' +
Media:  visual +
+
+
+ +

The 'background' property +is a shorthand property for setting the individual background +properties (i.e., 'background-color', 'background-image', 'background-repeat', 'background-attachment' +and 'background-position') at +the same place in the style sheet. +

+ +

The 'background' property +first sets all the individual background properties to their initial +values, then assigns explicit values given in the declaration. +

+
+[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a silver background and a horizontal stripe of green crosshair images running along the top side of its background area, beginning in the top right corner of the background area. +
+[inh1] This 'div' element should have a silver background and a horizontal stripe of green crosshair images running along the top side of its background area, beginning in the top right corner of the background area, the same as its parent, as it has a style attribute set to inherit the background value. If the background is light red with a bright red vertical stripe through its center, the test has been failed. +
+This is the end of the parent element. +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-02.htm ##### + + + +15.2.2 font-family + + + + + + +

CSS2 Test Suite: 15.2.2 font-family

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
DIV.one {font-family: monospace;}
+.cl1 {font-family: serif;}
+.cl2 {font-family: sans-serif;}
+.cl3 {font-family: cursive;}
+.cl4 {font-family: fantasy;}
+.cl5 {font-family: monospace;}
+.cl6 {font-family: sans-serif,cursive;}
+.cl7 {font-family: monospace,serif;}
+div.parent {font-family: sans-serif;}
+div.inh1 {font-family: cursive;}
+div.inh2 {font-family: monospace;}
+
+
+
+
+

+This sentence is normal for the second division, which is the next five paragraph elements; it should be dislpayed using a monospace font. +

+

+[cl1] This sentence should be in a serif font. +

+

+[cl2] This sentence should be in a sans-serif font. +

+

+[cl3] This sentence should be in a cursive font. +

+

+[cl4] This sentence should be in a fantasy font. +

+

+[cl5] This sentence should be in a monospace font. +

+
+

+[cl6] This sentence should be in a sans-serif font, not cursive. +

+

+[cl7] This sentence should be in a monospace font, not serif. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a sans-serif font for its display, as it has a style attribute set to inherit the font-family value. [/div.inh1] +
+
+[div.inh2] This DIV should use a sans-serif font for its display, as it has a style attribute set to inherit the font-family value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-03a.htm ##### + + + +15.2.3a font-style + + + + + + +

CSS2 Test Suite: 15.2.3 font-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font-style: italic;}
+.cl2 {font-style: oblique;}
+.cl3, I {font-style: normal;}
+div.parent {font-style: normal;}
+div.inh1 {font-style: italic;}
+div.inh2 {font-style: oblique;}
+
+
+
+

+[cl1] The font in this paragraph should be in italics, but the last word of the sentence should be [cl3] normal. +

+

+[cl2] The font in this paragraph should be oblique. +

+

+[I] This italics element should be normal instead of italicized. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normal (non-italic) font for its display, as it has a style attribute set to inherit the font-style value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normal (non-oblique) font for its display, as it has a style attribute set to inherit the font-style value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-03b.htm ##### + + + +15.2.3b font-variant + + + + + + +

CSS2 Test Suite: 15.2.3 font-variant

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font-variant: small-caps;}
+.cl2 {font-variant: normal;}
+div.parent {font-variant: normal;}
+div.inh1 {font-variant: small-caps;}
+
+
+
+

+[cl1] This Paragraph should be in Small Caps. +

+

+[cl1] This Paragraph should be in Small Caps, but the Last three Words in the Sentence [cl2] should be Normal. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normal (non-small-caps) font for its display, as it has a style attribute set to inherit the font-variant value. [/div.inh1] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-03c.htm ##### + + + +15.2.3c font-weight + + + + + + +

CSS2 Test Suite: 15.2.3 font-weight

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font-weight: bold;}
+.cl2, B {font-weight: lighter;}
+.cl3 {font-weight: bolder;}
+.cl4 {font-weight: normal;}
+.cl5w1 {font-weight: 100;}
+.cl5w2 {font-weight: 200;}
+.cl5w3 {font-weight: 300;}
+.cl5w4 {font-weight: 400;}
+.cl5w5 {font-weight: 500;}
+.cl5w6 {font-weight: 600;}
+.cl5w7 {font-weight: 700;}
+.cl5w8 {font-weight: 800;}
+.cl5w9 {font-weight: 900;}
+div.parent {font-weight: normal;}
+div.inh1 {font-weight: bold;}
+div.inh2 {font-weight: 900;}
+
+
+
+

+[cl1] The font for this paragraph should be bold. +

+

+[cl1] The font for this paragraph should be bold, but the last three words in the sentence [cl2] should be normal. +

+

+[B] The font for this bold element should be normal (boldface made lighter). +

+

+[cl3] The font for this paragraph should be bolder than normal. +

+

This is a heading-4.

+

[cl3] This is a bolder heading-4.

+ + + +

+The following list should contain list items in which the content of each item is the same weight. +

+ +
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normally weighted font for its display, as it has a style attribute set to inherit the font-weight value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normally weighted font for its display, as it has a style attribute set to inherit the font-weight value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-03d.htm ##### + + + +15.2.3d font-stretch + + + + + + +

CSS2 Test Suite: 15.2.3 font-stretch

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cln {font-stretch: narrower;}
+.clw {font-stretch: wider;}
+.cl1 {font-stretch: ultra-condensed;}
+.cl2 {font-stretch: extra-condensed;}
+.cl3 {font-stretch: condensed;}
+.cl4 {font-stretch: semi-condensed;}
+.cl5 {font-stretch: normal;}
+.cl6 {font-stretch: semi-expanded;}
+.cl7 {font-stretch: expanded;}
+.cl8 {font-stretch: extra-expanded;}
+.cl9 {font-stretch: ultra-expanded;}
+div.parent {font-stretch: normal;}
+div.inh1 {font-stretch: expanded;}
+div.inh2 {font-stretch: ultra-condensed;}
+
+
+
+

+[cl1] This text should have an ultra-condensed font, + + [cln] while this text should also be ultra-condensed + + + [clw] and this text should be wider. + +

+ +

+[cl2] This text should have an extra-condensed font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl3] This text should have a condensed font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl4] This text should have a semi-condensed font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl5] This text should have a normal font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl6] This text should have a semi-expanded font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl7] This text should have a expanded font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl8] This text should have an extra-expanded font, + + [cln] while this text should be narrower + + + [clw] and this text should be wider. + +

+ +

+[cl9] This text should have an extra-expanded font, + + [cln] while this text should be narrower + + + [clw] and this text should also be ultra-expanded. + +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normally stretched font for its display, as it has a style attribute set to inherit the font-stretch value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normally stretched font for its display, as it has a style attribute set to inherit the font-stretch value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-04a.htm ##### + + + +15.2.4a font-size + + + + + + +

CSS2 Test Suite: 15.2.4 font-size

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font-size: medium;}
+.cl2 {font-size: larger;}
+.cl3 {font-size: smaller;}
+.cl4 {font-size: xx-small;}
+.cl5 {font-size: x-small;}
+.cl6 {font-size: small;}
+.cl7 {font-size: large;}
+.cl8 {font-size: x-large;}
+.cl9 {font-size: xx-large;}
+.cl10 {font-size: 0.5in;}
+.cl11 {font-size: 1cm;}
+.cl12 {font-size: 10mm;}
+.cl13 {font-size: 18pt;}
+.cl14 {font-size: 1.5pc;}
+.cl15 {font-size: 2em;}
+.cl16 {font-size: 3ex;}
+.cl17 {font-size: 25px;}
+.cl18 {font-size: 200%;}
+.cl19 {font-size: -0.5in;}
+div.parent {font-size: medium;}
+div.inh1 {font-size: xx-small;}
+div.inh2 {font-size: xx-large;}
+
+
+
+

+This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent. +

+

+[cl1] The font of this paragraph has been set to medium, which may or may not be the same size as unstyled text. +

+

+[cl2] The font of this paragraph should be larger than unstyled text. +

+

+[cl3] The font of this paragraph should be smaller than unstyled text. +

+

+[cl4] The font of this paragraph should be very small, but the last three words in the sentence [cl1] should be medium. +

+

+[cl5] The font of this paragraph should be rather small, but the last three words in the sentence [cl1] should be medium. +

+

+[cl6] The font of this paragraph should be small, but the last three words in the sentence [cl1] should be medium. +

+

+[cl7] The font of this paragraph should be large, but the last three words in the sentence [cl1] should be medium. +

+

+[cl8] The font of this paragraph should be rather large, but the last three words in the sentence [cl1] should be medium. +

+

+[cl9] The font of this paragraph should be very large, but the last three words in the sentence [cl1] should be medium. +

+

+[cl10] The font of this paragraph should be half an inch tall. +

+

+[cl11] The font of this paragraph should be one centimeter tall. +

+

+[cl12] The font of this paragraph should be ten millimeters tall. +

+

+[cl13] The font of this paragraph should be eighteen points tall. +

+

+[cl14] The font of this paragraph should be one and one half picas tall. +

+

+[cl15] The font of this paragraph should be two em tall. +

+

+[cl16] The font of this paragraph should be three ex tall. +

+

+[cl17] The font of this paragraph should be twenty-five pixels tall. +

+

+[cl18] The font of this paragraph should be twice normal size. +

+

+[cl19] The font of this paragraph should be normal size, since no negative values are allowed and therefore should be ignored. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size value. [/div.inh1] +
+
+[div.inh2] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-04b.htm ##### + + + +15.2.4b font-size-adjust + + + + + + +

CSS2 Test Suite: 15.2.4 font-size-adjust

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font: 14px "Greek Isles", serif; font-size-adjust: 1;}
+.cl2 {font: 14px "Greek Isles", serif; font-size-adjust: 2;}
+.cl3 {font: 14px "Greek Isles", serif; font-size-adjust: 0.75;}
+div.parent {font-size-adjust: none; font: 14px "Greek Isles", serif;}
+div.inh1 {font-size-adjust: 2;}
+div.inh2 {font-size-adjust: 0.75;}
+
+
+
+

+[p.cl1] This paragraph should use a serif font whose font-size is very close to 14px. [/p.cl1] +

+

+[p.cl2] This paragraph should use a serif font whose font-size is very close to 28px. [/p.cl2] +

+

+[p.cl3] This paragraph should use a serif font whose font-size is very close to 9px. [/p.cl3] +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size-adjust value. [/div.inh1] +
+
+[div.inh2] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size-adjust value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec15-02-05.htm ##### + + + +15.2.5 font + + + + + + +

CSS2 Test Suite: 15.2.5 font

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font: bold 12px monospace;}
+.cl2 {font: 700 italic small-caps 16px/12px Helvetica, sans-serif;}
+.cl3 {font: 1em/1.0 serif;}
+.cl-sys-a {font: caption;}
+.cl-sys-b {font: icon;}
+.cl-sys-c {font: menu;}
+.cl-sys-d {font: message-box;}
+.cl-sys-e {font: small-caption;}
+.cl-sys-f {font: status-bar;}
+div.parent {font: normal normal normal medium sans-serif;}
+div.inh1 {font: bold italic small-caps 28px serif;}
+div.inh2 {font: normal oblique small-caps 0.8em cursive;}
+
+
+
+

+[p.cl1] This paragraph should use a boldfaced 12px monospace font. [/p.cl1] +

+

+[p.cl2] This paragraph should use a boldfaced italic small-caps 16px sans-serif font (Helvetica if available) with a line-height of 12px, which should cause the lines to overlap ever so slightly. [/p.cl2] +

+

+[p.cl3] This paragraph should use a normal medium-size serif font. [/p.cl3] +

+

+[p.cl-sys-a] This paragraph should use the system font for captioned controls (e.g. buttons, drop-downs, etc.). [/p.cl-sys-a] +

+

+[p.cl-sys-b] This paragraph should use the system font for icon labels. [/p.cl-sys-b] +

+

+[p.cl-sys-c] This paragraph should use the system font for menu entries (e.g., dropdown menus and menu lists). [/p.cl-sys-c] +

+

+[p.cl-sys-d] This paragraph should use the system font for dialog boxes. [/p.cl-sys-d] +

+

+[p.cl-sys-e] This paragraph should use the system font for labelling small controls. [/p.cl-sys-e] +

+

+[p.cl-sys-f] This paragraph should use the system font for window status bars. [/p.cl-sys-f] +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normal medium-size sans-serif font for its display, as it has a style attribute set to inherit the font value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normal medium-size sans-serif font for its display, as it has a style attribute set to inherit the font value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-01.htm ##### + + + +16.1 text-indent + + + + + + +

CSS2 Test Suite: 16.1 text-indent

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {text-indent: 0.5in; background: aqua;}
+.cl2 {text-indent: 2cm; background: aqua;}
+.cl3 {text-indent: 20mm; background: aqua;}
+.cl4 {text-indent: 24pt; background: aqua;}
+.cl5 {text-indent: 2pc; background: aqua;}
+.cl6 {text-indent: 2em; background: aqua;}
+.cl7 {text-indent: 2ex; background: aqua;}
+.cl8 {text-indent: 50%; background: aqua;}
+.cl9 {text-indent: 25px; background: aqua;}
+blockquote {text-indent: 50%; background: aqua;}
+div.parent {text-indent: 50%; width: 400px;}
+div.inh1 {text-indent: 10px; margin: 25px;}
+div.inh2 {text-indent: 10%; margin: 25px;}
+
+
+
+

+[cl1] The first line of this paragraph should be indented half an inch. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl2] The first line of this sentence should be indented two centimeters. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl3] The first line of this sentence should be indented twenty millimeters. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl4] The first line of this sentence should be indented twenty-four points. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl5] The first line of this sentence should be indented two picas. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl6] The first line of this sentence should be indented two em. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl7] The first line of this sentence should be indented two ex. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl8] The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page. Line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl9] The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page. Line-wrapping will have to occur in order to properly test this assertion. +

+

+[cl1] Only the first line of this sentence should be indented half an inch,
+no matter where the lines might start, and
+regardless of any other markup which may be present. +

+
+[blockquote] The first line of this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY. No other line in the element should be so indented, although line-wrapping will have to occur in order to properly test this assertion. +
+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have its first line indented by half the width of its parent element, as it has a style attribute set to inherit the text-indent value. [/div.inh1] +
+
+[div.inh2] This DIV should have its first line indented by half the width of its parent element, as it has a style attribute set to inherit the text-indent value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-02.htm ##### + + + +16.2 text-align + + + + + + +

CSS2 Test Suite: 16.2 text-align

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {text-align: left;}
+.cl2 {text-align: right;}
+.cl3 {text-align: center;}
+.cl4 {text-align: justify;}
+.cl5 {text-align: ".";}div.parent {text-align: left;}
+div.inh1 {text-align: right;}
+div.inh2 {text-align: center;}
+
+
+
+

+[cl1] This sentence should be left-justified. +

+

+[cl2] This sentence should be right-justified. +

+

+[cl3] This sentence should be centered. +

+

+[cl4] This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages. +

+ +

+In the following table, all content should align on the period (.) symbol. +

+ + + + + + + + + + + + + + + + +
451.27$999.95
578.1$12,499.95
450#9.95
1923875.934572$59.95
3.14159265$1499.95

+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have its text left aligned, as it has a style attribute set to inherit the text-align value. [/div.inh1] +
+
+[div.inh2] This DIV should have its text left aligned, as it has a style attribute set to inherit the text-align value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-03-01.htm ##### + + + +16.3.1 text-decoration + + + + + + +

CSS2 Test Suite: 16.3.1 text-decoration

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {text-decoration: underline;}
+.cl2 {text-decoration: overline;}
+.cl3 {text-decoration: line-through;}
+.cl4 {text-decoration: blink;}
+B.cl5 {text-decoration: none;}
+.cl6 {text-decoration: underline overline;}
+.cl7 {text-decoration: underline overline line-through;}
+div.parent {text-decoration: none;}
+div.inh1 {text-decoration: underline;}
+div.inh2 {text-decoration: line-through;}
+
+
+
+

+[cl1] The text of this paragraph should be underlined. +

+

+[cl2] The text of this paragraph should be overlined. +

+

+[cl3] The text of this paragraph should be stricken (linethrough). +

+

+[cl4] The text of this paragraph should be blinking. (It is not required, however, that UAs support this behavior.) +

+ +

+[cl1] The text of this paragraph should be underlined. The boldfaced text in this paragraph [cl5] should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own. +

+ +

+[cl6] The text of this paragraph should be underlined and overlined. +

+

+[cl7] The text of this paragraph should be underlined, overlined, and stricken. +

+

+

+

+There should be nothing visible between this paragraph and the one above (there is an empty paragraph element with class of seven between them). +

+

+[cl1] Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements. +

+

+[cl1] The underlining in this paragraph should be green, no matter what the text color may be. +

+

+[cl1] The colors of the underlining in this paragraph should be the same as that of the parent text (that is, the first word in the sentence, which should be black). +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use no text decoration for its display, as it has a style attribute set to inherit the text-decoration value. [/div.inh1] +
+
+[div.inh2] This DIV should use no text decoration for its display, as it has a style attribute set to inherit the text-decoration value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-03-02.htm ##### + + + +16.3.2 text-shadow + + + + + + +

CSS2 Test Suite: 16.3.2 text-shadow

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
h3.cl1{text-shadow: gray 0.5em 0.5em 2px;}
+h3.cl2 {text-shadow: purple 0 0 5px;}
+h3.cl3 {text-shadow: red -10px -0.5em 0.25em, green 1mm 1px 0, blue 0 0.33em 10px;}
+div.parent {text-shadow: none;}
+div.inh1 {text-shadow: purple 3px 5px;}
+div.inh2 {text-shadow: red -10px;}
+
+
+
+

[h3.cl1] This should have a gray shadow [/h3.cl1]

+

[h3.cl2] This should have a purple "glow" [/h3.cl2]

+

[h3.cl3] This should have a wild set of shadows [/h3.cl3]

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have no text shadow, as it has a style attribute set to inherit the text-shadow value. [/div.inh1] +
+
+[div.inh2] This DIV should have no text shadow, as it has a style attribute set to inherit the text-shadow value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-04a.htm ##### + + + +16.4a letter-spacing + + + + + + +

CSS2 Test Suite: 16.4 letter-spacing

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {letter-spacing: 0.3in;}
+.cl2 {letter-spacing: 0.5cm;}
+.cl3 {letter-spacing: 5mm;}
+.cl4 {letter-spacing: 3pt;}
+.cl5 {letter-spacing: 0.25pc;}
+.cl6 {letter-spacing: 1em;}
+.cl7 {letter-spacing: 1ex;}
+.cl8 {letter-spacing: 5px;}
+.cl9 {letter-spacing: normal;}
+.cl10 {letter-spacing: 300%;}
+.cl11 {letter-spacing: -0.1em;}div.parent {letter-spacing: normal;}
+div.inh1 {letter-spacing: 1em;}
+div.inh2 {letter-spacing: -4px;}
+
+
+
+

+[cl1] The letters in this paragraph should have extra space between them. +

+

+[cl2] The letters in this paragraph should have extra space between them. +

+

+[cl3] The letters in this paragraph should have extra space between them. +

+

+[cl4] The letters in this paragraph should have extra space between them. +

+

+[cl5] The letters in this paragraph should have extra space between them. +

+

+[cl6] The letters in this paragraph should have extra space between them. +

+

+[cl7] The letters in this paragraph should have extra space between them. +

+

+[cl8] The letters in this paragraph should have extra space between them, but the last few words in the sentence [cl9] should show normal spacing. +

+

+[cl10] The letters in this paragraph should have normal space between them, since percentage values are not allowed on this property. +

+

+[cl11] The letters in this paragraph should have reduced space between them, since negative values are allowed on this property. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normal letter spacing for its display, as it has a style attribute set to inherit the letter-spacing value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normal letter spacing for its display, as it has a style attribute set to inherit the letter-spacing value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-04b.htm ##### + + + +16.4b word-spacing + + + + + + +

CSS2 Test Suite: 16.4 word-spacing

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {word-spacing: 0.3in;}
+.cl2 {word-spacing: 0.5cm;}
+.cl3 {word-spacing: 5mm;}
+.cl4 {word-spacing: 3pt;}
+.cl5 {word-spacing: 0.25pc;}
+.cl6 {word-spacing: 1em;}
+.cl7 {word-spacing: 1ex;}
+.cl8 {word-spacing: 5px;}
+.cl9 {word-spacing: normal;}
+.cl10 {word-spacing: 300%;}
+.cl11 {word-spacing: -0.2em;}
+div.parent {word-spacing: normal;}
+div.inh1 {word-spacing: 2em;}
+div.inh2 {word-spacing: -2em;}
+
+
+
+

+[cl1] The words in this paragraph should have extra space between them. +

+

+[cl2] The words in this paragraph should have extra space between them. +

+

+[cl3] The words in this paragraph should have extra space between them. +

+

+[cl4] The words in this paragraph should have extra space between them. +

+

+[cl5] The words in this paragraph should have extra space between them. +

+

+[cl6] The words in this paragraph should have extra space between them. +

+

+[cl7] The words in this paragraph should have extra space between them. +

+

+[cl8] The words in this paragraph should have extra space between them, but the last few words in the sentence [cl9] should show normal spacing. +

+

+[cl10] The words in this paragraph should have normal space between them, since percentage values are not allowed on this property. +

+

+[cl11] The words in this paragraph should have reduced space between them, since negative values are allowed on this property. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use a normal word spacing for its display, as it has a style attribute set to inherit the word-spacing value. [/div.inh1] +
+
+[div.inh2] This DIV should use a normal word spacing for its display, as it has a style attribute set to inherit the word-spacing value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-05.htm ##### + + + +16.5 text-transform + + + + + + +

CSS2 Test Suite: 16.5 text-transform

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.ttn {text-transform: none;}
+.cap {text-transform: capitalize;}
+.upp {text-transform: uppercase;}
+.low {text-transform: lowercase;}
+div.parent {text-transform: none;}
+div.inh1 {text-transform: uppercase;}
+div.inh2 {text-transform: lowercase;}
+
+
+
+

[ttn] This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal. +

+

[cap] This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence. +

+

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital [cap] letter. +

+

[upp] This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, [ttn] the last eight words should not be uppercase. +

+

[low] This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use no text transformation in for its display, as it has a style attribute set to inherit the text-transform value. [/div.inh1] +
+
+[div.inh2] This DIV should use no text transformation in for its display, as it has a style attribute set to inherit the text-transform value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec16-06.htm ##### + + + +16.6 white-space + + + + + + +

CSS2 Test Suite: 16.6 white-space

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {white-space: pre;}
+.cl2 {white-space: nowrap;}
+.cl3 {white-space: normal;}
+div.parent {white-space: normal;}
+div.inh1 {white-space: pre;}
+div.inh2 {white-space: nowrap;}
+
+
+
+

+[cl1] This paragraph should show extra space where there would ordinarily not be any. + There should also be preservation of returns +as this sentence + very clearly demonstrates. +

+ +

+[cl2] This paragraph should not word-wrap, no matter how long the paragraph might be or over how many lines it would ordinarily wrap, as it has been set to white-space: nowrap and that should have the obvious effect. +

+ +

+[cl1] This paragraph should show extra space, [cl3] except in the second half. +

+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should use normal white space handling for its display, as it has a style attribute set to inherit the white-space value. [/div.inh1] +
+
+[div.inh2] This DIV should use normal white space handling for its display, as it has a style attribute set to inherit the white-space value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec17-04-01.htm ##### + + + +17.4.1 caption-side + + + + + + +

CSS2 Test Suite: 17.4.1 caption-side

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
table {margin: 20px 150px; background: silver;}
+table td {background: #FF9;}
+caption {border: 1px dotted purple;}
+.cl1 {caption-side: top;}
+.cl2 {caption-side: right;}
+.cl3 {caption-side: bottom;}
+.cl4 {caption-side: left;}
+
+
+
+ + + + + + +
[cl1] Table caption on the top
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
+ + + + + + + +
[cl2] Table caption on the right
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
+ + + + + + + +
[cl3] Table caption on the bottom
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
+ + + + + + + +
[cl4] Table caption on the left
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec17-05-02.htm ##### + + + +17.5.2 table-layout + + + + + + +

CSS2 Test Suite: 17.5.2 table-layout

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
table {background: gray; width: 300px;}
+table td {background: #FF9; color: black;}
+.r1c2 {width: 100px;}
+.r2c1 {width: 150px;}
+.r3c3 {width: 100px;}
+.cl1 {table-layout: fixed;}
+.cl2 {table-layout: auto;}
+
+
+
+

+In the following table, the cells should extend outside of the 'table' element itself, because their aggregate widths are greater than 300px. The table should not expand to contain the cells. +

+ + + + + + + + + + +
[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+ +

+In the following table, the cells should not extend outside of the 'table' element itself, even though their aggregate widths are greater than 300px. The table should instead expand to contain the cells. +

+ + + + + + + + + + +
[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec17-06.htm ##### + + + +17.6 border-collapse + + + + + + +

CSS2 Test Suite: 17.6 border-collapse

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
table {background: gray; width: 300px; padding: 10px; border-spacing: 3px;}
+table td {background: #FF9; color: black; border: 2px outset silver;}
+.cl1 {border-collapse: separate;}
+.cl2 {border-collapse: collapse;}
+
+table.cl3 { border-collapse: collapse; border: 5px solid yellow; }
+table.cl3 col#col1 { border: 3px solid black; }
+table.cl3 td { border: 1px solid red; padding: 1em; }
+table.cl3 td.solid-blue { border: 5px dashed blue; }
+table.cl3 td.solid-green { border: 5px solid green; }
+
+
+
+
+

+The following 'table' element should have 3 pixels of space between its cells (both horizontally and vertically) and 10 pixels of padding around the outer edge of the table. In addition, each cell should have a two-pixel outset border, with each border separate from the others. +

+ + + + + + + + + + +
[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+ +

+The following 'table' element should not have 3 pixels of space between its cells (both horizontally and vertically), not should it have 10 pixels of padding around the outer edge of the table. The cells should not be separated except by their borders, and the borders should appear to "merge" so that cells share borders. +

+ + + + + + + + + + +
[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+ +

+The following 'table' element, with a class of 'cl3', is a test of the collapsed-borders model. +

+ ++ + + + + + + + + + +
1 + 2 + 3 +
4 + 5 + 6 +
7 + 8 + 9 +
10 + 11 + 12 +
13 + 14 + 15 +
+ +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec17-06-01a.htm ##### + + + +17.6.1a border-spacing + + + + + + +

CSS2 Test Suite: 17.6.1 border-spacing

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
table {background: gray; width: 300px; border-spacing: 6px 3px;}
+table td {background: #FF9; color: black;}
+.cl1 {border-collapse: separate;}
+.cl2 {border-collapse: collapse;}
+
+
+
+

+The cells of the following 'table' element should be separated by six pixels horizontally, and three pixels vertically. +

+ + + + + + + + + + +
[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+ +

+The cells of the following 'table' element should be not be separated. +

+ + + + + + + + + + +
[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec17-06-01b.htm ##### + + + +17.6.1b empty-cells + + + + + + +

CSS2 Test Suite: 17.6.1 empty-cells

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
table {background: gray; width: 300px; border-collapse: separate;}
+table td {background: #FF9; color: black; border: 1px solid green;}
+.cl1 {empty-cells: show;}
+.cl2, .cl3 {empty-cells: hide;}
+
+
+
+

+The empty cell in the middle of the following 'table' element should be rendered, including its background and borders. +

+ + + + + + + + + + +
[cl1]r1c2r1c3
r2c1r2c3
r3c1r3c2r3c3
+ +

+The empty cell in the middle of the following 'table' element should not be rendered at all. There should instead be a blank spot in the middle of the 'table'. +

+ + + + + + + + + + +
[cl2]r1c2r1c3
r2c1r2c3
r3c1r3c2r3c3
+ + +

+The second row in the following 'table' element, which contains only empty cells, should not be rendered at all. The table should be drawn as if the entire row had been set to 'display: none'. +

+ + + + + + + + + + +
[cl3]r1c2r1c3
r3c1r3c2r3c3
+
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-01.htm ##### + + + +18.1 cursor + + + + + + +

CSS2 Test Suite: 18.1 cursor

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
TD {background: white;}
+.cl1 {cursor: auto;}
+.cl2 {cursor: default;}
+.cl3 {cursor: crosshair;}
+.cl4 {cursor: pointer;}
+.cl5 {cursor: move;}
+.cl6 {cursor: n-resize;}
+.cl7 {cursor: e-resize;}
+.cl8 {cursor: s-resize;}
+.cl9 {cursor: w-resize;}
+.cl10 {cursor: ne-resize;}
+.cl11 {cursor: se-resize;}
+.cl12 {cursor: sw-resize;}
+.cl13 {cursor: nw-resize;}
+.cl14 {cursor: text;}
+.cl15 {cursor: wait;}
+.cl16 {cursor: help;}
+.cl17 {cursor: url(Globe.ani);}
+div.parent {cursor: auto;}
+div.inh1 {cursor: crosshair;}
+div.inh2 {cursor: help;}
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
[cl1] auto[cl2] default[cl3] crosshair[cl4] pointer[cl5] move
[cl6] n-resize[cl7] e-resize[cl8] s-resize[cl9] w-resize
[cl10] ne-resize[cl11] se-resize[cl12] sw-resize[cl13] nw-resize
[cl14] text[cl15] wait[cl16] help[cl17] url(...)
+
+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have the usual cursor when the mouse pointer hovers over it, as it has a style attribute set to inherit the cursor value. [/div.inh1] +
+
+[div.inh2] This DIV should have the usual cursor when the mouse pointer hovers over it, as it has a style attribute set to inherit the cursor value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-02.htm ##### + + + +18.2 User preferences for colors + + + + + + +

CSS2 Test Suite: 18.2 User preferences for colors

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {color: ActiveBorder;}
+.cl2 {color: ActiveCaption;}
+.cl3 {color: AppWorkspace;}
+.cl4 {color: Background;}
+.cl5 {color: ButtonFace;}
+.cl6 {color: ButtonHighlight;}
+.cl7 {color: ButtonShadow;}
+.cl8 {color: ButtonText;}
+.cl9 {color: CaptionText;}
+.cl10 {color: GrayText;}
+.cl11 {color: Highlight;}
+.cl12 {color: HighlightText;}
+.cl13 {color: InactiveBorder;}
+.cl14 {color: InactiveCaption;}
+.cl15 {color: InactiveCaptionText;}
+.cl16 {color: InfoBackground;}
+.cl17 {color: InfoText;}
+.cl18 {color: Menu;}
+.cl19 {color: MenuText;}
+.cl20 {color: Scrollbar;}
+.cl21 {color: ThreeDDarkShadow;}
+.cl22 {color: ThreeDFace;}
+.cl23 {color: ThreeDHighlight;}
+.cl24 {color: ThreeDLightShadow;}
+.cl25 {color: ThreeDShadow;}
+.cl26 {color: Window;}
+.cl27 {color: WindowFrame;}
+.cl28 {color: WindowText;}
+
+
+
+

+The list items in the following list are all set to various colors. These should match elements of the user agent's operating system or other computing environment. +

+ + +
[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-04a.htm ##### + + + +18.4a outline + + + + + + +

CSS2 Test Suite: 18.4 outline

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
INPUT {border: 3px solid gray;}
+.cl1 {outline: 2px dotted green;}
+.cl2 {outline: 1em double green;}
+.cl3 {outline: thick solid invert;}
+div.parent {outline: none;}
+div.inh1 {outline: 10px solid red;}
+div.inh2 {outline: 1em inset red;}
+
+
+
+

+Here's an input whose outline (when in focus) should be 2 pixels wide, dotted, and green. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be 1em wide, double, and green. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be as wide as "thick", solid, and invert the background. The outline should be drawn to the outside of the element border. +

+

+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have no outline under any circumstances, as it has a style attribute set to inherit the outline value. [/div.inh1] +
+
+[div.inh2] This DIV should have no outline under any circumstances, as it has a style attribute set to inherit the outline value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-04b.htm ##### + + + +18.4b outline-width + + + + + + +

CSS2 Test Suite: 18.4 outline-width

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
INPUT {border: 3px solid gray; outline-style: solid;}
+.cl1 {outline-width: 2px;}
+.cl2 {outline-width: 1em;}
+.cl3 {outline-width: thick;}
+div.parent {outline-width: 1px;}
+div.inh1 {outline-width: 10px;}
+div.inh2 {outline-width: 1em;}
+
+
+

+Note that the following tests are valid only if the property outline-style is supported. +

+
+

+Here's an input whose outline (when in focus) should be 2 pixels wide, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be 1em wide, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be thick, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border. +

+

+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have an outline width of 1px when it is in focus, as it has a style attribute set to inherit the outline-width value. [/div.inh1] +
+
+[div.inh2] This DIV should have an outline width of 1px when it is in focus, as it has a style attribute set to inherit the outline-width value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-04c.htm ##### + + + +18.4c outline-style + + + + + + +

CSS2 Test Suite: 18.4 outline-style

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
INPUT {border: 3px solid gray;}
+.cl1 {outline-style: solid;}
+.cl2 {outline-style: double;}
+.cl3 {outline-style: dotted;}
+.cl4 {outline-style: dashed;}
+.cl5 {outline-style: inset;}
+.cl6 {outline-style: outset;}
+.cl7 {outline-style: groove;}
+.cl8 {outline-style: ridge;}
+div.parent {outline-style: solid;}
+div.inh1 {outline-style: inset;}
+div.inh2 {outline-style: outset;}
+
+
+
+

+Here's an input whose outline (when in focus) should be solid and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be double and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be dotted and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be dashed and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be inset and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be outset and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be grooved and of medium width. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be ridged and of medium width. The outline should be drawn to the outside of the element border. +

+

+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have a solid outline when it is in focus, as it has a style attribute set to inherit the outline-style value. [/div.inh1] +
+
+[div.inh2] This DIV should have a solid outline when it is in focus, as it has a style attribute set to inherit the outline-style value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + +##### sec18-04d.htm ##### + + + +18.4d outline-color + + + + + + +

CSS2 Test Suite: 18.4 outline-color

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
INPUT {border: 3px solid gray; outline-style: solid;}
+.cl1 {outline-color: green;}
+.cl2 {outline-color: invert;}
+div.parent {outline-color: green;}
+div.inh1 {outline-color: maroon;}
+div.inh2 {outline-color: red;}
+
+
+

+Note that the following tests are valid only if the property outline-style is supported. +

+
+

+Here's an input whose outline (when in focus) should be of medium width, solid, and green. The outline should be drawn to the outside of the element border. +

+

+Here's an input whose outline (when in focus) should be of medium width, solid, and invert the background. The outline should be drawn to the outside of the element border. +

+

+[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement. +
+[div.inh1] This DIV should have a green outline when it is in focus, as it has a style attribute set to inherit the outline-color value. [/div.inh1] +
+
+[div.inh2] This DIV should have a green outline when it is in focus, as it has a style attribute set to inherit the outline-color value. [/div.inh2] +
+This is the end of the parent DIV. [/div.parent] +

+[index page] [section] [Previous] [Next] [Specification] +
+ + diff --git a/css2/sec05-02-01.htm b/css2/sec05-02-01.htm new file mode 100755 index 0000000..59b3f09 --- /dev/null +++ b/css2/sec05-02-01.htm @@ -0,0 +1 @@ + 5.2.1 Grouping

CSS2 Test Suite: 5.2.1 Grouping

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1, .cl2, .cl3 {color: green;}
.cl4, %cl5 {color: red;}

[cl1] This sentence should be green.

[cl2] This sentence should be green.

[cl3] This sentence should be green.

[cl4] This sentence should be black.

[cl5] This sentence should be black.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-02.htm b/css2/sec05-02.htm new file mode 100755 index 0000000..9b393f2 --- /dev/null +++ b/css2/sec05-02.htm @@ -0,0 +1 @@ + 5.2 Selector Syntax

CSS2 Test Suite: 5.2 Selector Syntax

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1:first-line strong {color: red;}
.cl2em {color: red;}
.cl2+.cl3 {color: green;}
.cl3  +  .cl4 {color: green;}

[cl1] The emphasized text in the first line of this element should NOT be red, but the same color as the text in the element.

[cl2] The emphasized text in this element should NOT be red, but the same color as the text in the element.

[cl3] The text in this element should be green.

[cl4] The text in this element should be green.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-03.htm b/css2/sec05-03.htm new file mode 100755 index 0000000..f3d1085 --- /dev/null +++ b/css2/sec05-03.htm @@ -0,0 +1 @@ + 5.3 Universal Selector

CSS2 Test Suite: 5.3 Universal Selector

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

* {text-decoration: overline;}
*.cl1 {color: purple;}
.pastoral {color: green;}  /* omitted universal selector should be inferred */
big {font-size: 133%; color: rgb(60%,60%,40%);}


This is a paragraph element, which should be overlined. In fact, all of the elements on this page should be overlined. The word "all" in this paragraph may therefore appear to have two overlines, one consistent with the normal text and one slightly higher than that. (Other renderings may be possible.) However, the overline for the big element should be a dusky yellow no matter where it appears.

This H3 should be black.

This H4 should be purple. [cl1]


[pastoral] An H3 element which should be green.

[pastoral] A paragraph element which should be green.

[pastoral] A blockquote element which should be green.
[pastoral] A PRE element which should be green.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-04.htm b/css2/sec05-04.htm new file mode 100755 index 0000000..09c9d52 --- /dev/null +++ b/css2/sec05-04.htm @@ -0,0 +1 @@ + 5.4 Type Selectors

CSS2 Test Suite: 5.4 Type Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

H1 {font-family: sans-serif;}
BODY {color: purple;}
P {color: green;}
H3 {color: navy;}
LI {color: green;}

This H1 should be sans-serif.

This paragraph should be green.

This paragraph should be green despite having a class of 'tester'.

This H3 should be navy (dark blue).

  1. This list item should be green...
  2. ...as should this.
This H5 should be purple.

Another paragraph o' green.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-05.htm b/css2/sec05-05.htm new file mode 100755 index 0000000..9ccde95 --- /dev/null +++ b/css2/sec05-05.htm @@ -0,0 +1 @@ + 5.5 Descendant Selectors

CSS2 Test Suite: 5.5 Descendant Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

H1 EM {color: blue;}
P STRONG {color: maroon;}
DIV * P {color: green;}
LI * STRONG {color: green;}

This headline is very important

The EM text in the previous H1 element should be blue.


The strongly emphasized text in this paragraph should be maroon.

The strongly emphasized text in this paragraph should be maroon, despite being the child of an EM element.

In this paragraph we have an anchor which contains emphasized text, which in turn contains a citation, which in turn contains strongly emphasized text-- and that text should be maroon. Here goes: The W3C Web site contains a great resource called The CSS2 Test Suite (if we do say so ourselves).


This is anonymous text within a DIV, followed by:
...another DIV, with more anonymous text, followed by:

...a paragraph, which should be green in color.



[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-06.htm b/css2/sec05-06.htm new file mode 100755 index 0000000..bb8f958 --- /dev/null +++ b/css2/sec05-06.htm @@ -0,0 +1 @@ + 5.6 Child Selectors

CSS2 Test Suite: 5.6 Child Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

BODY > P {color: green;}
BODY>P.cl1 {font-family: sans-serif;}
DIV OL > LI STRONG {color: green;}

This paragraph, as a direct child of the BODY, should be green.

[cl1] This paragraph, as a direct child of the BODY and bearing a class of 'cl1', should be green and in a sans-serif font.

This paragraph, which is a child of a DIV, should NOT be green.

  1. The STRONG text in this list...
  2. ...should be green, since it is a descendant of an LI which is a child of an OL element that's a descendant of the BODY.
  3. This item contains an unordered list:
    • The STRONG text in this list...
    • ...should be green, since it is also a descendant of an LI which is a child of an OL element that's a descendant of the BODY.
  4. One more list item, just for good measure, containing strongly empahsized text which should be green.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-07.htm b/css2/sec05-07.htm new file mode 100755 index 0000000..172e020 --- /dev/null +++ b/css2/sec05-07.htm @@ -0,0 +1 @@ + 5.7 Adjacent Sibling Selectors

CSS2 Test Suite: 5.7 Adjacent Sibling Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

H3 + H4 {color: green;}
UL+P {border-top: 3px solid green;}  /* lack of whitespace shouldn't matter */
EM + STRONG {color: green;}
H3.opener + P {border-top: 3px solid green;}

Here's an H3 element

This H4 should be green


Here's another H3 element

this text is not in an element, and so shouldn't affect the adjacency selector; thus:

This H4 should be green


Here's another H3 element

This text is contained within a paragraph element, and so should affect the adjacency selector; thus:

This H4 should NOT be green


This paragraph, since it follows a UL element, should have a three-pixel green top border.

Within this paragraph, there is emphasized text which contains strongly emphasized text which should NOT be green, as well as strongly emphasized text which should be green.


This is an H3 with a class of "opener".

This paragraph should have a three-pixel solid green top border.

This paragraph should have no border.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-08-01.htm b/css2/sec05-08-01.htm new file mode 100755 index 0000000..f0b99b2 --- /dev/null +++ b/css2/sec05-08-01.htm @@ -0,0 +1 @@ + 5.8.1 Attribute Selectors

CSS2 Test Suite: 5.8.1 Attribute Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P[class] {color: purple;}
P[class="one"] {color: green;}
P[class = "one"] {text-decoration: underline;}
P[class~="two"] {color: olive;}
P[class ~= "two"] {text-decoration: overline;}
P[class|="three"] {color: green;}
P[class |= "three"] {text-decoration: underline;}
P[class|="give"] {color: green;}
P[class~="give"][class~="generously"] {color: red;}
P[lang|="en"] {color: green;}
P[lang |= "de"] {color: green;}
A[HREF] {color: purple;}
A[HREF="http://www.erehwon.zzz/"] {color: green;}
A[NAME="hello"] {color: green;}
P[class="null"] {color: yellow; background: red; font-weight: bold;}
     /*  catch broken forward-compatible parsing */</STYLE>


This is a paragraph, and should not be green.

This is a paragraph with a class of 'test', and should be purple.

This is a paragraph with a class of 'one', and should be green and underlined.

This is a paragraph with a class of 'one step forward', and should NOT be green (but purple instead), nor should it be underlined.

This is a paragraph with a class of 'two steps back', and should be olive and overlined.

This is a paragraph with a class of 'one two three', and should be olive and overlined.

This is a paragraph with a class of 'world war two', and should be olive and overlined.

This is a paragraph with a class of 'three-blind-mice', and should be green and underlined.

This is a paragraph with a class of 'bakers-three', and should NOT be green (but purple instead), nor should it be underlined.

This is a paragraph with a class of 'give me liberty', and should be green. If it is red, then it has inappropriately matched a rule which contains the classes 'give' and 'generously'; if it is black, it has not matched any attribute selector rules. If it is purple, it has matched the attribute selector [class] but not any of the value-related selectors.

This is a paragraph with a LANG of 'en', and should be green.

This is a paragraph with a LANG of 'en-au', and should be green, mate.

This is a paragraph with a LANG of 'de-test', and should be green, ja?

The following hyperlinks should have the color indicated for each:

The text between the dashes-- you know, this stuff here-- should be green, as it is contained by an anchor with a NAME of "hello".


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-08-03.htm b/css2/sec05-08-03.htm new file mode 100755 index 0000000..0e0baec --- /dev/null +++ b/css2/sec05-08-03.htm @@ -0,0 +1 @@ + 5.8.3 Class Selectors

CSS2 Test Suite: 5.8.3 Class Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.pastoral {color: green;}
P.cl0 {color: green;}
P.give.liberty {color: blue; border: 2px solid red; background: white;}

An H3 element which should NOT be green.

A paragraph element which should NOT be green.

A blockquote element which should NOT be green.
A PRE element which should NOT be green.

[pastoral] An H3 element which should be green.

[pastoral] A paragraph element which should be green.

[pastoral] A blockquote element which should be green.
[pastoral] A PRE element which should be green.

[cl0] An H3 element which should NOT be green.

[cl0] A paragraph which should be green.

[cl0] A blockquote element which should NOT be green.
[cl0] A PRE element which should NOT be green.

This is a paragraph with a class of 'give me liberty', and should be red (border), white (background), and blue (foreground).


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-09.htm b/css2/sec05-09.htm new file mode 100755 index 0000000..6e7b0dd --- /dev/null +++ b/css2/sec05-09.htm @@ -0,0 +1 @@ + 5.9 ID Selectors

CSS2 Test Suite: 5.9 ID Selectors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

#one {color: green;}
#1 {color: red;}
#id1 {color: green;}
P#id2 {color: blue;}
P#id3 {color: purple;}

This sentence should be green.

[1] This sentence should be black, not red-- ID selectors cannot begin with digits in CSS1.

[id1] This sentence should be green.

[id2] This paragraph should be blue.

[id2] This sentence should NOT be blue.
[id3] This sentence should be black.

[id11] This paragraph should be black.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-10.htm b/css2/sec05-10.htm new file mode 100755 index 0000000..59cbf7d --- /dev/null +++ b/css2/sec05-10.htm @@ -0,0 +1 @@ + 5.10 Pseudo-Class Combinations

CSS2 Test Suite: 5.10 Pseudo-Class Combinations

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 a:hover {background-color: yellow; color: red;}
.cl2 a:link:hover {background-color: yellow; color: red;}
.cl3 a:hover:link {background-color: yellow; color: red;}
.cl4 a:visited:hover {background-color: yellow; color: red;}
.cl5 a:hover:visited {background-color: yellow; color: red;}
.cl6 :link:hover {background-color: yellow; color: red;}
.cl7 :hover:link {background-color: yellow; color: red;}
.cl8 :visited:hover {background-color: yellow; color: red;}
.cl9 :hover:visited {background-color: yellow; color: red;}
.cl10 a:active {background-color: yellow; color: green;}
.cl11 a:link:active {background-color: yellow; color: green;}
.cl12 a:active:link {background-color: yellow; color: green;}
.cl13 a:visited:active {background-color: yellow; color: green;}
.cl14 a:active:visited {background-color: yellow; color: green;}
.cl15 :link:active {background-color: yellow; color: green;}
.cl16 :active:link {background-color: yellow; color: green;}
.cl17 :visited:active {background-color: yellow; color: green;}
.cl18 :active:visited {background-color: yellow; color: green;}


Note: Before beginning, ensure that this link has been visited, and this link has not.

[cl1] You should see hover effects on both these links: link, visited

[cl2] You should see hover effects on only the "link": link, visited

[cl3] You should see hover effects on only the "link": link, visited

[cl4] You should see hover effects on only the "visited": link, visited

[cl5] You should see hover effects on only the "visited": link, visited

[cl6] You should see hover effects on only the "link": link, visited

[cl7] You should see hover effects on only the "link": link, visited

[cl8] You should see hover effects on only the "visited": link, visited

[cl9] You should see hover effects on only the "visited": link, visited


[cl10] You should see active effects on both these links: link, visited

[cl11] You should see active effects on only the "link": link, visited

[cl12] You should see active effects on only the "link": link, visited

[cl13] You should see active effects on only the "visited": link, visited

[cl14] You should see active effects on only the "visited": link, visited

[cl15] You should see active effects on only the "link": link, visited

[cl16] You should see active effects on only the "link": link, visited

[cl17] You should see active effects on only the "visited": link, visited

[cl18] You should see active effects on only the "visited": link, visited


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-11-01.htm b/css2/sec05-11-01.htm new file mode 100755 index 0000000..525612f --- /dev/null +++ b/css2/sec05-11-01.htm @@ -0,0 +1 @@ + 5.11.1 :first-child

CSS2 Test Suite: 5.11.1 :first-child

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

LI:first-child {color: green;}
P STRONG:first-child {color: green;}
DIV > P:first-child {color: purple;}


The first child element of this paragraph is strongly emphasized text, and should be green, as is also the case for the strongly emphasized text which is the first child of the EM element found here.. The STRONG text in this sentence should NOT be green, since it is not the first child of anything.

In this paragraph, we have some emphasized text, and then a little later, some strongly emphasized text, which should NOT be green, since it is the second child of the paragraph (the EM element is the first).


Within this DIV...

There is a paragraph, and as the first child, it should be purple.

Within this DIV...

An H3 element

There is a paragraph, and as the second child, it should NOT be either purple or green.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-11-02.htm b/css2/sec05-11-02.htm new file mode 100755 index 0000000..240ae43 --- /dev/null +++ b/css2/sec05-11-02.htm @@ -0,0 +1 @@ + 5.11.2 :link and :visited

CSS2 Test Suite: 5.11.2 :link and :visited

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

A {color: green;}
A:link {color: purple;}
A:visited {color: lime;}
#id1 {color: #006600;}
A.external:link {color: olive;}
A.external:visited {color: maroon;}

The following hyperlinks should be purple if the site is unvisited, lime (light green) if visited:

Dark green in any circumstance:

The quoted word "anchor" should be green, NOT purple, since it's part of an anchor. It's a named anchor, and styles declared for the A tag are applied to them under CSS1. It also should NOT turn orange when clicked upon.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-11-03.htm b/css2/sec05-11-03.htm new file mode 100755 index 0000000..f900cc7 --- /dev/null +++ b/css2/sec05-11-03.htm @@ -0,0 +1 @@ + 5.11.3 :active, :hover, and :focus

CSS2 Test Suite: 5.11.3 :active, :hover, and :focus

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

A {color: red;}
A:hover {color: cyan;}
A:active {color: maroon;}
A:focus {border: 1px solid red;}
A:focus:hover {color: lime;}

P.cl1:hover {background: yellow;}
TD:hover {background: silver;}
TD A:hover {color: red; background: yellow;}

INPUT:hover {background: yellow;}
INPUT:focus {background: #FF99FF;}
INPUT:focus:hover {background: #99FF99;}

The following hyperlinks should become maroon (dark red) while active (being clicked), become cyan (light blue) while being hovered over but not in focus, have a one-pixel solid red border when in focus, and become lime (light green) when in focus and being hovered over:

This paragraph, and the one at the top of the page, should have no effects applied when the mouse pointer hovers over them.

[cl1] This paragraph should attain a yellow background when the mouse pointer hovers over it, and have a transparent background in all other circumstances. Extra text has been included in an attempt to have the paragraph display more than one line of text.

This cell contains no anchor. This cell contains an anchor.

The elements in the following form should have a yellow background when being hovered over, a purple background when in focus, and a light green background when in focus and being hovered over.



Input 4.1 Input 4.2 Input 4.3


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-11-04.htm b/css2/sec05-11-04.htm new file mode 100755 index 0000000..d0cdc4a --- /dev/null +++ b/css2/sec05-11-04.htm @@ -0,0 +1 @@ + 5.11.4 :lang

CSS2 Test Suite: 5.11.4 :lang

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P:lang(en) {color: green;}
P:lang(de) {color: purple;}


This paragraph should NOT be any color except black. It (along with all the test statements on this page) has an ancestor element with a lang attribute that has a value of et-kl, which is intended to reset any potentially inherited lang values, either from HTTP headers or the user's language settings.

[en] This paragraph has been marked English, and should be green.

[de] This paragraph has been marked Deutsch, despite the fact that it clearly is English, and should be purple.

[de-ch] This paragraph has been marked as Swiss German, despite the fact that it clearly is English, and should be purple.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-12-01.htm b/css2/sec05-12-01.htm new file mode 100755 index 0000000..d71764a --- /dev/null +++ b/css2/sec05-12-01.htm @@ -0,0 +1 @@ + 5.12.1 :first-line

CSS2 Test Suite: 5.12.1 :first-line

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P:first-line {color: green;}
.cl2:first-line {font-size: 200%;}
.cl3:first-line {font-variant: small-caps;}


The first line of this paragraph, and only that one, should be green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first line of this paragraph, and only that one, should be a larger font size as well as green. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. [cl2]

The first line of this paragraph, and only that one, should be displayed in small-caps style. Thus, if the first line is not in small-caps style, OR if the entire paragraph turns out in small-caps, then the user agent has failed this test (although the problem might be that small-caps is not supported by your browser). This is extra text included for the purposes of making the paragraph long enough to have more than one line. [cl3]


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-12-02.htm b/css2/sec05-12-02.htm new file mode 100755 index 0000000..d471e38 --- /dev/null +++ b/css2/sec05-12-02.htm @@ -0,0 +1 @@ + 5.12.2 :first-letter

CSS2 Test Suite: 5.12.2 :first-letter

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P:first-letter {color: maroon;}
.cl2:first-letter {font-size: 200%;}
P.cl3:first-letter {font-size: 350%;}


The first letter of this paragraph, and only that one, should be maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line.

The first letter of this paragraph, and only that one, should be a larger font size, as well as maroon. If this precise combination does not occur, then the user agent has failed this test. Remember that in order to ensure a complete test, the paragraph must be displayed on more than one line. [cl2]

"We should check for quotation support," it was said. The first two characters in this paragraph-- a double-quote mark and a capital 'W'-- should be 350% bigger than the rest of the paragraph, and maroon. Note that this is not required under CSS1, but it is recommended. [cl3]


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec05-12-03.htm b/css2/sec05-12-03.htm new file mode 100755 index 0000000..8cfe6ea --- /dev/null +++ b/css2/sec05-12-03.htm @@ -0,0 +1 @@ + 5.12.3 :before and :after

CSS2 Test Suite: 5.12.3 :before and :after

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

H3:before {content: "An H3 ";}
P.special:before {content: "Special! ";}
P.special:first-letter {color: green;}
P.special:after {content: " -- The End.";}

This H3 element should have generated content at its beginning.

This paragraph should have no generated content either before or after its content.

This paragraph should start with the word "Special!" and the first letter "S" should be green. Also, the paragraph should end with the words "The End." preceded by a double-dash composed of two hyphens. That is all.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-02-01.htm b/css2/sec06-02-01.htm new file mode 100755 index 0000000..1401c15 --- /dev/null +++ b/css2/sec06-02-01.htm @@ -0,0 +1 @@ + 6.2.1 inherit

CSS2 Test Suite: 6.2.1 inherit

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.cl1 {color: red;}
A:link {color: inherit; text-decoration: underline; font-weight: bold;}


[cl1] Although this paragraph has a class of 'cl1', it also has an inline STYLE of 'color: inherit', which should cause it to inherit its color from the BODY element. Thus, the color should be black.

This unclassed paragraph contains a number of anchors which have been underlined and boldfaced, but whose color inherits from the paragraph itself (thus making them black).


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-03.htm b/css2/sec06-03.htm new file mode 100755 index 0000000..e5ee73d --- /dev/null +++ b/css2/sec06-03.htm @@ -0,0 +1 @@ + 6.3 @import

CSS2 Test Suite: 6.3 @import

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

@import "styleimport.css";
@import url(folder/styleimport.css);

/* This line resets any browsers that got confused by the @import lines */
.ignored { color: black; }

.style { font-weight: bold; color: green; background: silver none; }


The style declaration applied in each following case is: {font-weight: bold; color: green; background: silver none;}.

1. Inline style (style attribute).

2. Embedded stylesheet (style element).

3. Stylesheet imported by embedded stylesheet.

4. Stylesheet in another folder imported by embedded stylesheet.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-04-01.htm b/css2/sec06-04-01.htm new file mode 100755 index 0000000..48853d5 --- /dev/null +++ b/css2/sec06-04-01.htm @@ -0,0 +1 @@ + 6.4.1 Cascading Order

CSS2 Test Suite: 6.4.1 Cascading Order

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

<LINK rel="stylesheet" type="text/css" HREF="linktest.css">
LI {color: purple;}
UL LI {color: blue;}
UL LI LI {color: gray;}
LI.red {color: green;}
UL LI.mar {color: #660000;}
UL LI#gre {color: green;}
.test {color: blue;}
.test {color: purple;}
.cl1 {text-decoration: line-through;}


This sentence should be blue (STYLE attr.).

This sentence should be purple [class="test"].

[cl1] This text should be stricken (overriding the imported underline; only works if LINKed sheets are supported).


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-04-02.htm b/css2/sec06-04-02.htm new file mode 100755 index 0000000..ad5c904 --- /dev/null +++ b/css2/sec06-04-02.htm @@ -0,0 +1 @@ + 6.4.2 !important rules

CSS2 Test Suite: 6.4.2 !important rules

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P {color: green ! important;}
P {color: red;}
P#id1 {color: purple;}


This sentence should be green, because the declaration marked important should override any other normal declaration for the same element, even if it occurs later in the stylesheet.

[id1] This sentence should also be green, even though it has an ID of id1, which would ordinarily make it purple. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.

This sentence should also be green, even though it has a STYLE attribute declaring it to be red. This is because declarations marked important have more weight than normal declarations given in a STYLE attribute.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-04-03.htm b/css2/sec06-04-03.htm new file mode 100755 index 0000000..01a3f6a --- /dev/null +++ b/css2/sec06-04-03.htm @@ -0,0 +1 @@ + 6.4.3 Calculating specificity

CSS2 Test Suite: 6.4.3 Calculating specificity

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

* {color: red;}  /* a=0 b=0 c=0 -> specificity =   0 */
LI  {color: maroon;}  /* a=0 b=0 c=1 -> specificity =   1 */
UL LI {color: green;}  /* a=0 b=0 c=2 -> specificity =   2 */
H1 + *[REL=up] {color: purple;}  /* a=0 b=1 c=1 -> specificity =  11 */
UL OL LI.olive {color: olive;}  /* a=0 b=1 c=3 -> specificity =  13 */ 
LI.olive.level {color: olive; font-weight: bold;}
   /* a=0 b=2 c=1 -> specificity =  21 */
#x34y {color: lime;}  /* a=1 b=0 c=0 -> specificity = 100 */ 




Although this unstyled paragraph, and many other elements on this page, may be red, this is acceptable. For example, the text "No inheritance tests for this property" should be red.

[x34y] This paragraph should be lime.

An H1 element

[rel=up] This paragraph should be purple.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec06-04-04.htm b/css2/sec06-04-04.htm new file mode 100755 index 0000000..8f88612 --- /dev/null +++ b/css2/sec06-04-04.htm @@ -0,0 +1 @@ + 6.4.4 Precedence of non-CSS hints

CSS2 Test Suite: 6.4.4 Precedence of non-CSS hints

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: green;}

This paragraph contains text which is contained by [cl1] a FONT element with a color value of "red". This should be overridden by the CSS rule for class 'cl1', which takes precedence over the non-CSS presentational hint embodied by the FONT element. Therefore, the FONT-enclosed text should be green, not red.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-02.htm b/css2/sec08-02.htm new file mode 100755 index 0000000..0ca3f37 --- /dev/null +++ b/css2/sec08-02.htm @@ -0,0 +1 @@ + 8.2 Margins, padding, borders

CSS2 Test Suite: 8.2 Margins, padding, borders

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

ul {background: green;
    margin: 12px 12px 12px 12px;padding: 3px 3px 3px 3px;}
li{color: black; background: gray;
    margin: 12px 12px 12px 12px; padding: 12px 0px 12px 12px;
    list-style: none;}
li.withborder {border-color: black;
    border-style: dashed; border-width: medium;}



[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-03a.htm b/css2/sec08-03a.htm new file mode 100755 index 0000000..55110a8 --- /dev/null +++ b/css2/sec08-03a.htm @@ -0,0 +1 @@ + 8.3a margin-top

CSS2 Test Suite: 8.3 margin-top

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin-top: 10px;}
.cl2 {margin-top: 15px;}
.cl3 {margin-top: 1em;}
.cl4 {margin-top: -2px; background-color: aqua;}

[test] This 'div' element has no margins applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a top margin of 10 pixels.
[test cl2] This 'div' element should have a top margin of 15 pixels.
[test cl3] This 'div' element should have a top margin of 1em.
[test cl4] This 'div' element should have a top margin of -2 pixels, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-03b.htm b/css2/sec08-03b.htm new file mode 100755 index 0000000..860c165 --- /dev/null +++ b/css2/sec08-03b.htm @@ -0,0 +1 @@ + 8.3b margin-right

CSS2 Test Suite: 8.3 margin-right

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin-right: 10px;}
.cl2 {margin-right: 15px;}
.cl3 {margin-right: 1em;}
.cl4 {margin-right: -2px; background-color: aqua;}

[test] This 'div' element has no margins applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a right margin of 10 pixels.
[test cl2] This 'div' element should have a right margin of 15 pixels.
[test cl3] This 'div' element should have a right margin of 1em.
[test cl4] This 'div' element should have a right margin of -2 pixels, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-03c.htm b/css2/sec08-03c.htm new file mode 100755 index 0000000..0cd5d55 --- /dev/null +++ b/css2/sec08-03c.htm @@ -0,0 +1 @@ + 8.3c margin-bottom

CSS2 Test Suite: 8.3 margin-bottom

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin-bottom: 10px;}
.cl2 {margin-bottom: 15px;}
.cl3 {margin-bottom: 1em;}
.cl4 {margin-bottom: -2px; background-color: aqua;}

[test] This 'div' element has no margins applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a bottom margin of 10 pixels.
[test cl2] This 'div' element should have a bottom margin of 15 pixels.
[test cl3] This 'div' element should have a bottom margin of 1em.
[test cl4] This 'div' element should have a bottom margin of -2 pixels, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-03d.htm b/css2/sec08-03d.htm new file mode 100755 index 0000000..e8aa09d --- /dev/null +++ b/css2/sec08-03d.htm @@ -0,0 +1 @@ + 8.3d margin-left

CSS2 Test Suite: 8.3 margin-left

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin-left: 10px;}
.cl2 {margin-left: 15px;}
.cl3 {margin-left: 1em;}
.cl4 {margin-left: -2px; background-color: aqua;}

[test] This 'div' element has no margins applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a left margin of 10 pixels.
[test cl2] This 'div' element should have a left margin of 15 pixels.
[test cl3] This 'div' element should have a left margin of 1em.
[test cl4] This 'div' element should have a left margin of -2 pixels, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-03e.htm b/css2/sec08-03e.htm new file mode 100755 index 0000000..09fdfe0 --- /dev/null +++ b/css2/sec08-03e.htm @@ -0,0 +1 @@ + 8.3e margin

CSS2 Test Suite: 8.3 margin

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin: 10px;}
.cl2 {margin: 15px;}
.cl3 {margin: 1em;}
.cl4 {margin: -2px; background-color: aqua;}
.cl5 {margin: 10px 20px 0 -5px;}
.cl6 {margin: 10px 20px 0;}
.cl7 {margin: 10px 20px;}


[test] This 'div' element has no margins applied to it, and acts as a reference point.
[test cl1] This 'div' element should have an overall margin of 10 pixels.
[test cl2] This 'div' element should have an overall margin of 15 pixels.
[test cl3] This 'div' element should have an overall margin of 1em.
[test cl4] This 'div' element should have an overall margin of -2 pixels, and an aqua background.
[test cl5] This 'div' element should have margins of 10px top, 20px right, 0 bottom, and -5px left.
[test cl6] This 'div' element should have margins of 10px top, 20px right, 0 bottom, and 20px left.
[test cl7] This 'div' element should have margins of 10px top, 20px right, 10px bottom, and 20px left.
[test] This 'div' element contains a 'span' element with a class of 'cl5' that should appear to have no top or bottom margins, but a 20px right margin and a -5px left margin. If there is [cl5]any increase of line separation in the 'div' element due to the top and bottom margins on the 'span' element, the test has been failed; margins do not affect the height of lines.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-04a.htm b/css2/sec08-04a.htm new file mode 100755 index 0000000..81f4722 --- /dev/null +++ b/css2/sec08-04a.htm @@ -0,0 +1 @@ + 8.4a padding-top

CSS2 Test Suite: 8.4 padding-top

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; margin: 0.5em 0;}
.cl1 {padding-top: 10px;}
.cl2 {padding-top: 15px;}
.cl3 {padding-top: 1em;}
.cl4 {padding-top: -2px; background-color: aqua;}

[test] This 'div' element has no top padding applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a top padding of 10 pixels.
[test cl2] This 'div' element should have a top padding of 15 pixels.
[test cl3] This 'div' element should have a top padding of 1em.
[test cl4] This 'div' element should have a top padding of zero, as negative padding values are not permitted, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-04b.htm b/css2/sec08-04b.htm new file mode 100755 index 0000000..8d9cc87 --- /dev/null +++ b/css2/sec08-04b.htm @@ -0,0 +1 @@ + 8.4b padding-right

CSS2 Test Suite: 8.4 padding-right

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; margin: 0.5em 0;}
.cl1 {padding-right: 10px;}
.cl2 {padding-right: 15px;}
.cl3 {padding-right: 1em;}
.cl4 {padding-right: -2px; background-color: aqua;}

[test] This 'div' element has no right padding applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a right padding of 10 pixels.
[test cl2] This 'div' element should have a right padding of 15 pixels.
[test cl3] This 'div' element should have a right padding of 1em.
[test cl4] This 'div' element should have a right padding of zero, as negative padding values are not permitted, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-04c.htm b/css2/sec08-04c.htm new file mode 100755 index 0000000..822db28 --- /dev/null +++ b/css2/sec08-04c.htm @@ -0,0 +1 @@ + 8.4c padding-bottom

CSS2 Test Suite: 8.4 padding-bottom

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; margin: 0.5em 0;}
.cl1 {padding-bottom: 10px;}
.cl2 {padding-bottom: 15px;}
.cl3 {padding-bottom: 1em;}
.cl4 {padding-bottom: -2px; background-color: aqua;}

[test] This 'div' element has no bottom padding applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a bottom padding of 10 pixels.
[test cl2] This 'div' element should have a bottom padding of 15 pixels.
[test cl3] This 'div' element should have a bottom padding of 1em.
[test cl4] This 'div' element should have a bottom padding of zero, as negative padding values are not permitted, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-04d.htm b/css2/sec08-04d.htm new file mode 100755 index 0000000..a8fddfe --- /dev/null +++ b/css2/sec08-04d.htm @@ -0,0 +1 @@ + 8.4d padding-left

CSS2 Test Suite: 8.4 padding-left

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; margin: 0.5em 0;}
.cl1 {padding-left: 10px;}
.cl2 {padding-left: 15px;}
.cl3 {padding-left: 1em;}
.cl4 {padding-left: -2px; background-color: aqua;}

[test] This 'div' element has no left padding applied to it, and acts as a reference point.
[test cl1] This 'div' element should have a left padding of 10 pixels.
[test cl2] This 'div' element should have a left padding of 15 pixels.
[test cl3] This 'div' element should have a left padding of 1em.
[test cl4] This 'div' element should have a left padding of zero, as negative padding values are not permitted, and an aqua background.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-04e.htm b/css2/sec08-04e.htm new file mode 100755 index 0000000..583e84f --- /dev/null +++ b/css2/sec08-04e.htm @@ -0,0 +1 @@ + 8.4e padding

CSS2 Test Suite: 8.4 padding

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; margin: 0.5em 0;}
.cl1 {padding: 10px;}
.cl2 {padding: 15px;}
.cl3 {padding: 1em;}
.cl4 {padding: -2px; background-color: aqua;}
.cl5 {margin: 10px 20px 0 -5px;}
.cl6 {margin: 10px 20px 0;}
.cl7 {margin: 10px 20px;}


[test] This 'div' element has no padding applied to it, and acts as a reference point.
[test cl1] This 'div' element should have an overall padding of 10 pixels.
[test cl2] This 'div' element should have an overall padding of 15 pixels.
[test cl3] This 'div' element should have an overall padding of 1em.
[test cl4] This 'div' element should have an overall padding of zero, as negative padding values are not permitted, and an aqua background.
[test cl5] This 'div' element should have padding of 10px top, 20px right, 0 bottom, and 0 left (as negative passing values are not permitted).
[test cl6] This 'div' element should have padding of 10px top, 20px right, 0 bottom, and 20px left.
[test cl7] This 'div' element should have padding of 10px top, 20px right, 10px bottom, and 20px left.
[test] This 'div' element contains a 'span' element with a class of 'cl5' that may or may not appear to have top or bottom padding, but should have a 20px right padding and a no left padding. If there is [cl5]any increase of line separation in the 'div' element due to the top and bottom padding on the 'span' element, the test has been failed; padding does not affect the height of lines. However, the padding may extend into or overlap other lines of text.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-01a.htm b/css2/sec08-05-01a.htm new file mode 100755 index 0000000..01c1b3e --- /dev/null +++ b/css2/sec08-05-01a.htm @@ -0,0 +1 @@ + 8.5.1a border-top-width

CSS2 Test Suite: 8.5.1 border-top-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid; border-width: 0;}
.cl1 {border-top-width: thin;}
.cl2 {border-top-width: medium;}
.cl3 {border-top-width: thick;}
.cl4 {border-top-width: 5px;}
.cl5 {border-top-width: 0;}
.cl6 {border-top-width: -5px;}


[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear).

[test cl1] This 'p' element should have a thin top border.

[test cl2] This 'p' element should have a medium top border.

[test cl3] This 'p' element should have a thick top border.

[test cl4] This 'p' element should have a 5px top border.

[test cl5] This 'p' element should have no top border.

[test cl6] This 'p' element should have no top border, as negative border widths are not permitted.

[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px top border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-01b.htm b/css2/sec08-05-01b.htm new file mode 100755 index 0000000..b89dfa8 --- /dev/null +++ b/css2/sec08-05-01b.htm @@ -0,0 +1 @@ + 8.5.1b border-right-width

CSS2 Test Suite: 8.5.1 border-right-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid; border-width: 0;}
.cl1 {border-right-width: thin;}
.cl2 {border-right-width: medium;}
.cl3 {border-right-width: thick;}
.cl4 {border-right-width: 5px;}
.cl5 {border-right-width: 0;}
.cl6 {border-right-width: -5px;}


[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear).

[test cl1] This 'p' element should have a thin right border.

[test cl2] This 'p' element should have a medium right border.

[test cl3] This 'p' element should have a thick right border.

[test cl4] This 'p' element should have a 5px right border.

[test cl5] This 'p' element should have no right border.

[test cl6] This 'p' element should have no right border, as negative border widths are not permitted.

[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px right border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-01c.htm b/css2/sec08-05-01c.htm new file mode 100755 index 0000000..355e44d --- /dev/null +++ b/css2/sec08-05-01c.htm @@ -0,0 +1 @@ + 8.5.1c border-bottom-width

CSS2 Test Suite: 8.5.1 border-bottom-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid; border-width: 0;}
.cl1 {border-bottom-width: thin;}
.cl2 {border-bottom-width: medium;}
.cl3 {border-bottom-width: thick;}
.cl4 {border-bottom-width: 5px;}
.cl5 {border-bottom-width: 0;}
.cl6 {border-bottom-width: -5px;}


[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear).

[test cl1] This 'p' element should have a thin bottom border.

[test cl2] This 'p' element should have a medium bottom border.

[test cl3] This 'p' element should have a thick bottom border.

[test cl4] This 'p' element should have a 5px bottom border.

[test cl5] This 'p' element should have no bottom border.

[test cl6] This 'p' element should have no bottom border, as negative border widths are not permitted.

[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px bottom border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-01d.htm b/css2/sec08-05-01d.htm new file mode 100755 index 0000000..689d325 --- /dev/null +++ b/css2/sec08-05-01d.htm @@ -0,0 +1 @@ + 8.5.1d border-left-width

CSS2 Test Suite: 8.5.1 border-left-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid; border-width: 0;}
.cl1 {border-left-width: thin;}
.cl2 {border-left-width: medium;}
.cl3 {border-left-width: thick;}
.cl4 {border-left-width: 5px;}
.cl5 {border-left-width: 0;}
.cl6 {border-left-width: -5px;}


[test] This 'p' element should have no border applied to it, as it has been given a zero-width overall border (this helps keep the following tests more clear).

[test cl1] This 'p' element should have a thin left border.

[test cl2] This 'p' element should have a medium left border.

[test cl3] This 'p' element should have a thick left border.

[test cl4] This 'p' element should have a 5px left border.

[test cl5] This 'p' element should have no left border.

[test cl6] This 'p' element should have no left border, as negative border widths are not permitted.

[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px left border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-01e.htm b/css2/sec08-05-01e.htm new file mode 100755 index 0000000..380a43e --- /dev/null +++ b/css2/sec08-05-01e.htm @@ -0,0 +1 @@ + 8.5.1e border-width

CSS2 Test Suite: 8.5.1 border-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-width: thin;}
.cl2 {border-width: medium;}
.cl3 {border-width: thick;}
.cl4 {border-width: 5px;}
.cl5 {border-width: 0;}
.cl6 {border-width: -5px;}


[test] This 'p' element has no border width applied to it, and acts as a reference point. It should default to the same border width as the result shown for 'medium' (cl2).

[test cl1] This 'p' element should have a thin overall border.

[test cl2] This 'p' element should have a medium overall border.

[test cl3] This 'p' element should have a thick overall border.

[test cl4] This 'p' element should have a 5px overall border.

[test cl5] This 'p' element should have no overall border.

[test cl6] This 'p' element should have a default-width border, as negative border widths are not permitted.

[test] This 'p' element contains a 'span' element with a class of 'test cl4' that should have a 5px overall border. If there is [test cl4]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-02a.htm b/css2/sec08-05-02a.htm new file mode 100755 index 0000000..1f4d43e --- /dev/null +++ b/css2/sec08-05-02a.htm @@ -0,0 +1 @@ + 8.5.2a border-top-color

CSS2 Test Suite: 8.5.2 border-top-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-top-color: green;}


[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element.

[test cl1] This 'p' element should have a green top border, with the other border sides matching the text color.

[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green top border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-02b.htm b/css2/sec08-05-02b.htm new file mode 100755 index 0000000..c39c41c --- /dev/null +++ b/css2/sec08-05-02b.htm @@ -0,0 +1 @@ + 8.5.2b border-right-color

CSS2 Test Suite: 8.5.2 border-right-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-right-color: green;}


[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element.

[test cl1] This 'p' element should have a green right border, with the other border sides matching the text color.

[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green right border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-02c.htm b/css2/sec08-05-02c.htm new file mode 100755 index 0000000..dcf836c --- /dev/null +++ b/css2/sec08-05-02c.htm @@ -0,0 +1 @@ + 8.5.2c border-bottom-color

CSS2 Test Suite: 8.5.2 border-bottom-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-bottom-color: green;}


[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element.

[test cl1] This 'p' element should have a green bottom border, with the other border sides matching the text color.

[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green bottom border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-02d.htm b/css2/sec08-05-02d.htm new file mode 100755 index 0000000..087c0b6 --- /dev/null +++ b/css2/sec08-05-02d.htm @@ -0,0 +1 @@ + 8.5.2d border-left-color

CSS2 Test Suite: 8.5.2 border-left-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-left-color: green;}


[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element.

[test cl1] This 'p' element should have a green left border, with the other border sides matching the text color.

[test] This 'p' element contains a 'span' element with a class of 'test cl1' that should have a green left border and text-colored borders on the other sides. If there is [test cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-02e.htm b/css2/sec08-05-02e.htm new file mode 100755 index 0000000..bf5833b --- /dev/null +++ b/css2/sec08-05-02e.htm @@ -0,0 +1 @@ + 8.5.2e border-color

CSS2 Test Suite: 8.5.2 border-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-style: solid;}
.cl1 {border-color: green;}
.cl2 {border-color: green red blue purple;}
.cl3 {border-color: green red blue;}
.cl4 {border-color: green red;}


[test] This 'p' element should have a default-color medium-width border applied to it; the border's color should match the color of the text in the element.

[test cl1] This 'p' element should have a green border.

[test cl2] This 'p' element should have a green top border, a red right border, a blue bottom border, and a purple left border.

[test cl3] This 'p' element should have a green top border, a red right border, a blue bottom border, and a red left border.

[test cl4] This 'p' element should have a green top border, a red right border, a green bottom border, and a red left border.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-03a.htm b/css2/sec08-05-03a.htm new file mode 100755 index 0000000..dda9a25 --- /dev/null +++ b/css2/sec08-05-03a.htm @@ -0,0 +1 @@ + 8.5.3a border-top-style

CSS2 Test Suite: 8.5.3 border-top-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-width: 5px; border-color: #753;}
.cl1 {border-top-style: solid;}
.cl2 {border-top-style: dotted;}
.cl3 {border-top-style: dashed;}
.cl4 {border-top-style: double;}
.cl5 {border-top-style: groove;}
.cl6 {border-top-style: ridge;}
.cl7 {border-top-style: inset;}
.cl8 {border-top-style: outset;}


[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753.

[test cl1] This 'p' element should have a solid top border.

[test cl2] This 'p' element should have a dotted top border.

[test cl3] This 'p' element should have a dashed top border.

[test cl4] This 'p' element should have a double top border.

[test cl5] This 'p' element should have a grooved top border.

[test cl6] This 'p' element should have a ridged top border.

[test cl7] This 'p' element should have an inset top border.

[test cl8] This 'p' element should have an outset top border.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid top text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-03b.htm b/css2/sec08-05-03b.htm new file mode 100755 index 0000000..618ddf7 --- /dev/null +++ b/css2/sec08-05-03b.htm @@ -0,0 +1 @@ + 8.5.3b border-right-style

CSS2 Test Suite: 8.5.3 border-right-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-width: 5px; border-color: #753;}
.cl1 {border-right-style: solid;}
.cl2 {border-right-style: dotted;}
.cl3 {border-right-style: dashed;}
.cl4 {border-right-style: double;}
.cl5 {border-right-style: groove;}
.cl6 {border-right-style: ridge;}
.cl7 {border-right-style: inset;}
.cl8 {border-right-style: outset;}


[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753.

[test cl1] This 'p' element should have a solid right border.

[test cl2] This 'p' element should have a dotted right border.

[test cl3] This 'p' element should have a dashed right border.

[test cl4] This 'p' element should have a double right border.

[test cl5] This 'p' element should have a grooved right border.

[test cl6] This 'p' element should have a ridged right border.

[test cl7] This 'p' element should have an inset right border.

[test cl8] This 'p' element should have an outset right border.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid right text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-03c.htm b/css2/sec08-05-03c.htm new file mode 100755 index 0000000..61ed0de --- /dev/null +++ b/css2/sec08-05-03c.htm @@ -0,0 +1 @@ + 8.5.3c border-bottom-style

CSS2 Test Suite: 8.5.3 border-bottom-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-width: 5px; border-color: #753;}
.cl1 {border-bottom-style: solid;}
.cl2 {border-bottom-style: dotted;}
.cl3 {border-bottom-style: dashed;}
.cl4 {border-bottom-style: double;}
.cl5 {border-bottom-style: groove;}
.cl6 {border-bottom-style: ridge;}
.cl7 {border-bottom-style: inset;}
.cl8 {border-bottom-style: outset;}


[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753.

[test cl1] This 'p' element should have a solid bottom border.

[test cl2] This 'p' element should have a dotted bottom border.

[test cl3] This 'p' element should have a dashed bottom border.

[test cl4] This 'p' element should have a double bottom border.

[test cl5] This 'p' element should have a grooved bottom border.

[test cl6] This 'p' element should have a ridged bottom border.

[test cl7] This 'p' element should have an inset bottom border.

[test cl8] This 'p' element should have an outset bottom border.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid bottom text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-03d.htm b/css2/sec08-05-03d.htm new file mode 100755 index 0000000..afe4c15 --- /dev/null +++ b/css2/sec08-05-03d.htm @@ -0,0 +1 @@ + 8.5.3d border-left-style

CSS2 Test Suite: 8.5.3 border-left-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-width: 5px; border-color: #753;}
.cl1 {border-left-style: solid;}
.cl2 {border-left-style: dotted;}
.cl3 {border-left-style: dashed;}
.cl4 {border-left-style: double;}
.cl5 {border-left-style: groove;}
.cl6 {border-left-style: ridge;}
.cl7 {border-left-style: inset;}
.cl8 {border-left-style: outset;}


[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753.

[test cl1] This 'p' element should have a solid left border.

[test cl2] This 'p' element should have a dotted left border.

[test cl3] This 'p' element should have a dashed left border.

[test cl4] This 'p' element should have a double left border.

[test cl5] This 'p' element should have a grooved left border.

[test cl6] This 'p' element should have a ridged left border.

[test cl7] This 'p' element should have an inset left border.

[test cl8] This 'p' element should have an outset left border.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid left text-colored border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-03e.htm b/css2/sec08-05-03e.htm new file mode 100755 index 0000000..8d14593 --- /dev/null +++ b/css2/sec08-05-03e.htm @@ -0,0 +1 @@ + 8.5.3e border-style

CSS2 Test Suite: 8.5.3 border-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver; border-width: 5px; border-color: #753;}
.cl1 {border-style: solid;}
.cl2 {border-style: dotted;}
.cl3 {border-style: dashed;}
.cl4 {border-style: double;}
.cl5 {border-style: groove;}
.cl6 {border-style: ridge;}
.cl7 {border-style: inset;}
.cl8 {border-style: outset;}
.cl9 {border-style: solid dotted double groove;}
.cl10 {border-style: solid dotted double;}
.cl11 {border-style: solid dotted;}


[test] This 'p' element should have no border applied to it, because its border style defaults to none. The borders of 'test' elements in this test should be 5 pixels wide, and the color should be #753.

[test cl1] This 'p' element should have a solid overall border.

[test cl2] This 'p' element should have a dotted overall border.

[test cl3] This 'p' element should have a dashed overall border.

[test cl4] This 'p' element should have a double overall border.

[test cl5] This 'p' element should have a grooved overall border.

[test cl6] This 'p' element should have a ridged overall border.

[test cl7] This 'p' element should have an inset overall border.

[test cl8] This 'p' element should have an outset overall border.

[test cl9] This 'p' element should have a solid top border, a dotted right border, a double bottom border, and a groove left border.

[test cl10] This 'p' element should have a solid top border, a dotted right border, a double bottom border, and a dotted left border.

[test cl11] This 'p' element should have a solid top border, a dotted right border, a solid bottom border, and a dotted left border.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a solid text-colored medium-width border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-04a.htm b/css2/sec08-05-04a.htm new file mode 100755 index 0000000..110fe8a --- /dev/null +++ b/css2/sec08-05-04a.htm @@ -0,0 +1 @@ + 8.5.4a border-top

CSS2 Test Suite: 8.5.4 border-top

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: silver; border-style: none;}
.cl1 {border-top: solid;}
.cl2 {border-top: solid green;}
.cl3 {border-top: solid green 5px;}
.cl4 {border-top: green 5px;}


[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none.

[test cl1] This 'p' element should have a medium-width solid text-colored top border.

[test cl2] This 'p' element should have a medium-width solid green top border.

[test cl3] This 'p' element should have a 5px solid green top border.

[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored top border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-04b.htm b/css2/sec08-05-04b.htm new file mode 100755 index 0000000..5e72c48 --- /dev/null +++ b/css2/sec08-05-04b.htm @@ -0,0 +1 @@ + 8.5.4b border-right

CSS2 Test Suite: 8.5.4 border-right

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: silver; border-style: none;}
.cl1 {border-right: solid;}
.cl2 {border-right: solid green;}
.cl3 {border-right: solid green 5px;}
.cl4 {border-right: green 5px;}


[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none.

[test cl1] This 'p' element should have a medium-width solid text-colored right border.

[test cl2] This 'p' element should have a medium-width solid green right border.

[test cl3] This 'p' element should have a 5px solid green right border.

[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored right border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-04c.htm b/css2/sec08-05-04c.htm new file mode 100755 index 0000000..9f77f4e --- /dev/null +++ b/css2/sec08-05-04c.htm @@ -0,0 +1 @@ + 8.5.4c border-bottom

CSS2 Test Suite: 8.5.4 border-bottom

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: silver; border-style: none;}
.cl1 {border-bottom: solid;}
.cl2 {border-bottom: solid green;}
.cl3 {border-bottom: solid green 5px;}
.cl4 {border-bottom: green 5px;}


[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none.

[test cl1] This 'p' element should have a medium-width solid text-colored bottom border.

[test cl2] This 'p' element should have a medium-width solid green bottom border.

[test cl3] This 'p' element should have a 5px solid green bottom border.

[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored bottom border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-04d.htm b/css2/sec08-05-04d.htm new file mode 100755 index 0000000..7445756 --- /dev/null +++ b/css2/sec08-05-04d.htm @@ -0,0 +1 @@ + 8.5.4d border-left

CSS2 Test Suite: 8.5.4 border-left

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: silver; border-style: none;}
.cl1 {border-left: solid;}
.cl2 {border-left: solid green;}
.cl3 {border-left: solid green 5px;}
.cl4 {border-left: green 5px;}


[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none.

[test cl1] This 'p' element should have a medium-width solid text-colored left border.

[test cl2] This 'p' element should have a medium-width solid green left border.

[test cl3] This 'p' element should have a 5px solid green left border.

[test cl4] This 'p' element should have no border, as no style was supplied as so it defaults to none.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have a medium-width solid text-colored left border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec08-05-04e.htm b/css2/sec08-05-04e.htm new file mode 100755 index 0000000..0566db1 --- /dev/null +++ b/css2/sec08-05-04e.htm @@ -0,0 +1 @@ + 8.5.4e border

CSS2 Test Suite: 8.5.4 border

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: silver; border-style: none;}
.cl1 {border: medium black solid;}
.cl2 {border: thin maroon ridge;}
.cl3 {border: 10px teal outset;}
.cl4 {border: 10px olive inset;}
.cl5 {border: 10px solid; color: maroon;}
.cl6 {border: maroon double;}
.cl7 {border: left red solid;}
.cl8 {border: solid 0px;}

[test] This 'p' element should have no border applied to it, because its border style has been explicitly set to none.

[test cl1] This 'p' element should have an overall medium-width solid black border.

[test cl2] This 'p' element should have an overall thin ridged maroon border.

[test cl3] This 'p' element should have an overall 10px outset teal border.

[test cl4] This 'p' element should have an overall 10px inset olive border.

[test cl5] This 'p' element should have an overall 10px solid maroon border, which is applied by using the value of 'color' set for the element itself.

[test cl6] This 'p' element should have an overall medium-width double maroon border.

[test cl7] This 'p' element should have no border, as the value supplied is invalid.

[test cl8] This 'p' element should have no border, as its width has been set to zero.

[test] This 'p' element contains a 'span' element with a class of 'cl1' that should have an overall medium-width solid black border. If there is [cl1]any increase of line separation in the 'p' element due to the border on the 'span' element, the test has been failed; borders do not affect the height of lines. However, the border may extend into or overlap other lines of text.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-02-05.htm b/css2/sec09-02-05.htm new file mode 100755 index 0000000..f6dfcd6 --- /dev/null +++ b/css2/sec09-02-05.htm @@ -0,0 +1 @@ + 9.2.5 display

CSS2 Test Suite: 9.2.5 display

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {display: inline;}
.cl2 {display: block; background: #FCC;}
.cl3 {display: list-item; list-style-type: square; margin-left: 3em;}
.cl4 {display: none; color: red; font-weight: bold; background: yellow;}
.cl5 {display: run-in;}
.cl6 {margin-left: 5em;}
dt {display: compact;}


In this page, each test or set of tests has been separated with an 'hr' element in order to keep them distinct from one another.


[cl1] This 'p' element should be inline, as should the next two.

[cl1] This 'p' element should be inline, as should the previous and next paragraph.

[cl1] This 'p' element should be inline, as should the previous two.


This 'div' element, which is unstyled, contains a 'span' element [cl2] which is set to class 'cl2' and should therefore be block-level thus breaking up the flow of the 'div' by interrupting it with another block-level element.

[cl3] This paragraph should be rendered as a list-item.


The text following the class marker should be invisible: [cl4] you can't see me!

If the following paragraph is visible, it will be very obvious. It should not be visible, since it a has a class of "cl4".

Hey! I shouldn't be visible!


[cl5] A Heading 3.

The previous 'h3' element (with a class of 'cl5') should run into this paragraph, which means that it appears as inline content at the beginning of this paragraph.


[cl6]
This is a 'dd' element with a 'dt' element preceding it.
Term Number 2
This is another 'dd' element with a 'dt' element preceding it.
No. 3
This is yet another 'dd' element with a 'dt' element preceding it.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-03-01.htm b/css2/sec09-03-01.htm new file mode 100755 index 0000000..0931b63 --- /dev/null +++ b/css2/sec09-03-01.htm @@ -0,0 +1 @@ + 9.3.1 position

CSS2 Test Suite: 9.3.1 position

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {position: static; top: -5px; left: 2px;}
.cl2 {position: relative; top: -5px; left: 2px;}
.cl3 {position: absolute; top: 25px; left: 2px;}
.cl4 {position: fixed; top: 0px;  left: 200px;}
.contain {position: relative; background: yellow; height: 50px;}

The following paragraph will contain four positioned images. Each image is prefaced by a class marker, and each image is numbered so that it is possible to determine which images have been positioned in which places. The containing 'p' element has a class of 'contain'. The following is what should happen with each image:

[cl1] image [cl2] image [cl3] image [cl4] image

An excerpt from section 9.3.1:

The 'position' and 'float' properties determine which of the CSS2 positioning algorithms is used to calculate the position of a box.

'position'
Value:  static | relative | absolute | fixed | inherit
Initial:  static
Applies to:  all elements, but not to generated content
Inherited:  no
Percentages:  N/A
Media:  visual

The values of this property have the following meanings:

static
The box is a normal box, laid out according to the normal flow. The 'left' and 'top' properties do not apply.
relative
The box's position is calculated according to the normal flow (this is called the position in normal flow). Then the box is offset relative to its normal position. When a box B is relatively positioned, the position of the following box is calculated as though B were not offset.
absolute
The box's position (and possibly size) is specified with the 'left', 'right', 'top', and 'bottom' properties. These properties specify offsets with respect to the box's containing block. Absolutely positioned boxes are taken out of the normal flow. This means they have no impact on the layout of later siblings. Also, though absolutely positioned boxes have margins, they do not collapse with any other margins.
fixed
The box's position is calculated according to the 'absolute' model, but in addition, the box is fixed with respect to some reference. In the case of continuous media, the box is fixed with respect to the viewport (and doesn't move when scrolled). In the case of paged media, the box is fixed with respect to the page, even if that page is seen through a viewport (in the case of a print-preview, for example).

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-03-02a.htm b/css2/sec09-03-02a.htm new file mode 100755 index 0000000..ab66b66 --- /dev/null +++ b/css2/sec09-03-02a.htm @@ -0,0 +1 @@ + 9.3.2a top

CSS2 Test Suite: 9.3.2 top

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: purple; position: relative; top: 10px;}
.img-contain {position: relative; background: yellow; 
     height: 50px; width: 250px;}
.img-contain img {position: absolute;}


This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels downward. The space it would have occupied will be preserved.

The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The top edge of the image should be placed 10 pixels below the top edge of the containing block established by the 'div'.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-03-02b.htm b/css2/sec09-03-02b.htm new file mode 100755 index 0000000..06650d2 --- /dev/null +++ b/css2/sec09-03-02b.htm @@ -0,0 +1 @@ + 9.3.2b right

CSS2 Test Suite: 9.3.2 right

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: purple; position: relative; right: 10px;}
.img-contain {position: relative; background: yellow; 
     height: 50px; width: 250px;}
.img-contain img {position: absolute;}


This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels to the left. The space it would have occupied will be preserved.

The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The right edge of the image should be placed 10 pixels to the left of the right edge of the containing block established by the 'div'.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-03-02c.htm b/css2/sec09-03-02c.htm new file mode 100755 index 0000000..7a30889 --- /dev/null +++ b/css2/sec09-03-02c.htm @@ -0,0 +1 @@ + 9.3.2c bottom

CSS2 Test Suite: 9.3.2 bottom

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: purple; position: relative; bottom: 10px;}
.img-contain {position: relative; background: yellow; 
     height: 50px; width: 250px;}
.img-contain img {position: absolute;}


This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels upward. The space it would have occupied will be preserved.

The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The bottom edge of the image should be placed 10 pixels above the bottom edge of the containing block established by the 'div'.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-03-02d.htm b/css2/sec09-03-02d.htm new file mode 100755 index 0000000..abdc727 --- /dev/null +++ b/css2/sec09-03-02d.htm @@ -0,0 +1 @@ + 9.3.2d left

CSS2 Test Suite: 9.3.2 left

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: purple; position: relative; left: 10px;}
.img-contain {position: relative; background: yellow; 
     height: 50px; width: 250px;}
.img-contain img {position: absolute;}


This 'p' element contains a 'span' element that has been [cl1] relatively positioned, which will cause it to move 10 pixels to the right. The space it would have occupied will be preserved.

The following 'div' element has a class of 'img-contain' and contains an image with a class of 'cl1'. The left edge of the image should be placed 10 pixels to the right of the left edge of the containing block established by the 'div'.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-05-01.htm b/css2/sec09-05-01.htm new file mode 100755 index 0000000..ed7a4b2 --- /dev/null +++ b/css2/sec09-05-01.htm @@ -0,0 +1 @@ + 9.5.1 float

CSS2 Test Suite: 9.5.1 float

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

IMG {float: right;}
IMG.cl1 {float: left;}
IMG.cl2 {float: right;}
IMG.cl3 {float: none;}
P.cl4 {float: left; width: 10em; background: yellow;}
SPAN.cl5 {float: right; width: 7em; background: yellow;}

[cl1] The image which occurs at the beginning of this paragraph should be floated to the left, and the text is the paragraph should "wrap around" the image. This is the kind of behavior we've come to expect from Web browsers over the years.

[cl2] The image which occurs at the beginning of this paragraph should be floated to the right, and the text is the paragraph should "wrap around" the image. This is the kind of behavior we've come to expect from Web browsers over the years.

[cl3] The image which occurs at the beginning of this paragraph should not be floated at all, and therefore the text is the paragraph should not "wrap around" the image. Instead, the image should appear as an inline element at the beginning of the paragraph. This is the kind of behavior we came to expect from Web browsers in the early years.

[cl4] This paragraph has been floated to the left, and has a width of ten (10) em with a yellow background.

This is an ordinary, unstyled paragraph. It should "wrap around" the previous paragraph, the one with a class of 'cl4', due to the floatation of the previous paragraph. In other words, the behavior should be exactly the same as one would expect from the test cases above, or indeed from any surfing done on the Web.


This paragraph contains an inline element [cl5] with a class of 'cl5' which should float to the right, be seven (7) em wide, and have a yellow background.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-05-02.htm b/css2/sec09-05-02.htm new file mode 100755 index 0000000..12ffc96 --- /dev/null +++ b/css2/sec09-05-02.htm @@ -0,0 +1 @@ + 9.5.2 clear

CSS2 Test Suite: 9.5.2 clear

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {clear: left;}
.cl2 {clear: right;}
.cl3{clear: both;}
.cl4 {clear: none;}

[Image]

This text should be flowing past a tall orange rectangle on the left side of the browser window.


[Image]

[cl1] This paragraph should appear below the tall orange rectangle above and to the left, and not flow past it.


[Image]

[cl2] This paragraph should appear below the tall orange rectangle above and to the right, and not flow past it.


[Image] [Image]

[cl3] This paragraph should appear below the two tall orange rectangles, and not flow between them.

[Image] [Image]

[cl4] This paragraph should be between both tall orange rectangles.



[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-08-02.htm b/css2/sec09-08-02.htm new file mode 100755 index 0000000..f2e3a69 --- /dev/null +++ b/css2/sec09-08-02.htm @@ -0,0 +1 @@ + 9.8.2 Relative Positioning

CSS2 Test Suite: 9.8.2 Relative Positioning

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.start {line-height: 24px; font-size: 12px; width: 400px;
     color: black; background: white;}
#outer {color: purple; border: 1px solid purple; position: relative; top: -12px;}
#inner {color: blue; border: 1px solid blue; position: relative; top: 12px;}

DIV {background: yellow; height: 50px; width: 250px; margin: 10px;}
IMG.cl1 {position: relative; top: 30%;}
IMG.cl2 {position: relative; right: -30%;}
IMG.cl3 {position: relative; bottom: 30%;}
IMG.cl4 {position: relative; left: 30%;}
IMG.cl5 {position: relative; top: -20px;}
IMG.cl6 {position: relative; right: -20px;}
IMG.cl7 {position: relative; bottom: -20px;}
IMG.cl8 {position: relative; left: -20px;}

SPAN.cl9 {position: relative; top: -1em; left: -5em; color: purple;}
SPAN.cl10 {position: relative; bottom: -1em; right: -5em; color: purple;}

[start] The beginning of the paragraph contents. [outer] The beginning of the outer SPAN. [inner] The contents of the inner SPAN. [outer] The end of the outer SPAN. The end of the paragraph contents.


The following DIVs have been engineered to create a context for positioning. The class of each test is noted at the beginning of the DIV. The percentage offsets should be calculated with respect to the width (250px) or height (50px) of the containing block, depending on the property being tested.

[cl1]
[cl2]
[cl3]
[cl4]
[cl5]
[cl6]
[cl7]
[cl8]

This paragraph contains a SPAN element [cl9] which has been shifted up, and to the left, which demonstrates relative positioning.

This paragraph contains a SPAN element [cl10] which has been shifted down, and to the right, which demonstrates relative positioning.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-08-03.htm b/css2/sec09-08-03.htm new file mode 100755 index 0000000..df4828a --- /dev/null +++ b/css2/sec09-08-03.htm @@ -0,0 +1 @@ + 9.8.3 Floating a Box

CSS2 Test Suite: 9.8.3 Floating a Box

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.start {line-height: 24px; font-size: 12px; width: 400px;
     color: black; background: white;}
#outer1 {color: purple; border: 1px solid purple;}
#inner1 {color: blue; border: 1px solid blue; float: right; width: 130px;}
#outer2 {color: purple; border: 1px solid purple;}
#inner2 {color: blue; border: 1px solid blue; float: right; width: 130px;}
#sibling2 {color: maroon; border: 1px solid maroon;}
#outer3 {color: purple; border: 1px solid purple;}
#inner3 {color: blue; border: 1px solid blue; float: right; width: 130px;}
#sibling3 {color: maroon; border: 1px solid maroon; clear: right;}


[start] The beginning of the paragraph contents. [outer1] The beginning of the outer SPAN. [inner1] The contents of the inner SPAN. [outer] The end of the outer SPAN. The end of the paragraph contents.

[start] The beginning of the paragraph contents. [outer2] The beginning of the outer SPAN. [inner2] The contents of the inner SPAN. [sibling2] The sibling's contents. [outer] The end of the outer SPAN. The end of the paragraph contents.

[start] The beginning of the paragraph contents. [outer3] The beginning of the outer SPAN. [inner3] The contents of the inner SPAN. [sibling3] The sibling's contents. [outer] The end of the outer SPAN. The end of the paragraph contents.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-08-04.htm b/css2/sec09-08-04.htm new file mode 100755 index 0000000..550674d --- /dev/null +++ b/css2/sec09-08-04.htm @@ -0,0 +1 @@ + 9.8.4 Absolute Positioning

CSS2 Test Suite: 9.8.4 Absolute Positioning

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.start {line-height: 24px; font-size: 12px; width: 400px;
     color: black; background: white; position: relative;}
#outer1 {color: purple; border: 1px solid purple; position: absolute; top: 100px; left: 100px; width: 200px;}
#inner1 {color: blue; border: 1px solid blue;}
#outer2 {color: purple; border: 1px solid purple; position: relative;}
#inner2 {color: blue; border: 1px solid blue; position: absolute; top: 100px; left: -100px; width: 200px;}

P.barnote {position: relative; margin-right: 2em; left: 2em; width: 50%;}
SPAN.mark {position: absolute; top: auto; left: -2em; color: maroon;}

DIV {position: relative; background: yellow; height: 50px; width: 250px; margin: 10px;}
IMG.cl1 {position: absolute; top: 30%;}
IMG.cl2 {position: absolute; right: 30%;}
IMG.cl3 {position: absolute; bottom: 30%;}
IMG.cl4 {position: absolute; left: 30%;}
IMG.cl5 {position: absolute; top: 0; left: 0;}
IMG.cl6 {position: absolute; top: 0; right: 100%;}
IMG.cl7 {position: absolute; bottom: 100%; left: 0;}
IMG.cl8 {position: absolute; bottom: 100%; right: 100%;}


[start] The beginning of the paragraph contents. [outer1] The beginning of the outer SPAN. [inner1] The contents of the inner SPAN. [outer] The end of the outer SPAN. The end of the paragraph contents.

[start] The beginning of the paragraph contents. [outer2] The beginning of the outer SPAN. [inner2] The contents of the inner SPAN. [outer] The end of the outer SPAN. The end of the paragraph contents.


[barnote] This paragraph contains an SPAN element (with a class of 'mark') which will cause the SPANned text to be "floated" to the beginning of the line in which it occurs. In other words, a pair of red dashes will appear at the beginning of the line containing THIS -- word.


The following DIVs have been engineered to create a context for positioning. The class of each test is noted at the beginning of the DIV. The percentage offsets should be calculated with respect to the width (250px) or height (50px) of the containing block, depending on the property being tested.

[cl1]
[cl2]
[cl3]
[cl4]

The following four images have been absolutely positioned without a containing element, and so are positioned with respect to the BODY element, which is their parent element. The images should be scrolled with the document, should any scrolling occur.

[cl5] [cl6] [cl7] [cl8]
[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-09-01.htm b/css2/sec09-09-01.htm new file mode 100755 index 0000000..72f29e8 --- /dev/null +++ b/css2/sec09-09-01.htm @@ -0,0 +1 @@ + 9.9.1 z-index

CSS2 Test Suite: 9.9.1 z-index

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.poswrap {position: relative; border: 1px solid purple;
     height: 16px; margin-bottom: 16px;}
.cl1 {position: absolute; left: 0px; top: 0px; z-index: -5;}
.cl2 {position: absolute; left: 43px; top: 0px; z-index: 5;}
.cl3 {position: absolute; left: 0px; top: 0px; z-index: 5;}
.cl4 {position: absolute; left: 43px; top: 0px; z-index: -5;}


The following paragraph will contain two line-break separated images which are absolutely positioned. The first image should be overlapped by the second image. Note that positioning must be supported in order for this test to work, but z-index doesn't do much good without positioning anyway.



The following paragraph will contain two line-break separated images which are absolutely positioned. The containing paragraph is set to be relatively positioned, so that the image offsets are calculated with respect to the upper left corner of the paragraph. The second image should be overlapped by the first image. Note that positioning must be supported in order for this test to work, but z-index doesn't do much good without positioning anyway.




[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-10a.htm b/css2/sec09-10a.htm new file mode 100755 index 0000000..b21d538 --- /dev/null +++ b/css2/sec09-10a.htm @@ -0,0 +1 @@ + 9.10a direction

CSS2 Test Suite: 9.10 direction

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

P.cl1 {direction: ltr;}
P.cl2 {direction: rtl;}


[cl1] This paragraph should be written left-to-right.

[cl2] This paragraph should be written right-to-left.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec09-10b.htm b/css2/sec09-10b.htm new file mode 100755 index 0000000..a40a832 --- /dev/null +++ b/css2/sec09-10b.htm @@ -0,0 +1 @@ + 9.10b unicode-bidi

CSS2 Test Suite: 9.10 unicode-bidi

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div {border: 1px dotted gray; background: white;
   padding: 0.25em; margin-bottom: 0.5em;}
span {border: 1px dashed gray; border-color: gray red silver blue;
   padding: 1px 0.5em;}
.left {direction: ltr;}
.right {direction: rtl;}
.cl1 {unicode-bidi: normal;}
.cl2 {unicode-bidi: bidi-override;}
.cl3 {unicode-bidi: embed;}


The characters in the following elements should be ordered according to the value of 'unicode-bidi'.

[left cl1] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g
[left cl2] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g
[left cl3] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g
[right cl1] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g
[right cl2] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g
[right cl3] 1 2 3 4 5 6 7 8 9 10 11 12 13 a b c d e f g

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-02.htm b/css2/sec10-02.htm new file mode 100755 index 0000000..6950c33 --- /dev/null +++ b/css2/sec10-02.htm @@ -0,0 +1 @@ + 10.2 width

CSS2 Test Suite: 10.2 width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {width: 50px;}
.cl2 {width: 25%;}
.cl3 {width: 150px; background: yellow;}


The following image has no class, and is provided as a reference point for the tests to follow.

[image]

The following image has a class of 'cl1', and should be 50 pixels wide. Since the source image is square, it should also be 50 pixels tall.

[image]

The following image has a class of 'cl2', and should be one-quarter the width of its parent element (the 'body'). Since the source image is square, the height of the image should equal its width.

[image]

This 'p' element contains a 'span' element that has a class of 'cl3'. The 'span' is here: [cl3]. Since width does not apply to inline non-replaced elements, the 'span' should not be 150 pixels wide. If the 'span' is 150 pixels wide, the test has been failed.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-01.htm b/css2/sec10-03-01.htm new file mode 100755 index 0000000..503242f --- /dev/null +++ b/css2/sec10-03-01.htm @@ -0,0 +1 @@ + 10.3.1 Computing widths and margins: inline, non-replaced elements

CSS2 Test Suite: 10.3.1 Computing widths and margins: inline, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.bookend {background: #FCC;}
.test {background: #9F9;}
.cl1 {width: 200px;}
.cl2 {padding: 0 10px;}
.cl3 {border: 10px solid green; border-width: 0 10px;}
.cl4 {margin: 0 10px;}
.cl5 {padding: 0 10px; border: 10px solid green; border-width: 0 10px; margin: 0 10px;}
.cl6 {margin: 0 auto;}


This 'p' element contains a 'span' element with a class of 'test cl1', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl1] this is a span[bookend]. The test span's width should be equal to the size of the content, and it should not be 200 pixels wide, as 'width' is ignored for inline non-replaced elements. The left and right padding, borders, and margins should all have zero width.

This 'p' element contains a 'span' element with a class of 'test cl2', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl2] this is a span[bookend]. The test span's right and left padding should each be 10 pixels wide.

This 'p' element contains a 'span' element with a class of 'test cl3', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl3] this is a span[bookend]. The test span's right and left borders should each be 10 pixels wide (and solid green).

This 'p' element contains a 'span' element with a class of 'test cl4', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl4] this is a span[bookend]. The test span's right and left margins should each be 10 pixels wide.

This 'p' element contains a 'span' element with a class of 'test cl5', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl5] this is a span[bookend]. The test span's right and left padding, borders, and margins should each be 10 pixels wide, and the width should be equal to the size of the content.

This 'p' element contains a 'span' element with a class of 'test cl6'., surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend][test cl6] this is a span[bookend]. The test span's right and left margins should have zero width.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-02.htm b/css2/sec10-03-02.htm new file mode 100755 index 0000000..a87e195 --- /dev/null +++ b/css2/sec10-03-02.htm @@ -0,0 +1 @@ + 10.3.2 Computing widths and margins: inline, replaced elements

CSS2 Test Suite: 10.3.2 Computing widths and margins: inline, replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.bookend {background: #FCC;}
.test {background: #9F9;}
.cl1 {width: 30px;}
.cl2 {padding: 0 10px;}
.cl3 {border: 10px solid green; border-width: 0 10px;}
.cl4 {margin: 0 10px;}
.cl5 {width: 30px; padding: 0 10px; border: 10px solid green; border-width: 0 10px; margin: 0 10px;}
.cl6 {width: auto;}


This 'p' element contains an 'img' element with a class of 'test cl1', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's width should be 30 pixels. The left and right padding, borders, and margins should all have zero width.

This 'p' element contains an 'img' element with a class of 'test cl2', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's right and left padding should each be 10 pixels wide.

This 'p' element contains an 'img' element with a class of 'test cl3', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's right and left borders should each be 10 pixels wide (and solid green).

This 'p' element contains an 'img' element with a class of 'test cl4', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's right and left margins should each be 10 pixels wide.

This 'p' element contains an 'img' element with a class of 'test cl5', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's right and left padding, border, and margins should each be 10 pixels wide, and the image's width should be 30 pixels.

This 'p' element contains an 'img' element with a class of 'test cl6', surrounded by 'span' elements with a class of 'bookend'. These elements are here: [bookend]image[bookend]. The image's width should be equal to its intrinsic width, which is 20 pixels.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-03.htm b/css2/sec10-03-03.htm new file mode 100755 index 0000000..36f519f --- /dev/null +++ b/css2/sec10-03-03.htm @@ -0,0 +1 @@ + 10.3.3 Computing widths and margins: block-level, non-replaced elements in normal flow

CSS2 Test Suite: 10.3.3 Computing widths and margins: block-level, non-replaced elements in normal flow

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {margin-left: 10px;}
.cl2 {margin-left: 10px;}
.cl3 {margin-left: 0;    width: 50%;  margin-right: auto;}
.cl4 {margin-left: auto; width: 50%;  margin-right: auto;}
.cl5 {margin-left: auto; width: 50%;  margin-right: 0;}
.cl6 {margin-left: auto; width: auto; margin-right: 0;}
.cl7 {margin-left: 0;    width: auto; margin-right: auto;}
.cl8 {margin-left: auto; width: auto; margin-right: auto;}
.cl9 {margin-left: auto; width: 100%; margin-right: auto;}
.cl10 {margin-left: 0; padding-left: auto;
  width: 50%; 
  padding-right: auto; margin-right: 0;}

.ruler {padding: 0px; margin: 0px; border-width: 0px;}
p.ruled {background-color: aqua; width: 400px;
  border: solid silver 40px; border-width: 0 40px;
  padding: 0 40px; margin: 0 40px;}


[test cl1] This 'p' element should be offset ten pixels to the left by its 10 pixel left margin.

[cl2]

[test cl1] This 'p' element should be offset twenty pixels to the left by the 10 pixel left margins on itself and the containing 'div' element, since horizontal margins do not collapse.

[test cl3] This 'p' element has a width of 50%, and due to 'auto' values applied to the right margin, the element should be left justified within its parent. The gray rectangle should therefore appear on the left edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

[test cl4] This 'p' element has a width of 50%, and due to 'auto' values applied to the left and right margins, the element should be centered within its parent. The gray rectangle should therefore appear in the middle of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

[test cl5] This element has a width of 50%, and due to 'auto' values applied to the left margin, the element should be right justified within its parent. The gray rectangle should therefore appear on the right edge of the viewport (e.g. the browser window). The text inside the gray rectangle should not be centered.

[test cl6] Since the width is "auto" and the right margin has a length value declared, the left margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

[test cl7] Since the width is "auto" and the left margin has a length value dclared, the right margin becomes zero. This paragraph should have a width of 100% and the text should be left justified.

[test cl8] Since the width is "auto" and both margins are set to "auto", the margins that are set to "auto" become zero. This paragraph should have a width of 100% and the text should be left justified.

[test cl9] Because this paragraph has width 100%, the auto margins become zero, so it should not be centered.

[test cl10] Since auto is an invalid value for padding, the right-margin of this paragraph should be reset to auto and thus be expanded to 50% and it should only occupy the left half of the viewport.

an image of a pixel ruler

[ruled] The border, padding, and margins for this 'p' element should line up with the boundaries denoted in the image below; the edges of the light blue background should line up with the boundary between "padding" and "border." There should be no top or bottom margin; the images above and below should be flush with this paragraph.

an image showing the various boundaries between portions of the test element's element box

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-04.htm b/css2/sec10-03-04.htm new file mode 100755 index 0000000..4455ad8 --- /dev/null +++ b/css2/sec10-03-04.htm @@ -0,0 +1 @@ + 10.3.4 Computing widths and margins: block-level, replaced elements in normal flow

CSS2 Test Suite: 10.3.4 Computing widths and margins: block-level, replaced elements in normal flow

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

img {display: block; height: 15px;}
img.cl1 {margin-right: auto; margin-left: auto; width: auto;}
img.cl2 {margin-right: auto; margin-left: auto; width: 50%;}
img.cl3 {margin-right: 0; margin-left: auto; width: 25px;}


The following image, which has a class of 'cl1', should be its intrinsic width (15 pixels) and centered in the content area of its parent element.

test image

The following image, which has a class of 'cl2', should be half the width of its parent element and centered in the content area of its parent element.

test image

The following image, which has a class of 'cl3', should be 25 pixels wide and its right edge should abut the right edge of the content area of its parent element.

test image
[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-05.htm b/css2/sec10-03-05.htm new file mode 100755 index 0000000..50d0ad8 --- /dev/null +++ b/css2/sec10-03-05.htm @@ -0,0 +1 @@ + 10.3.5 Computing widths and margins: floating, non-replaced elements

CSS2 Test Suite: 10.3.5 Computing widths and margins: floating, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div {float: right; background: #FDA;}
hr {clear: right;}
.cl1 {width: auto; margin-right: auto; margin-left: auto;}
.cl2 {width: auto; margin-right: 20px; margin-left: 20px;}
.cl3 {width: 25%; margin-right: auto; margin-left: auto;}
.cl4 {width: 100%; margin-right: auto; margin-left: auto;}


Note that the horizontal rules are used to keep tests separate, and to "reset" the float environment by providing a handy element to 'clear'.


[cl1] A floated element.
With two lines.
Okay, three.

The floated 'div' to the right of this text should be as skinny as possible, as its computed 'width' should be '0', and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space).


[cl2] A floated element.
With two lines.
Okay, three.

The floated 'div' to the right of this text should be as skinny as possible, as its computed 'width' should be '0', and have 20-pixel right and left margins. This will cause its right edge to be placed 20 pixels to the left of the right edge of the content area of its parent element, and have 20 pixels of extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of additional space).


[cl3] A floated element.
With two lines.
Okay, three.

The floated 'div' to the right of this text should be one-quarter the width of its parent element, and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space).


[cl4] A floated element.
With two lines.
Okay, three.

The floated 'div' should not be to the right of this text but instead be the width of its parent element's content area. This paragraph should appear below the float instead of to its left.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-06.htm b/css2/sec10-03-06.htm new file mode 100755 index 0000000..8ef87eb --- /dev/null +++ b/css2/sec10-03-06.htm @@ -0,0 +1 @@ + 10.3.6 Computing widths and margins: floating, replaced elements

CSS2 Test Suite: 10.3.6 Computing widths and margins: floating, replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

img {float: right; height: 15px;}
hr {clear: right;}
.cl1 {width: auto; margin-right: auto; margin-left: auto;}
.cl2 {width: auto; margin-right: 20px; margin-left: 20px;}
.cl3 {width: 25%; margin-right: auto; margin-left: auto;}
.cl4 {width: 100%; margin-right: auto; margin-left: auto;}


Note that the horizontal rules are used to keep tests separate, and to "reset" the float environment by providing a handy element to 'clear'.


test image

The floated 'img' to the right of this text, which has a class of 'cl1', should be its intrinsic width (15 pixels) and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space).


test image

The floated 'img' to the right of this text, which has a class of 'cl2', should be its intrinsic width (15 pixels) and have 20-pixel right and left margins. This will cause its right edge to be placed 20 pixels to the left of the right edge of the content area of its parent element, and have 20 pixels of extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of additional space).


test image

The floated 'img' to the right of this text, which has a class of 'cl3', should be one-quarter the width of its parent element, and have no right or left margins. This will cause its right edge to abut the right edge of the content area of its parent element, and no extra space between the text in this paragraph and the left edge of the floated element (note that line-breaking in this paragraph may create the appearance of space).


test image

The floated 'img' should not be to the right of this text but instead be the width of its parent element's content area. This paragraph should appear below the float instead of to its left.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-07.htm b/css2/sec10-03-07.htm new file mode 100755 index 0000000..bf57d05 --- /dev/null +++ b/css2/sec10-03-07.htm @@ -0,0 +1 @@ + 10.3.7 Computing widths and margins: absolutely positioned, non-replaced elements

CSS2 Test Suite: 10.3.7 Computing widths and margins: absolutely positioned, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div.contain {position: relative; width: auto;
   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
div.contain * {color: black;}
div.contain span {position: absolute; top: 0; background: #FDA;}
.cl1 {left: 0;}
.cl2 {left: auto;}
.cl3 {left: 25%; right: 25%; width: 50%;}
.cl4 {left: 25%; right: 25%; margin-left: auto; margin-right: auto; width: 25%;}
.cl5 {left: 0; right: 0; margin-left: 25%; margin-right: auto; width: 25%;}
.cl6 {left: 0; right: 0;}
.cl7 {left: 10px; right: 10px;}
.cl8 {left: 10px; right: -10px;}
.cl9 {left: 25%; right: 25%; margin-right: 25%; margin-left: 25%; width: 25%;}

[contain]

This paragraph contains a 'span' with a class of 'cl1' ([cl1]) that should appear in the top left corner of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl2' ([cl2]) that should appear at the top of the containing block with its left edge aligned with the position it would have been if the 'span' had not been positioned.

[contain]

This paragraph contains a 'span' with a class of 'cl3' ([cl3]) that should appear at the top of the containing block with a width half that of the containing block, and centered horizontally within the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl4' ([cl4]) that should appear at the top of the containing block with a width one-quarter that of the containing block, and centered horizontally within the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl5' ([cl5]) that should appear at the top of the containing block with a width one-quarter that of the containing block, and with its right edge lined up with the hoizontal midpoint of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl6' ([cl6]) that should appear at the top of the containing block with a width equal to that of the containing block, centered within it.

[contain]

This paragraph contains a 'span' with a class of 'cl7' ([cl7]) that should appear at the top of the containing block with a width 20 pixels less than that of the containing block, and with its right and left edges inset 10 pixels from each edge of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl8' ([cl8]) that should appear at the top of the containing block with a width equal to that of the containing block, but shifted 10 pixels to the right.

[contain]

This paragraph contains a 'span' with a class of 'cl9' ([cl9]) that should appear at the top of the containing block with a width one-quarter that of the containing block, its left edge lined up with the horizontal midpoint of the containing block, and its right edge 25% inset from the right edge of the containing block.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-03-08.htm b/css2/sec10-03-08.htm new file mode 100755 index 0000000..93e6824 --- /dev/null +++ b/css2/sec10-03-08.htm @@ -0,0 +1 @@ + 10.3.8 Computing widths and margins: absolutely positioned, replaced elements

CSS2 Test Suite: 10.3.8 Computing widths and margins: absolutely positioned, replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div.contain {position: relative; width: auto;
   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
div.contain * {color: black;}
div.contain img {position: absolute; top: 0; height: 15px;}
.cl1 {left: 0;}
.cl2 {left: auto;}
.cl3 {left: 25%; right: 25%; width: 50%;}
.cl4 {left: 25%; right: 25%; margin-left: auto; margin-right: auto; width: 25%;}
.cl5 {left: 0; right: 0; margin-left: 25%; margin-right: auto; width: 25%;}
.cl6 {left: 0; right: 0;}
.cl7 {left: 10px; right: 10px;}
.cl8 {left: 10px; right: -10px;}
.cl9 {left: 25%; right: 25%; margin-right: 25%; margin-left: 25%; width: 25%;}

[contain]

This paragraph contains an 'img' with a class of 'cl1' (test image) that should appear in the top left corner of the containing block, and have an intrinsic width (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl2' (test image) that should appear at the top of the containing block with its left edge aligned with the position it would have been if the 'img' had not been positioned, and have an intrinsic width (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl3' (test image) that should appear at the top of the containing block with a width half that of the containing block, and centered horizontally within the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl4' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, and centered horizontally within the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl5' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, and with its right edge lined up with the hoizontal midpoint of the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl6' (test image) that should appear in the top left corner of the containing block, and have an intrinsic width (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl7' (test image) that should appear near the top left corner of the containing block, with its left edge inset 10 pixels from the left edge of the containing block, and have an intrinsic width (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl8' (test image) that should appear near the top left corner of the containing block, with its left edge inset 10 pixels from the left edge of the containing block, and have an intrinsic width (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl9' (test image) that should appear at the top of the containing block with a width one-quarter that of the containing block, its left edge lined up with the horizontal midpoint of the containing block, and its right edge 25% inset from the right edge of the containing block.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-04a.htm b/css2/sec10-04a.htm new file mode 100755 index 0000000..1374bf6 --- /dev/null +++ b/css2/sec10-04a.htm @@ -0,0 +1 @@ + 10.4a min-width

CSS2 Test Suite: 10.4 min-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {width: 50px; min-width: 50%;}
.cl2 {min-width: 500px;}


[test cl1] This 'p' element has been set to have a width of 50px, but a minimum width of half its parent element's content-width. Thus its width should be half that of its parent element, unless the parent element is 100 pixels or narrower, in which case this element will be 50 pixels wide.

[test cl2] This 'p' element has been set to have a minimum width of 500px. Thus its width should never be narrower than 500 pixels, no matter how narrow its parent element's content-width may become.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-04b.htm b/css2/sec10-04b.htm new file mode 100755 index 0000000..04fda7c --- /dev/null +++ b/css2/sec10-04b.htm @@ -0,0 +1 @@ + 10.4b max-width

CSS2 Test Suite: 10.4 max-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {width: 250px; max-width: 50%;}
.cl2 {max-width: 500px;}


[test cl1] This 'p' element has been set to have a width of 250px, but a maxmum width of half its parent element's content-width. Thus its width should be 250 pixels, unless the parent element is 500 pixels or narrower, in which case this element will be half as wide as its parent's content-width.

[test cl2] This 'p' element has been set to have a maximum width of 500px. Thus its width should never be wider than 500 pixels, no matter how wide its parent element's content-width may become.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-05.htm b/css2/sec10-05.htm new file mode 100755 index 0000000..6d0d522 --- /dev/null +++ b/css2/sec10-05.htm @@ -0,0 +1 @@ + 10.5 height

CSS2 Test Suite: 10.5 height

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {height: 50px;}
.cl2 {height: 50%;}
.cl2contain {height: 80px; border: 1px dotted gray;}
.cl3 {height: 150px; background: yellow;}


The following image has no class, and is provided as a reference point for the tests to follow.

[image]

The following image has a class of 'cl1', and should be 50 pixels tall. Since the source image is square, it should also be 50 pixels wide.

[image]

The following image has a class of 'cl2', and should be its intrinsic height, since its parent element (the 'body') does not have an explicitly assigned height. Since the source image is square, the width of the image should equal its height.

[image]

The following image has a class of 'cl2' and is contained in a 'div' with a class of 'cl2contain'. The image should be half the height of the content-height of 'cl2contain'. Since the source image is square, the width of the image should equal its height.

[image]

This 'p' element contains a 'span' element that has a class of 'cl3'. The 'span' is here: [cl3]. Since height does not apply to inline non-replaced elements, the 'span' should not be 150 pixels tall. If the 'span' is 150 pixels tall, the test has been failed.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-06-01.htm b/css2/sec10-06-01.htm new file mode 100755 index 0000000..dda41ae --- /dev/null +++ b/css2/sec10-06-01.htm @@ -0,0 +1 @@ + 10.6.1 Computing heights and margins: inline, non-replaced elements

CSS2 Test Suite: 10.6.1 Computing heights and margins: inline, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: #9F9;}
.cl1 {height: 200px;}
.cl2 {padding: 10px 0;}
.cl3 {border: 10px solid green; border-width: 10px 0;}
.cl4 {margin: 10px 0;}
.cl5 {padding: 10px 0; border: 10px solid green; border-width: 10px 0; margin: 10px 0;}
.cl6 {margin: auto 0;}


This 'p' element contains a 'span' element with a class of 'test cl1'. This elements is here: [test cl1] this is a span. The test span's height should be equal to the size of the content, and it should not be 200 pixels tall, as 'height' is ignored for inline non-replaced elements. The top and bottom padding, borders, and margins should all have zero width.

This 'p' element contains a 'span' element with a class of 'test cl2'. This elements is here: [test cl2] this is a span. The test span's top and bottom padding should be 10 pixels tall. Padding on non-replaced elements does not increase line height, and so the padding may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." Therefore the top and bottom padding may appear to be zero.

This 'p' element contains a 'span' element with a class of 'test cl3'. This elements is here: [test cl3] this is a span. The test span's top and bottom borders should be 10 pixels tall (and solid green). Borders on non-replaced elements do not increase line height, and so the borders may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." Therefore the top and bottom borders may not appear.

This 'p' element contains a 'span' element with a class of 'test cl4'. This elements is here: [test cl4] this is a span. The test span's top and bottom margins should be 10 pixels tall. Margins on non-replaced elements do not increase line height, and so the top and bottom margins should have no visible effect on layout.

This 'p' element contains a 'span' element with a class of 'test cl5'. This elements is here: [test cl5] this is a span. The test span's top and bottom padding, borders, and margins should be 10 pixels tall. Padding and borders on non-replaced elements do not increase line height, and so they may overlap other lines of text (or be overlapped by them). Per CSS2 section 10.8.1, however, "user agents may use the line box to 'clip' the border and padding areas (i.e., not render them)." The margins should have no visible effect on layout in either case.

This 'p' element contains a 'span' element with a class of 'test cl4'. This elements is here: [test cl4] this is a span. The test span's top and bottom margins should have no height, which means no visible effect on line layout.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-06-02.htm b/css2/sec10-06-02.htm new file mode 100755 index 0000000..fcf7eee --- /dev/null +++ b/css2/sec10-06-02.htm @@ -0,0 +1 @@ + 10.6.2 Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements

CSS2 Test Suite: 10.6.2 Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.bookend {background: #FCC;}
.test {background: #9F9;}
.cl1 {height: 30px;}
.cl2 {padding: 10px 0;}
.cl3 {border: 10px solid green; border-width: 10px 0;}
.cl4 {margin: 10px 0;}
.cl5 {height: 30px; padding: 10px 0; border: 10px solid green; border-width: 10px 0; margin: 10px 0;}
.cl6 {height: auto;}


This 'p' element contains an 'img' element with a class of 'test cl1'. The image is here: image. The image's height should be 30 pixels. The top and bottom padding, borders, and margins should all have zero width.

This 'p' element contains an 'img' element with a class of 'test cl2'. The image is here: image. The image's top and bottom padding should each be 10 pixels wide.

This 'p' element contains an 'img' element with a class of 'test cl3'. The image is here: image. The image's top and bottomborders should each be 10 pixels wide (and solid green).

This 'p' element contains an 'img' element with a class of 'test cl4'. The image is here: image. The image's top and bottom margins should each be 10 pixels wide. This will raise the image 10 pixels, as well as increase the height of the line box to be 10 pixels above the top of the image (assuming the surrounding text is smaller than the image.

This 'p' element contains an 'img' element with a class of 'test cl5'. The image is here: image. The image's top and bottom padding, border, and margins should each be 10 pixels wide, and the image's height should be 30 pixels.

This 'p' element contains an 'img' element with a class of 'test cl6'. The image is here: image. The image's height should be equal to its intrinsic height, which is 20 pixels.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-06-03.htm b/css2/sec10-06-03.htm new file mode 100755 index 0000000..c54b2c2 --- /dev/null +++ b/css2/sec10-06-03.htm @@ -0,0 +1 @@ + 10.6.3 Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements

CSS2 Test Suite: 10.6.3 Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

p {border: 1px dotted gray;}
.cl1 {margin-top: auto; margin-bottom: auto;}
.cl2 {margin-top: 10px; margin-bottom: 10px;}
.cl3 {height: auto;}
.cl4 {height: 25px; overflow: hidden;}
hr {clear: right;}
div {float: right; width: 25%; background: #FDA;}


[cl1] This paragraph should have no top or bottom margins, since the 'auto' values are replaced with '0'.

[cl1] This paragraph should have no top or bottom margins, since the 'auto' values are replaced with '0'.

[cl2] This paragraph should have 10-pixel top and bottom margins. Remember that vertically adjacent margins "collapse."

[cl2] This paragraph should have 10-pixel top and bottom margins. Remember that vertically adjacent margins "collapse."

[cl3] The height of this paragraph depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be.

[cl3] The height of this paragraph depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.

[cl4] The height of this paragraph is 25 pixels. If the content is taller than that, it will be treated according to the value of 'overflow' (which is in this test is set to 'hidden'). Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.


[cl1] A floated element.
With two lines.
Okay, three.

The floated 'div' to the right of this text should be one-quarter the width of its parent element's content area.


[cl2] A floated element.

The floated 'div' to the right of this text should be one-quarter the width of its parent element's content area, with 10-pixel top and bottom margins. This will push it downaward 10 pixels, and prevent any inline content from appearing less than 10 pixels from the bottom of its content area. note that line layout may cause more than 10 pixels to appear between the bottom edge of the floated element's content area and inline content beneath it. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.


[cl3] A floated element.
With two lines.
Okay, three.

The height of the floated 'div' to the right of this text depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be.


[cl3] A floated element.

The height of the floated 'div' to the right of this text depends on its content. It effectively "shrink-wraps" the content, regardless of how short or long it might be.


[cl4] A floated element.
With two lines.
Okay, three.

The height of the floated 'div' to the right of this text is 25 pixels. It effectively "shrink-wraps" the content, regardless of how short or long it might be. If the content is taller than that, it will be treated according to the value of 'overflow' (which is in this test is set to 'hidden').



[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-06-04.htm b/css2/sec10-06-04.htm new file mode 100755 index 0000000..7b1ae9e --- /dev/null +++ b/css2/sec10-06-04.htm @@ -0,0 +1 @@ + 10.6.4 Computing heights and margins: absolutely positioned, non-replaced elements

CSS2 Test Suite: 10.6.4 Computing heights and margins: absolutely positioned, non-replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div.contain {position: relative; width: auto; height: 100px;
   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
div.contain * {color: black;}
div.contain p {margin: 0.5em 0 0.5em 3em;}
div.contain span {position: absolute; left: 0; background: #FDA;}
.cl1 {top: 0;}
.cl2 {top: auto;}
.cl3 {top: 25%; bottom: 25%; height: 50%;}
.cl4 {top: 25%; bottom: 25%; margin-top: auto; margin-bottom: auto; height: 25%;}
.cl5 {top: 0; bottom: 0; margin-top: 25px; margin-bottom: auto; height: 25%;}
.cl6 {top: 0; bottom: 0;}
.cl7 {top: 10px; bottom: 10px;}
.cl8 {top: 10px; bottom: -10px;}
.cl9 {top: 25%; bottom: 25%; margin-top: 25px; margin-bottom: 25px; height: 25%;}

[contain]

This paragraph contains a 'span' with a class of 'cl1' ([cl1]) that should appear in the top left corner of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl2' ([cl2]) that should appear at the left edge of the containing block with its top edge aligned with the position it would have been if the 'span' had not been positioned.

[contain]

This paragraph contains a 'span' with a class of 'cl3' ([cl3]) that should appear at the left edge of the containing block with a height half that of the containing block, and centered vertically within the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl4' ([cl4]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and centered vertically within the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl5' ([cl5]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and with its bottom edge lined up with the vertical midpoint of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl6' ([cl6]) that should appear at the left edge of the containing block with a height equal to that of the containing block, centered within it.

[contain]

This paragraph contains a 'span' with a class of 'cl7' ([cl7]) that should appear at the left edge of the containing block with a height 20 pixels less than that of the containing block, and with its top and bottom edges inset 10 pixels from each edge of the containing block.

[contain]

This paragraph contains a 'span' with a class of 'cl8' ([cl8]) that should appear at the left edge of the containing block with a height equal to that of the containing block, but shifted 10 pixels to downward.

[contain]

This paragraph contains a 'span' with a class of 'cl9' ([cl9]) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, its top edge lined up with the vertical midpoint of the containing block, and its bottom edge 25% inset from the bottom edge of the containing block.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-06-05.htm b/css2/sec10-06-05.htm new file mode 100755 index 0000000..44087e0 --- /dev/null +++ b/css2/sec10-06-05.htm @@ -0,0 +1 @@ + 10.6.5 Computing heights and margins: absolutely positioned, replaced elements

CSS2 Test Suite: 10.6.5 Computing heights and margins: absolutely positioned, replaced elements

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div.contain {position: relative; width: auto; height: 100px;
   border: 2px dashed gray; color: gray; margin-bottom: 0.5em;}
div.contain * {color: black;}
div.contain p {margin: 0.5em 0 0.5em 20px;}
div.contain img {position: absolute; left: 0; width: 15px;}
.cl1 {top: 0;}
.cl2 {top: auto;}
.cl3 {top: 25%; bottom: 25%; height: 50%;}
.cl4 {top: 25%; bottom: 25%; margin-top: auto; margin-bottom: auto; height: 25%;}
.cl5 {top: 0; bottom: 0; margin-top: 25px; margin-bottom: auto; height: 25%;}
.cl6 {top: 0; bottom: 0;}
.cl7 {top: 10px; bottom: 10px;}
.cl8 {top: 10px; bottom: -10px;}
.cl9 {top: 25%; bottom: 25%; margin-top: 25px;  margin-bottom: 25%;height: 25%;}

[contain]

This paragraph contains an 'img' with a class of 'cl1' (test image) that should appear in the top left corner of the containing block, and have an intrinsic height (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl2' (test image) that should appear at the left edge of the containing block with its top edge aligned with the position it would have been if the 'img' had not been positioned, and have an intrinsic height (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl3' (test image) that should appear at the left edge of the containing block with a height half that of the containing block, and centered vertically within the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl4' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and centered vertically within the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl5' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, and with its bottom edge lined up with the vertical midpoint of the containing block.

[contain]

This paragraph contains an 'img' with a class of 'cl6' (test image) that should appear in the top left corner of the containing block, and have an intrinsic height (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl7' (test image) that should appear near the top left corner of the containing block, with its top edge inset 10 pixels from the top edge of the containing block, and have an intrinsic height (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl8' (test image) that should appear near the top left corner of the containing block, with its top edge inset 10 pixels from the top edge of the containing block, and have an intrinsic height (15 pixels).

[contain]

This paragraph contains an 'img' with a class of 'cl9' (test image) that should appear at the left edge of the containing block with a height one-quarter that of the containing block, its top edge lined up with the vertical midpoint of the containing block, and its bottom edge 25% inset from the bottom edge of the containing block.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-07a.htm b/css2/sec10-07a.htm new file mode 100755 index 0000000..71cf6d3 --- /dev/null +++ b/css2/sec10-07a.htm @@ -0,0 +1 @@ + 10.7a min-height

CSS2 Test Suite: 10.7 min-height

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {height: 50%; min-height: 100px;}
.cl2 {min-height: 50%;}
.cl2contain {height: 80px; border: 1px dotted gray;}


[test cl1] This 'p' element has a percentage height, which should be treated as 'auto', and a minimum height of 100 pixels.

The following 'div' has a class of 'cl2contain', and contains an image with a class of 'cl2'. The image should be a minimum of half the height of the content-height of the 'div' that contains it.

test image

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-07b.htm b/css2/sec10-07b.htm new file mode 100755 index 0000000..cd01753 --- /dev/null +++ b/css2/sec10-07b.htm @@ -0,0 +1 @@ + 10.7b max-height

CSS2 Test Suite: 10.7 max-height

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-color: silver;}
.cl1 {height: 250px; max-height: 100px;}
.cl2 {max-height: 50%;}
.cl2contain {height: 10px; border: 1px dotted gray;}


[test cl1] This 'p' element has a height of 250 pixels, and a maximum height of 100 pixels. It should thus be no more than 100 pixels tall.

The following 'div' has a class of 'cl2contain', and contains an image with a class of 'cl2'. The image should be a maximum of half the height of the content-height of the 'div' that contains it.

test image

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-08a.htm b/css2/sec10-08a.htm new file mode 100755 index 0000000..974afda --- /dev/null +++ b/css2/sec10-08a.htm @@ -0,0 +1 @@ + 10.8a line-height

CSS2 Test Suite: 10.8 line-height

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

p span {background-color: #DDD;}
.cl0 {font-size: 15px;}
.cl1 {line-height: -1em; font-size: 15px;}
.cl2 {line-height: 30px; font-size: 15px;}
.cl3 {line-height: 200%; font-size: 15px;}
.cl4 {line-height: 2; font-size: 15px;}
div {border: 1px dotted gray; background: white;
   margin: 0.5em; padding: 0.25em;}
.shrink {font-size: 66%;}
.grow {font-size: 150%;}
.cl5 {line-height: 1.2em; font-size: 15px;}
.cl6 {line-height: 1.2; font-size: 15px;}
.huge {font-size: 200%; border: 1px dotted red; background: none;}
.cl5 img {height: 30px;}

[cl0] A 'p' element with browser-default 'line-height'. Its 'font-size' has been set to 15px, the same as the other tests in this page. This element is included largely for reference purposes, and is not intended to demonstrate a particular aspect of the CSS specification. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl1] This 'p' element should have a normal line-height, because negative values are not permitted for 'line-height'. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl2] This 'p' element should have a 'line-height' of 30 pixels. This will lead to a separation of 30 pixels between each baseline in the element, although the distance between actual character glyphs cannot be predicted. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl2] This 'p' element should have a 'line-height' of 30 pixels. This will lead to a separation of 30 pixels between each baseline in the element, and a separation of 15 pixels between the silver-backed areas. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl3] This 'p' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl4] This 'p' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl3] This 'div' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
[shrink] This text should have a font-size two-thirds that of the parent element, but the separation between baselines in this element should still be 30 pixels, as the value '200%' on the parent element causes a computed value to be inherited. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
[grow] This text should have a font-size half again as large as that of the parent element, but the separation between baselines in this element should still be 30 pixels, as the value '200%' on the parent element causes a computed value to be inherited. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
This is the end of the 'cl3' content. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
[cl4] This 'div' element should have a line-height of twice the font size, which should lead to a separation of 30 pixels between each baseline. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
[shrink] This text should have a font-size two-thirds that of the parent element, and the separation between baselines should also be two-thirds the parent; in other words, 20 pixels. This happens because the value '2' is inherited as a "scaling factor" that is multiplied by the value of the element's 'font-size' (in this case, 10px * 2). Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
[grow] This text should have a font-size half again as large as that of the parent element, and the separation between baselines should also be half again that of the parent; in other words, 45 pixels. This happens because the value '2' is inherited as a "scaling factor" that is multiplied by the value of the element's 'font-size' (in this case, 22.5px * 2). Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.
This is the end of the 'cl4' content. Extra text has been added to this element for the sole purpose of making it more likely that the content will be rendered using two or more lines of text.

[cl5] This 'p' element contains an inline element that is twice the size of the 'p' element's text, but it does not have an increased line-height. Thus, the inline element's content area will overlap other lines in the parent element. The inline element is [huge]. Note that the baselines of both the 'p' and the 'span' are aligned, since that's the default behavior. The overlap can go both upward and downward; that is, preceding and succeeding lines can be overlapped. The height of the line in which the 'span' appears may also be taller than normal due to the inline box of the 'span'.

[cl6] This 'p' element contains an inline element that is twice the size of the 'p' element's text, and which will inherit the scaling factor for its line-height. Thus, the inline element's content area will not overlap other lines in the parent element. The inline element is [huge]. Note that the line in which the inline element appears is increased in height to account for its presence. This does not increase the content area of the line of text, as the silver background demonstrates.

[cl5] This 'p' element contains an inline image that is twice the height of the 'p' element's text. Thus, the images will increase the height of the line in which it appears, and will not overlap content in lines above or below it. The inline element is test image. Note that the bottom of the 'img' is aligned with the baseline of the 'p', since that's the default behavior.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec10-08b.htm b/css2/sec10-08b.htm new file mode 100755 index 0000000..ebf35a0 --- /dev/null +++ b/css2/sec10-08b.htm @@ -0,0 +1 @@ + 10.8b vertical-align

CSS2 Test Suite: 10.8 vertical-align

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

p {font-size: 15px;}
p img {height: 50px; width: 15px;}
.cl1 {vertical-align: sub;}
.cl2 {vertical-align: super;}
.cl3 {vertical-align: top; font-size: 15px;}
.cl4 {vertical-align: text-top; font-size: 15px;}
.cl5 {vertical-align: middle; font-size: 15px;}
.cl6 {vertical-align: bottom; font-size: 15px;}
.cl7 {vertical-align: text-bottom; font-size: 15px;}
.cl8 {vertical-align: baseline; font-size: 15px;}
.cl9 {vertical-align: 50%; font-size: 15px; line-height: 20px;}
p.explain {margin-top: 2em; padding-top: 0.5em; border-top: 2px groove silver;}
p.ttopalign img, span.ttopalign {vertical-align: text-top;}
p.topalign img, span.topalign {vertical-align: top;}
p.midalign img, span.midalign {vertical-align: middle;}
big {font-size: 20px;}
small {font-size: 15px;}
img.px10 {height: 10px;}
img.px15 {height: 15px;}
img.px20 {height: 20px;}
img.px35 {height: 35px;}
img.px50 {height: 50px;}
img.px65 {height: 65px;}
img.px90 {height: 90px;}


test image[cl1] The first four words in this sentence should be subscript-aligned. The font size of the superscripted text should not be different from that of the parent element.

test image[cl2] The first four words in this sentence should be superscript-aligned. The font size of the subscripted text should not be different from that of the parent element.

test image[cl3] The first four words in this sentence should be top-aligned, which will align their tops with the top of the tallest element in the line (probably the orange rectangle).

test image [cl4] The first four words in this sentence should be text-top-aligned, which should align their tops with the top of the tallest text in the line.

test image [cl6] The first four words in this sentence should be 15px in size and bottom-aligned, which should align their bottom with the bottom of the lowest element in the line.

test image [cl7] The first eight words ("eight" has a descender) in this sentence should be 15px in size and text-bottom-aligned, which should align their bottom with the bottom of the lowest text (including descenders) in the line.

test image [cl8] The first four words in this sentence should be 15px in size and baseline-aligned, which should align their baseline with the baseline of the rest of the text in the line.

test image[cl9] The first four words in this sentence should have a font-size of 15px and a line-height of 20px; they are also 50%-aligned, which should raise them 10px relative to the natural baseline.

In the following paragraph, all images should be aligned with the top of the 15-pixel text, which is identical to the first section of text, whereas any size text should be aligned with the text baseline (which is the default value).

[ttopalign] This paragraph test image contains many images test image of varying heights test image and widths test image all of which test image should be aligned test image with the top of test image a 15-pixel text element test image regardless of the line in which test image the images appear. test image

In the following paragraph, all images should be aligned with the middle of the default text, whereas any text should be aligned with the text baseline (which is the default value).

[midalign] This paragraph test image contains many images test image of varying heights test image and widths test image all of which test image should be aligned test image with the middle of test image a 15-pixel text element test image regardless of the line in which test image the images appear. test image

In the following paragraph, all elements should be aligned with the top of the tallest element on the line, whether that element is an image or not. Each fragment of text has been 'span'ned appropriately in order to cause this to happen.

[topalign] This paragraph test image contains many images test image and some text test image of varying heights test image and widths test image all of which test image should be aligned test image with the top of test image the tallest element in test image whichever line the elements appear. test image


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec11-01-01.htm b/css2/sec11-01-01.htm new file mode 100755 index 0000000..6ca0139 --- /dev/null +++ b/css2/sec11-01-01.htm @@ -0,0 +1 @@ + 11.1.1 overflow

CSS2 Test Suite: 11.1.1 overflow

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

div.test {width: 100px; height: 100px; border: thin solid red;}
blockquote {width: 125px; height: 100px; margin-top: 50px; margin-left: 50px; border: thin dashed black;}
div.attributed-to {text-align: right; }

div.cl1 {overflow: visible;}
div.cl2 {overflow: hidden;}
div.cl3 {overflow: scroll;}
div.cl4 {overflow: auto;}


[cl1] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

- Groucho Marx

[cl2] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

- Groucho Marx

[cl3] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

- Groucho Marx

[cl4] I didn't like the play, but then I saw it under adverse conditions - the curtain was up.

- Groucho Marx

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec11-01-02.htm b/css2/sec11-01-02.htm new file mode 100755 index 0000000..9b532a1 --- /dev/null +++ b/css2/sec11-01-02.htm @@ -0,0 +1 @@ + 11.1.2 clip

CSS2 Test Suite: 11.1.2 clip

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {clip: rect(5px 10px 10px 5px); padding: 0; border: 1px solid gray; background: #FCC;}


Note: the behavior of 'clip' changed radically in CSS2.1. This test is provided as a historical curiosity. Browsers are not expected to pass it. Even those that pass it under 2.1 may appear to fail this test, and vice versa. The results seen on this page should not be taken as definitive.

[cl1] The content of this 'p' element should be clipped slightly: 5 pixels on the top, 10 pixels to the right, 10 pixels on the bottom, and 5 pixels to the left. This will cause the text to be cut off to a small extent on each side of the element.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec11-02.htm b/css2/sec11-02.htm new file mode 100755 index 0000000..cd17f03 --- /dev/null +++ b/css2/sec11-02.htm @@ -0,0 +1 @@ + 11.2 visibility

CSS2 Test Suite: 11.2 visibility

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {visibility: visible;}
.cl2 {visibility: hidden;}
.cl3 {visibility: collapse;}
table {background: silver;}
table td {background: #FF9;}

The following image has a class of 'cl1' and so should be visible: image. It should affect layout as normal.

The following image has a class of 'cl2' and so should not be visible: image. It should affect layout as normal even though it cannot be seen.

The following image has a class of 'cl3' and so should not be visible: image. It should affect layout as normal even though it cannot be seen.

In the following table, the cells of the second row should be invisible, but the space the row would have occupied should still be held open. The third row should be removed from the table altogether, and its space should not be held open.

r1c1r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3
r4c1r4c2r4c3
r5c1r5c2r5c3

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-01.htm b/css2/sec12-01.htm new file mode 100755 index 0000000..6e349d0 --- /dev/null +++ b/css2/sec12-01.htm @@ -0,0 +1 @@ + 12.1 :before and :after

CSS2 Test Suite: 12.1 :before and :after

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

BODY:after {
   content: "The End";
   display: block; margin-top: 2em;
   text-align: center; color: maroon;
}
P.note:before {content: "Note";}
P.note {color: purple;}

.fox1:before {content: "The quick brown fox ";}
.fox2:after {content: " jumped over the lazy dog.";}
.fox3:after {content: " the lazy dog.";}


A plain, unstyled paragraph. Note that, at the bottom of this page, there should be a block-level box containing the words "The End" centered, and colored maroon.

[note] This paragraph should have generated content inserted at its beginning, and the entire element (including the generated content) should be purple.


[fox1] jumped over the lazy dog.

[fox2] The quick brown fox

[fox1 fox3] jumped over


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-02.htm b/css2/sec12-02.htm new file mode 100755 index 0000000..9aea9ab --- /dev/null +++ b/css2/sec12-02.htm @@ -0,0 +1 @@ + 12.2 content

CSS2 Test Suite: 12.2 content

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

img:before {content: attr(alt);}
h1:before {
   display: block;
   text-align: center;
   content: "chapter\Ahoofdstuk\Achapitre";
}

The 'alt' text of the images on this page should appear before the images themselves.

Can you see me? Can you feel me? ...there has to be a trick.

An H1 element.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-04-01.htm b/css2/sec12-04-01.htm new file mode 100755 index 0000000..5e6733e --- /dev/null +++ b/css2/sec12-04-01.htm @@ -0,0 +1 @@ + 12.4.1 quotes

CSS2 Test Suite: 12.4.1 quotes

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

q:before {content: open-quote;}
q:after  {content: close-quote;}
.cl1 {quotes: '"' '"' "'" "'";}
.cl2 {quotes: "" "" "<" ">";}
.cl3 {quotes: "[[[" "]]]" "((" "))" "*-" "-*";}
.cl4 {quotes: "\201C" "\201D" "\2018" "\2019"; }


This 'p' element contains a quote element, which is provided to determine the user agent's default handling of the element: I hate quotations. (Ralph Waldo Emerson)

[cl1] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember. I didn't really believe him, but what could I do?

[cl2] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember. I didn't really believe him, but what could I do?

[cl3] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember anyone saying, I need some help, or else I would have helped. I didn't really believe him, but what could I do?

[cl4] This 'p' element contains a set of nested quotes which are: When I asked him about it, he said, I don't remember anyone saying, I need some help, or else I would have helped. I didn't really believe him, but what could I do?


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-05a.htm b/css2/sec12-05a.htm new file mode 100755 index 0000000..8ed7ced --- /dev/null +++ b/css2/sec12-05a.htm @@ -0,0 +1 @@ + 12.5a counter-reset

CSS2 Test Suite: 12.5 counter-reset

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

span:before {content: counter(ct1) "|" counter(ct2) "|" counter(ct3) "... ";}
li span:before {counter-increment: ct1; counter-reset: 0;}
li li span:before {counter-increment: ct2 2; counter-reset: 0;}
li li li span:before {counter-increment: ct3 -3; counter-reset: 0;}


The list items in the following set of lists all have 'span' elements, and each 'span' should be preceded with generated content in the form "a|b|c... " where the letters are incremented numbers. "a" numbers increment in ones, "b" in twos, and "c" in negative threes. Note that counters are reset for each sublist.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-05b.htm b/css2/sec12-05b.htm new file mode 100755 index 0000000..c05980d --- /dev/null +++ b/css2/sec12-05b.htm @@ -0,0 +1 @@ + 12.5b counter-increment

CSS2 Test Suite: 12.5 counter-increment

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

span:before {content: counter(ct1) "|" counter(ct2) "|" counter(ct3) "... ";}
li span:before {counter-increment: ct1;}
li li span:before {counter-increment: ct2 2;}
li li li span:before {counter-increment: ct3 -3;}


The list items in the following set of lists all have 'span' elements, and each 'span' should be preceded with generated content in the form "a|b|c... " where the letters are incremented numbers. "a" numbers increment in ones, "b" in twos, and "c" in negative threes. Note that counters are not reset for each sublist, or at any point, and so should use the default '0' as their base point.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-06-01.htm b/css2/sec12-06-01.htm new file mode 100755 index 0000000..00909ee --- /dev/null +++ b/css2/sec12-06-01.htm @@ -0,0 +1 @@ + 12.6.1 marker-offset

CSS2 Test Suite: 12.6.1 marker-offset

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

li:before {display: marker; marker-offset: 50px; width: 20px; border: 1px solid gray; background: #FF9;}
li {margin-left: 100px; padding-left: 0; border: 1px dotted gray; background: silver;}



[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-06-02a.htm b/css2/sec12-06-02a.htm new file mode 100755 index 0000000..200c20b --- /dev/null +++ b/css2/sec12-06-02a.htm @@ -0,0 +1 @@ + 12.6.2a list-style-type

CSS2 Test Suite: 12.6.2 list-style-type

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl0 {list-style-type: none;}
.cl1 {list-style-type: disc;}
.cl2 {list-style-type: circle;}
.cl3 {list-style-type: square;}
.cl4 {list-style-type: decimal;}
.cl5 {list-style-type: decimal-leading-zero;}
.cl6 {list-style-type: lower-roman;}
.cl7 {list-style-type: upper-roman;}
.cl8 {list-style-type: lower-greek;}
.cl9 {list-style-type: lower-alpha;}
.cl10 {list-style-type: lower-latin;}
.cl11 {list-style-type: upper-alpha;}
.cl12 {list-style-type: upper-latin;}
.cl13 {list-style-type: hebrew;}
.cl14 {list-style-type: armenian;}
.cl15 {list-style-type: georgian;}
.cl16 {list-style-type: cjk-ideographic;}
.cl17 {list-style-type: hiragana;}
.cl18 {list-style-type: katakana;}
.cl19 {list-style-type: hiragana-iroha;}
.cl20 {list-style-type: katakana-iroha;}
.parent {list-style-type: square;}
.inh1 {list-style-type: circle;}


  1. [cl0] This ordered list...
  2. ...should have no markers...
  3. ...next to its list items.
  1. [cl4] This ordered list...
  2. ...should have decimal markers...
  3. ...next to its list items.
  1. [cl5] This ordered list...
  2. ...should have decimal-leading-zero markers...
  3. ...next to its list items.
  1. [cl6] This ordered list...
  2. ...should have lower-roman markers...
  3. ...next to its list items.
  1. [cl7] This ordered list...
  2. ...should have upper-roman markers...
  3. ...next to its list items.
  1. [cl8] This ordered list...
  2. ...should have lower-greek markers...
  3. ...next to its list items.
  1. [cl9] This ordered list...
  2. ...should have lower-alpha markers...
  3. ...next to its list items.
  1. [cl10] This ordered list...
  2. ...should have lower-latin markers...
  3. ...next to its list items.
  1. [cl11] This ordered list...
  2. ...should have upper-alpha markers...
  3. ...next to its list items.
  1. [cl12] This ordered list...
  2. ...should have upper-latin markers...
  3. ...next to its list items.
  1. [cl13] This ordered list...
  2. ...should have hebrew markers...
  3. ...next to its list items.
  1. [cl14] This ordered list...
  2. ...should have armenian markers...
  3. ...next to its list items.
  1. [cl15] This ordered list...
  2. ...should have georgian markers...
  3. ...next to its list items.
  1. [cl16] This ordered list...
  2. ...should have cjk-ideographic markers...
  3. ...next to its list items.
  1. [cl17] This ordered list...
  2. ...should have hiragana markers...
  3. ...next to its list items.
  1. [cl18] This ordered list...
  2. ...should have katakana markers...
  3. ...next to its list items.
  1. [cl19] This ordered list...
  2. ...should have hiragana-iroha markers...
  3. ...next to its list items.
  1. [cl20] This ordered list...
  2. ...should have katakana-iroha markers...
  3. ...next to its list items.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-06-02b.htm b/css2/sec12-06-02b.htm new file mode 100755 index 0000000..a93830e --- /dev/null +++ b/css2/sec12-06-02b.htm @@ -0,0 +1 @@ + 12.6.2b list-style-image

CSS2 Test Suite: 12.6.2 list-style-image

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {list-style-image: url(pix/orancirc.gif);}
.cl2 {list-style-image: none;}
.parent {list-style-image: none;}
.inh1 {list-style-image: url(pix/orancirc.gif);}




[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-06-02c.htm b/css2/sec12-06-02c.htm new file mode 100755 index 0000000..0b02539 --- /dev/null +++ b/css2/sec12-06-02c.htm @@ -0,0 +1 @@ + 12.6.2c list-style-position

CSS2 Test Suite: 12.6.2 list-style-position

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {list-style-position: outside;}
.cl2 {list-style-position: inside;}
.parent {list-style-position: inside;}
.inh1 {list-style-position: outside;}




[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec12-06-02d.htm b/css2/sec12-06-02d.htm new file mode 100755 index 0000000..5f1501a --- /dev/null +++ b/css2/sec12-06-02d.htm @@ -0,0 +1 @@ + 12.6.2d list-style

CSS2 Test Suite: 12.6.2 list-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {list-style: lower-roman;}
.cl2 {list-style: inside upper-alpha;}
.cl3 {list-style: outside url(pix/orancirc.gif) circle;}
.cl3 .li-test {list-style-image: none;}
.parent {list-style: inside disc url(pix/orancirc.gif);}
.inh1 {list-style: square outside;}


  1. [cl1] This list items in this ordered list...
  2. ...should have lower-roman markers outside the content...
  3. ...for each item in the list.
  1. [cl2] This list items in this ordered list...
  2. ...should have upper-alpha markers inside the content...
  3. ...for each item in the list.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-01.htm b/css2/sec14-01.htm new file mode 100755 index 0000000..a72cd23 --- /dev/null +++ b/css2/sec14-01.htm @@ -0,0 +1 @@ + 14.1 color

CSS2 Test Suite: 14.1 color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: green;}.inh1 {color: red;}


This 'p' element has no styles assign to it, and serves as a reference point.

This 'p' element should be green.


[parent] This 'div' element has no explicitly assigned styles.
[inh1] This 'div' element should have the same text color as its parent, as it has a style attribute set to inherit the color value. If it is red, the 'inherit' test has been failed. [/inh1]
This is the end of the parent 'div' element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01a.htm b/css2/sec14-02-01a.htm new file mode 100755 index 0000000..545985d --- /dev/null +++ b/css2/sec14-02-01a.htm @@ -0,0 +1 @@ + 14.2.1a background-color

CSS2 Test Suite: 14.2.1 background-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {background-color: green;}
.cl2 {background-color: transparent;}
.parent {background-color: silver;}
.inh1 {background-color: red;}


[cl1] This 'p' element should have a green background that completely fills its content-area.

[cl2] This 'p' element should have a transparent background that completely fills its content-area; this will allow the background of any ancestor elements that encompass it to "shine through."

[cl1] This 'p' element contains a 'span' that has been given a class of 'cl2'. The transparent background of [cl2]the inline 'span' should allow the 'p' element's green background to "shine through."


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a silver background.
[inh1] This 'div' element should have the same silver background as its parent, as it has a style attribute set to inherit the background-color value. If the background is red, the 'inherit' test has been failed.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01b.htm b/css2/sec14-02-01b.htm new file mode 100755 index 0000000..ee5e237 --- /dev/null +++ b/css2/sec14-02-01b.htm @@ -0,0 +1 @@ + 14.2.1b background-image

CSS2 Test Suite: 14.2.1 background-image

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {background-image: url(pix/smgr-bg.gif);}
.cl2 {background-image: none;}
.parent {background-image: url(pix/crosshair2.gif);}
.inh1 {background-image: url(pix/redsqr.gif);}


[cl1] This 'p' element should have a background that completely fills its content-area. This background is a small green grid image that has been repeatedly "tiled" throughout the background area of the element.

[cl2] This 'p' element should have a transparent background that completely fills its content-area; this will allow the background of any ancestor elements that encompass it to "shine through."

[cl1] This 'p' element contains a 'span' that has been given a class of 'cl2'. The transparent background of [cl2]the inline 'span' should allow the 'p' element's green-grid background to "shine through."


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a background pattern of a crosshair image.
[inh1] This 'div' element should have the same crosshair-tiled background as its parent, as it has a style attribute set to inherit the background-image value. If the background is red, the 'inherit' test has been failed. If the crosshair pattern does not re-start itself in the top left corner of this child 'div', then the test has also been failed; by inheriting the image, this 'div' has a pattern independent of its parent.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01c.htm b/css2/sec14-02-01c.htm new file mode 100755 index 0000000..e837716 --- /dev/null +++ b/css2/sec14-02-01c.htm @@ -0,0 +1 @@ + 14.2.1c background-repeat

CSS2 Test Suite: 14.2.1 background-repeat

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-image: url(pix/smgr-bg.gif);}
.cl1 {background-repeat: no-repeat;}
.cl2 {background-repeat: repeat-x;}
.cl3 {background-repeat: repeat-y;}
.cl4 {background-repeat: repeat;}
.parent, .inh1 {background-image: url(pix/smgr-bg.gif);}
.parent {background-repeat: no-repeat;}
.inh1 {background-repeat: repeat;}


[test] This 'p' element should have a green grid as its background, extending through the content-area of the element.

[test cl1] This 'p' element should have a green image in the top left corner of the element's background area.

[test cl2] This 'p' element should have a green stripe running along the top edge of the element's background area.

[test cl3] This 'p' element should have a green stripe running down the left side of the element's background area.

[test cl4] This 'p' element should have a green grid throughout the entirety of the element's background area.


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a single small green image in its top left corner.
[inh1] This 'div' element should have a single green image in its top left corner, the same as its parent, as it has a style attribute set to inherit the background-image value. If the background is filled with a green grid, the 'inherit' test has been failed.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01d.htm b/css2/sec14-02-01d.htm new file mode 100755 index 0000000..3d28626 --- /dev/null +++ b/css2/sec14-02-01d.htm @@ -0,0 +1 @@ + 14.2.1d background-attachment

CSS2 Test Suite: 14.2.1 background-attachment

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

body {background-image: url(pix/test1.jpg); background-attachment: fixed;}
.test {background-image: url(pix/test2.jpg); background-attachment: fixed;
  padding: 50px; border: 1px dotted silver;}
.cl1 {background-repeat: repeat-x;}
.cl2 {background-attachment: scroll;}
.parent, .inh1 {background-image: url(pix/test2.jpg);}
.parent {background-attachment: fixed;}
.inh1 {background-attachment: scroll;}

The background of this document should be a repeated pattern of the word "TEST" at 45-degree angles. This background should fill the entire viewport and not scroll when the document itself is scrolled. This document will be extra-long in order to create a scrolling effect, but consider resizing the browser window if your display area is so large that the entire document can be seen without scrolling.

[test] The background of this 'p' element should be filled with a tiled "TEST" pattern where the letters in the words "TEST" are filled in. This background should line up precisely with the background of the 'body' element. As the document is scrolled, the effect should be that of a moving window through which the filled-in "TEST" background is visible. The background of this element and that of the 'body' element should always line up precisely, and should never move along with the scrolling document.

[test cl1] The background of this 'p' element should be transparent on document load, so the 'body' background will "shine through" this element. As the document is scrolled, pay attention when this element reaches the top of the browser window. As it scrolled past the top of the window, the "TEST" pattern should shift to a single horizontal stripe of filled-in letters. Depending on the height of this element, it may be possible that the single row is visible at once, or only portions of it may be visible.

[test cl1] The background of this 'p' element should be a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in. This tile will start at the top left corner of the element's background area. As the document is scrolled, the pattern will scroll along with it. The pattern may or may not line up with the 'body' element's background, but it is most likely that it will not. If it does, resize the browser window so the patterns do not line up.

A quotation of the relevant section of the CSS2 specification:

'background-attachment'
Value:  scroll | fixed | inherit
Initial:  scroll
Applies to:  all elements
Inherited:  no
Percentages:  N/A
Media:  visual

If a background image is specified, this property specifies whether it is fixed with regard to the viewport ('fixed') or scrolls along with the document ('scroll').

Even if the image is fixed, it is still only visible when it is in the background or padding area of the element. Thus, unless the image is tiled ('background-repeat: repeat'), it may be invisible.

Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in. This background should align with the background pattern of the 'body' element at all times.
[inh1] This 'div' element should have a repeated pattern of the word "TEST" at 45-degree angles and the letters filled in, the same as its parent, as it has a style attribute set to inherit the background-attachment value. If the background pattern begins at the top left corner of this element's background area, or it scrolls along with the document, or both, the test has been failed.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01e.htm b/css2/sec14-02-01e.htm new file mode 100755 index 0000000..f02764e --- /dev/null +++ b/css2/sec14-02-01e.htm @@ -0,0 +1 @@ + 14.2.1e background-position

CSS2 Test Suite: 14.2.1 background-position

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background-image: url(pix/smgr-bg.gif); background-repeat: no-repeat;
  border: 1px dashed gray;}
.cl1 {background-position: center;}
.cl2 {background-position: right top;}
.cl3 {background-position: bottom left;}
.cl4 {background-position: center left;}
.cl5 {background-position: center top;}
.cl6 {background-position: 50% 50%;}
.cl7 {background-position: 10px 10px;}
.cl8 {background-position: 10px 50%;}
.cl9 {background-position: 50% 10px;}
.cl10 {background-position: top 50%;}
.parent, .inh1 {background-image: url(pix/smgr-bg.gif); background-repeat: no-repeat;}
.parent {background-position: top right;}
.inh1 {background-position: center left;}

[test] This 'p' element should have a single small green image in the top left corner of its background area.

[test cl1] This 'p' element should have a single small green image in the center of its background area.

[test cl2] This 'p' element should have a single small green image in the top right corner of its background area.

[test cl3] This 'p' element should have a single small green image in the bottom left corner of its background area.

[test cl4] This 'p' element should have a single small green image in the center left of its background area.

[test cl5] This 'p' element should have a single small green image top center of its background area.

[test cl6] This 'p' element should have a single small green image in the center of its background area.

[test cl7] This 'p' element should have a single small green image whose top left corner is 10 pixels down and 10 pixels to the left of the top left corner of the background area.

[test cl8] This 'p' element should have a single small green image whose left side is 10 pixels to the right of the left side of the background area, and which is vertically centered within the background area.

[test cl9] This 'p' element should have a single small green image which is horizontally centered within the background area, and whose top side is 10 pixels down from the top edge of the background area.

[test cl10] This 'p' element should have a single small green image in the top left corner of the background area, as the value supplied is invalid and must be ignored.


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a single green image in the top right corner of the background area.
[inh1] This 'div' element should have a single green image in the top right corner of the background area, the same as its parent, as it has a style attribute set to inherit the background-position value. If the image appears at the center of the left side of the background area, the test has been failed.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec14-02-01f.htm b/css2/sec14-02-01f.htm new file mode 100755 index 0000000..6d261a2 --- /dev/null +++ b/css2/sec14-02-01f.htm @@ -0,0 +1 @@ + 14.2.1f background

CSS2 Test Suite: 14.2.1 background

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.test {background: lime;}
.cl1 {background: green;}
.cl2 {background: green url(pix/smgr-bg.gif) top center repeat-x;}
.cl3 {background: silver url(pix/crosshair.gif) center no-repeat;}
.cl4 {background: url(pix/crosshair.gif) no-repeat;}
.cl5 {background: transparent url(pix/vertical-wave.gif) center repeat-y fixed;}
.parent {background: silver url(pix/crosshair2.gif) top right repeat-x;}
.inh {background: #FCC url(pix/redsqr.gif) repeat-y;}


[test] This 'p' element should have a lime background.

[test cl1] This 'p' element should have a green background. This is distinct from a lime background.

test cl2] This 'p' element should have a green background, except along the top, where a green-grid strip should originate at the top center of the background area and repeat to both the right and the left of that point.

test cl3] This 'p' element should have a silver background and a single crosshair image at the center of the background area. This image should not tile in any direction.

test cl4] This 'p' element should have a single crosshair image at the top left corner of its background area, and the rest of the background should be transparent. If the rest of the background is lime, then the test has been failed.

test cl5] This 'p' element should have a wavy stripe down the center of its background area, and this stripe should remain stationary while the document is scrolled. In other words, the element should seem as if it is a moving window through which different parts of the wavy image are visible. In order to make the effect more obvious, extra text is appended to the content of this element in order to increase its height. Also consider resizing the browser window to be more narrow so that the element becomes taller and is (visually) pushed further down in the document.

A relevant quotation from the CSS2 specification:

'background'
Value:  [<'background-color'> || <'background-image'> || <'background-repeat'> || <'background-attachment'> || <'background-position'>] | inherit
Initial:  not defined for shorthand properties
Applies to:  all elements
Inherited:  no
Percentages:  allowed on 'background-position'
Media:  visual

The 'background' property is a shorthand property for setting the individual background properties (i.e., 'background-color', 'background-image', 'background-repeat', 'background-attachment' and 'background-position') at the same place in the style sheet.

The 'background' property first sets all the individual background properties to their initial values, then assigns explicit values given in the declaration.


[parent] This 'div' element is the parent of another 'div' that is used to test inheritance. The parent has a silver background and a horizontal stripe of green crosshair images running along the top side of its background area, beginning in the top right corner of the background area.
[inh1] This 'div' element should have a silver background and a horizontal stripe of green crosshair images running along the top side of its background area, beginning in the top right corner of the background area, the same as its parent, as it has a style attribute set to inherit the background value. If the background is light red with a bright red vertical stripe through its center, the test has been failed.
This is the end of the parent element.

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-02.htm b/css2/sec15-02-02.htm new file mode 100755 index 0000000..a8c96e0 --- /dev/null +++ b/css2/sec15-02-02.htm @@ -0,0 +1 @@ + 15.2.2 font-family

CSS2 Test Suite: 15.2.2 font-family

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

DIV.one {font-family: monospace;}
.cl1 {font-family: serif;}
.cl2 {font-family: sans-serif;}
.cl3 {font-family: cursive;}
.cl4 {font-family: fantasy;}
.cl5 {font-family: monospace;}
.cl6 {font-family: sans-serif,cursive;}
.cl7 {font-family: monospace,serif;}
div.parent {font-family: sans-serif;}
div.inh1 {font-family: cursive;}
div.inh2 {font-family: monospace;}


This sentence is normal for the second division, which is the next five paragraph elements; it should be dislpayed using a monospace font.

[cl1] This sentence should be in a serif font.

[cl2] This sentence should be in a sans-serif font.

[cl3] This sentence should be in a cursive font.

[cl4] This sentence should be in a fantasy font.

[cl5] This sentence should be in a monospace font.

[cl6] This sentence should be in a sans-serif font, not cursive.

[cl7] This sentence should be in a monospace font, not serif.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a sans-serif font for its display, as it has a style attribute set to inherit the font-family value. [/div.inh1]
[div.inh2] This DIV should use a sans-serif font for its display, as it has a style attribute set to inherit the font-family value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-03a.htm b/css2/sec15-02-03a.htm new file mode 100755 index 0000000..d8c5a8c --- /dev/null +++ b/css2/sec15-02-03a.htm @@ -0,0 +1 @@ + 15.2.3a font-style

CSS2 Test Suite: 15.2.3 font-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font-style: italic;}
.cl2 {font-style: oblique;}
.cl3, I {font-style: normal;}
div.parent {font-style: normal;}
div.inh1 {font-style: italic;}
div.inh2 {font-style: oblique;}


[cl1] The font in this paragraph should be in italics, but the last word of the sentence should be [cl3] normal.

[cl2] The font in this paragraph should be oblique.

[I] This italics element should be normal instead of italicized.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normal (non-italic) font for its display, as it has a style attribute set to inherit the font-style value. [/div.inh1]
[div.inh2] This DIV should use a normal (non-oblique) font for its display, as it has a style attribute set to inherit the font-style value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-03b.htm b/css2/sec15-02-03b.htm new file mode 100755 index 0000000..07fdb12 --- /dev/null +++ b/css2/sec15-02-03b.htm @@ -0,0 +1 @@ + 15.2.3b font-variant

CSS2 Test Suite: 15.2.3 font-variant

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font-variant: small-caps;}
.cl2 {font-variant: normal;}
div.parent {font-variant: normal;}
div.inh1 {font-variant: small-caps;}


[cl1] This Paragraph should be in Small Caps.

[cl1] This Paragraph should be in Small Caps, but the Last three Words in the Sentence [cl2] should be Normal.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normal (non-small-caps) font for its display, as it has a style attribute set to inherit the font-variant value. [/div.inh1]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-03c.htm b/css2/sec15-02-03c.htm new file mode 100755 index 0000000..e635396 --- /dev/null +++ b/css2/sec15-02-03c.htm @@ -0,0 +1 @@ + 15.2.3c font-weight

CSS2 Test Suite: 15.2.3 font-weight

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font-weight: bold;}
.cl2, B {font-weight: lighter;}
.cl3 {font-weight: bolder;}
.cl4 {font-weight: normal;}
.cl5w1 {font-weight: 100;}
.cl5w2 {font-weight: 200;}
.cl5w3 {font-weight: 300;}
.cl5w4 {font-weight: 400;}
.cl5w5 {font-weight: 500;}
.cl5w6 {font-weight: 600;}
.cl5w7 {font-weight: 700;}
.cl5w8 {font-weight: 800;}
.cl5w9 {font-weight: 900;}
div.parent {font-weight: normal;}
div.inh1 {font-weight: bold;}
div.inh2 {font-weight: 900;}


[cl1] The font for this paragraph should be bold.

[cl1] The font for this paragraph should be bold, but the last three words in the sentence [cl2] should be normal.

[B] The font for this bold element should be normal (boldface made lighter).

[cl3] The font for this paragraph should be bolder than normal.

This is a heading-4.

[cl3] This is a bolder heading-4.

The following list should contain list items in which the content of each item is the same weight.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normally weighted font for its display, as it has a style attribute set to inherit the font-weight value. [/div.inh1]
[div.inh2] This DIV should use a normally weighted font for its display, as it has a style attribute set to inherit the font-weight value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-03d.htm b/css2/sec15-02-03d.htm new file mode 100755 index 0000000..96217aa --- /dev/null +++ b/css2/sec15-02-03d.htm @@ -0,0 +1 @@ + 15.2.3d font-stretch

CSS2 Test Suite: 15.2.3 font-stretch

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cln {font-stretch: narrower;}
.clw {font-stretch: wider;}
.cl1 {font-stretch: ultra-condensed;}
.cl2 {font-stretch: extra-condensed;}
.cl3 {font-stretch: condensed;}
.cl4 {font-stretch: semi-condensed;}
.cl5 {font-stretch: normal;}
.cl6 {font-stretch: semi-expanded;}
.cl7 {font-stretch: expanded;}
.cl8 {font-stretch: extra-expanded;}
.cl9 {font-stretch: ultra-expanded;}
div.parent {font-stretch: normal;}
div.inh1 {font-stretch: expanded;}
div.inh2 {font-stretch: ultra-condensed;}


[cl1] This text should have an ultra-condensed font, [cln] while this text should also be ultra-condensed [clw] and this text should be wider.

[cl2] This text should have an extra-condensed font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl3] This text should have a condensed font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl4] This text should have a semi-condensed font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl5] This text should have a normal font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl6] This text should have a semi-expanded font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl7] This text should have a expanded font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl8] This text should have an extra-expanded font, [cln] while this text should be narrower [clw] and this text should be wider.

[cl9] This text should have an extra-expanded font, [cln] while this text should be narrower [clw] and this text should also be ultra-expanded.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normally stretched font for its display, as it has a style attribute set to inherit the font-stretch value. [/div.inh1]
[div.inh2] This DIV should use a normally stretched font for its display, as it has a style attribute set to inherit the font-stretch value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-04a.htm b/css2/sec15-02-04a.htm new file mode 100755 index 0000000..3f6c452 --- /dev/null +++ b/css2/sec15-02-04a.htm @@ -0,0 +1 @@ + 15.2.4a font-size

CSS2 Test Suite: 15.2.4 font-size

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font-size: medium;}
.cl2 {font-size: larger;}
.cl3 {font-size: smaller;}
.cl4 {font-size: xx-small;}
.cl5 {font-size: x-small;}
.cl6 {font-size: small;}
.cl7 {font-size: large;}
.cl8 {font-size: x-large;}
.cl9 {font-size: xx-large;}
.cl10 {font-size: 0.5in;}
.cl11 {font-size: 1cm;}
.cl12 {font-size: 10mm;}
.cl13 {font-size: 18pt;}
.cl14 {font-size: 1.5pc;}
.cl15 {font-size: 2em;}
.cl16 {font-size: 3ex;}
.cl17 {font-size: 25px;}
.cl18 {font-size: 200%;}
.cl19 {font-size: -0.5in;}
div.parent {font-size: medium;}
div.inh1 {font-size: xx-small;}
div.inh2 {font-size: xx-large;}


This paragraph element is unstyled, so the size of the font in this element is the default size for this user agent.

[cl1] The font of this paragraph has been set to medium, which may or may not be the same size as unstyled text.

[cl2] The font of this paragraph should be larger than unstyled text.

[cl3] The font of this paragraph should be smaller than unstyled text.

[cl4] The font of this paragraph should be very small, but the last three words in the sentence [cl1] should be medium.

[cl5] The font of this paragraph should be rather small, but the last three words in the sentence [cl1] should be medium.

[cl6] The font of this paragraph should be small, but the last three words in the sentence [cl1] should be medium.

[cl7] The font of this paragraph should be large, but the last three words in the sentence [cl1] should be medium.

[cl8] The font of this paragraph should be rather large, but the last three words in the sentence [cl1] should be medium.

[cl9] The font of this paragraph should be very large, but the last three words in the sentence [cl1] should be medium.

[cl10] The font of this paragraph should be half an inch tall.

[cl11] The font of this paragraph should be one centimeter tall.

[cl12] The font of this paragraph should be ten millimeters tall.

[cl13] The font of this paragraph should be eighteen points tall.

[cl14] The font of this paragraph should be one and one half picas tall.

[cl15] The font of this paragraph should be two em tall.

[cl16] The font of this paragraph should be three ex tall.

[cl17] The font of this paragraph should be twenty-five pixels tall.

[cl18] The font of this paragraph should be twice normal size.

[cl19] The font of this paragraph should be normal size, since no negative values are allowed and therefore should be ignored.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size value. [/div.inh1]
[div.inh2] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-04b.htm b/css2/sec15-02-04b.htm new file mode 100755 index 0000000..c4d9717 --- /dev/null +++ b/css2/sec15-02-04b.htm @@ -0,0 +1 @@ + 15.2.4b font-size-adjust

CSS2 Test Suite: 15.2.4 font-size-adjust

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font: 14px "Greek Isles", serif; font-size-adjust: 1;}
.cl2 {font: 14px "Greek Isles", serif; font-size-adjust: 2;}
.cl3 {font: 14px "Greek Isles", serif; font-size-adjust: 0.75;}
div.parent {font-size-adjust: none; font: 14px "Greek Isles", serif;}
div.inh1 {font-size-adjust: 2;}
div.inh2 {font-size-adjust: 0.75;}


[p.cl1] This paragraph should use a serif font whose font-size is very close to 14px. [/p.cl1]

[p.cl2] This paragraph should use a serif font whose font-size is very close to 28px. [/p.cl2]

[p.cl3] This paragraph should use a serif font whose font-size is very close to 9px. [/p.cl3]


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size-adjust value. [/div.inh1]
[div.inh2] This DIV should use a medium-size font for its display, as it has a style attribute set to inherit the font-size-adjust value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec15-02-05.htm b/css2/sec15-02-05.htm new file mode 100755 index 0000000..31032f5 --- /dev/null +++ b/css2/sec15-02-05.htm @@ -0,0 +1 @@ + 15.2.5 font

CSS2 Test Suite: 15.2.5 font

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {font: bold 12px monospace;}
.cl2 {font: 700 italic small-caps 16px/12px Helvetica, sans-serif;}
.cl3 {font: 1em/1.0 serif;}
.cl-sys-a {font: caption;}
.cl-sys-b {font: icon;}
.cl-sys-c {font: menu;}
.cl-sys-d {font: message-box;}
.cl-sys-e {font: small-caption;}
.cl-sys-f {font: status-bar;}
div.parent {font: normal normal normal medium sans-serif;}
div.inh1 {font: bold italic small-caps 28px serif;}
div.inh2 {font: normal oblique small-caps 0.8em cursive;}


[p.cl1] This paragraph should use a boldfaced 12px monospace font. [/p.cl1]

[p.cl2] This paragraph should use a boldfaced italic small-caps 16px sans-serif font (Helvetica if available) with a line-height of 12px, which should cause the lines to overlap ever so slightly. [/p.cl2]

[p.cl3] This paragraph should use a normal medium-size serif font. [/p.cl3]

[p.cl-sys-a] This paragraph should use the system font for captioned controls (e.g. buttons, drop-downs, etc.). [/p.cl-sys-a]

[p.cl-sys-b] This paragraph should use the system font for icon labels. [/p.cl-sys-b]

[p.cl-sys-c] This paragraph should use the system font for menu entries (e.g., dropdown menus and menu lists). [/p.cl-sys-c]

[p.cl-sys-d] This paragraph should use the system font for dialog boxes. [/p.cl-sys-d]

[p.cl-sys-e] This paragraph should use the system font for labelling small controls. [/p.cl-sys-e]

[p.cl-sys-f] This paragraph should use the system font for window status bars. [/p.cl-sys-f]


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normal medium-size sans-serif font for its display, as it has a style attribute set to inherit the font value. [/div.inh1]
[div.inh2] This DIV should use a normal medium-size sans-serif font for its display, as it has a style attribute set to inherit the font value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-01.htm b/css2/sec16-01.htm new file mode 100755 index 0000000..3db814f --- /dev/null +++ b/css2/sec16-01.htm @@ -0,0 +1 @@ + 16.1 text-indent

CSS2 Test Suite: 16.1 text-indent

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {text-indent: 0.5in; background: aqua;}
.cl2 {text-indent: 2cm; background: aqua;}
.cl3 {text-indent: 20mm; background: aqua;}
.cl4 {text-indent: 24pt; background: aqua;}
.cl5 {text-indent: 2pc; background: aqua;}
.cl6 {text-indent: 2em; background: aqua;}
.cl7 {text-indent: 2ex; background: aqua;}
.cl8 {text-indent: 50%; background: aqua;}
.cl9 {text-indent: 25px; background: aqua;}
blockquote {text-indent: 50%; background: aqua;}
div.parent {text-indent: 50%; width: 400px;}
div.inh1 {text-indent: 10px; margin: 25px;}
div.inh2 {text-indent: 10%; margin: 25px;}


[cl1] The first line of this paragraph should be indented half an inch. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl2] The first line of this sentence should be indented two centimeters. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl3] The first line of this sentence should be indented twenty millimeters. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl4] The first line of this sentence should be indented twenty-four points. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl5] The first line of this sentence should be indented two picas. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl6] The first line of this sentence should be indented two em. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl7] The first line of this sentence should be indented two ex. No other line in the paragraph should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[cl8] The first line of this sentence should be indented halfway across the page, but the rest of it should be flush with the normal left margin of the page. Line-wrapping will have to occur in order to properly test this assertion.

[cl9] The first line of this sentence should be indented 25 pixels, but the rest of it should be flush with the normal left margin of the page. Line-wrapping will have to occur in order to properly test this assertion.

[cl1] Only the first line of this sentence should be indented half an inch,
no matter where the lines might start, and
regardless of any other markup which may be present.

[blockquote] The first line of this BLOCKQUOTE element should have a text indent equal to 50% of the BODY element's width, since BLOCKQUOTE is a child of BODY. No other line in the element should be so indented, although line-wrapping will have to occur in order to properly test this assertion.

[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have its first line indented by half the width of its parent element, as it has a style attribute set to inherit the text-indent value. [/div.inh1]
[div.inh2] This DIV should have its first line indented by half the width of its parent element, as it has a style attribute set to inherit the text-indent value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-02.htm b/css2/sec16-02.htm new file mode 100755 index 0000000..bdf0a17 --- /dev/null +++ b/css2/sec16-02.htm @@ -0,0 +1 @@ + 16.2 text-align

CSS2 Test Suite: 16.2 text-align

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {text-align: left;}
.cl2 {text-align: right;}
.cl3 {text-align: center;}
.cl4 {text-align: justify;}
.cl5 {text-align: ".";}div.parent {text-align: left;}
div.inh1 {text-align: right;}
div.inh2 {text-align: center;}


[cl1] This sentence should be left-justified.

[cl2] This sentence should be right-justified.

[cl3] This sentence should be centered.

[cl4] This sentence should be fully justified, which means that the right and left margins of this paragraph should line up, no matter how long the paragraph becomes; the exception, of course, is the last line, which should be left-justified in Western languages.

In the following table, all content should align on the period (.) symbol.

451.27$999.95
578.1$12,499.95
450#9.95
1923875.934572$59.95
3.14159265$1499.95

[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have its text left aligned, as it has a style attribute set to inherit the text-align value. [/div.inh1]
[div.inh2] This DIV should have its text left aligned, as it has a style attribute set to inherit the text-align value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-03-01.htm b/css2/sec16-03-01.htm new file mode 100755 index 0000000..d7ba2ad --- /dev/null +++ b/css2/sec16-03-01.htm @@ -0,0 +1 @@ + 16.3.1 text-decoration

CSS2 Test Suite: 16.3.1 text-decoration

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {text-decoration: underline;}
.cl2 {text-decoration: overline;}
.cl3 {text-decoration: line-through;}
.cl4 {text-decoration: blink;}
B.cl5 {text-decoration: none;}
.cl6 {text-decoration: underline overline;}
.cl7 {text-decoration: underline overline line-through;}
div.parent {text-decoration: none;}
div.inh1 {text-decoration: underline;}
div.inh2 {text-decoration: line-through;}


[cl1] The text of this paragraph should be underlined.

[cl2] The text of this paragraph should be overlined.

[cl3] The text of this paragraph should be stricken (linethrough).

[cl4] The text of this paragraph should be blinking. (It is not required, however, that UAs support this behavior.)

[cl1] The text of this paragraph should be underlined. The boldfaced text in this paragraph [cl5] should also be underlined. This is because the parent's underline will 'span' the boldfaced text, even if the inline element has no underline of its own.

[cl6] The text of this paragraph should be underlined and overlined.

[cl7] The text of this paragraph should be underlined, overlined, and stricken.

There should be nothing visible between this paragraph and the one above (there is an empty paragraph element with class of seven between them).

[cl1] Text decorations only apply to the text of an element, so the image at the end of this sentence should not be overlined: [Image]. The underline of the parent element should hold true beneath the image, however, since text-decoration 'spans' child elements.

[cl1] The underlining in this paragraph should be green, no matter what the text color may be.

[cl1] The colors of the underlining in this paragraph should be the same as that of the parent text (that is, the first word in the sentence, which should be black).


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use no text decoration for its display, as it has a style attribute set to inherit the text-decoration value. [/div.inh1]
[div.inh2] This DIV should use no text decoration for its display, as it has a style attribute set to inherit the text-decoration value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-03-02.htm b/css2/sec16-03-02.htm new file mode 100755 index 0000000..93eba7e --- /dev/null +++ b/css2/sec16-03-02.htm @@ -0,0 +1 @@ + 16.3.2 text-shadow

CSS2 Test Suite: 16.3.2 text-shadow

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

h3.cl1{text-shadow: gray 0.5em 0.5em 2px;}
h3.cl2 {text-shadow: purple 0 0 5px;}
h3.cl3 {text-shadow: red -10px -0.5em 0.25em, green 1mm 1px 0, blue 0 0.33em 10px;}
div.parent {text-shadow: none;}
div.inh1 {text-shadow: purple 3px 5px;}
div.inh2 {text-shadow: red -10px;}


[h3.cl1] This should have a gray shadow [/h3.cl1]

[h3.cl2] This should have a purple "glow" [/h3.cl2]

[h3.cl3] This should have a wild set of shadows [/h3.cl3]


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have no text shadow, as it has a style attribute set to inherit the text-shadow value. [/div.inh1]
[div.inh2] This DIV should have no text shadow, as it has a style attribute set to inherit the text-shadow value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-04a.htm b/css2/sec16-04a.htm new file mode 100755 index 0000000..e0099c5 --- /dev/null +++ b/css2/sec16-04a.htm @@ -0,0 +1 @@ + 16.4a letter-spacing

CSS2 Test Suite: 16.4 letter-spacing

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {letter-spacing: 0.3in;}
.cl2 {letter-spacing: 0.5cm;}
.cl3 {letter-spacing: 5mm;}
.cl4 {letter-spacing: 3pt;}
.cl5 {letter-spacing: 0.25pc;}
.cl6 {letter-spacing: 1em;}
.cl7 {letter-spacing: 1ex;}
.cl8 {letter-spacing: 5px;}
.cl9 {letter-spacing: normal;}
.cl10 {letter-spacing: 300%;}
.cl11 {letter-spacing: -0.1em;}div.parent {letter-spacing: normal;}
div.inh1 {letter-spacing: 1em;}
div.inh2 {letter-spacing: -4px;}


[cl1] The letters in this paragraph should have extra space between them.

[cl2] The letters in this paragraph should have extra space between them.

[cl3] The letters in this paragraph should have extra space between them.

[cl4] The letters in this paragraph should have extra space between them.

[cl5] The letters in this paragraph should have extra space between them.

[cl6] The letters in this paragraph should have extra space between them.

[cl7] The letters in this paragraph should have extra space between them.

[cl8] The letters in this paragraph should have extra space between them, but the last few words in the sentence [cl9] should show normal spacing.

[cl10] The letters in this paragraph should have normal space between them, since percentage values are not allowed on this property.

[cl11] The letters in this paragraph should have reduced space between them, since negative values are allowed on this property.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normal letter spacing for its display, as it has a style attribute set to inherit the letter-spacing value. [/div.inh1]
[div.inh2] This DIV should use a normal letter spacing for its display, as it has a style attribute set to inherit the letter-spacing value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-04b.htm b/css2/sec16-04b.htm new file mode 100755 index 0000000..b03d499 --- /dev/null +++ b/css2/sec16-04b.htm @@ -0,0 +1 @@ + 16.4b word-spacing

CSS2 Test Suite: 16.4 word-spacing

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {word-spacing: 0.3in;}
.cl2 {word-spacing: 0.5cm;}
.cl3 {word-spacing: 5mm;}
.cl4 {word-spacing: 3pt;}
.cl5 {word-spacing: 0.25pc;}
.cl6 {word-spacing: 1em;}
.cl7 {word-spacing: 1ex;}
.cl8 {word-spacing: 5px;}
.cl9 {word-spacing: normal;}
.cl10 {word-spacing: 300%;}
.cl11 {word-spacing: -0.2em;}
div.parent {word-spacing: normal;}
div.inh1 {word-spacing: 2em;}
div.inh2 {word-spacing: -2em;}


[cl1] The words in this paragraph should have extra space between them.

[cl2] The words in this paragraph should have extra space between them.

[cl3] The words in this paragraph should have extra space between them.

[cl4] The words in this paragraph should have extra space between them.

[cl5] The words in this paragraph should have extra space between them.

[cl6] The words in this paragraph should have extra space between them.

[cl7] The words in this paragraph should have extra space between them.

[cl8] The words in this paragraph should have extra space between them, but the last few words in the sentence [cl9] should show normal spacing.

[cl10] The words in this paragraph should have normal space between them, since percentage values are not allowed on this property.

[cl11] The words in this paragraph should have reduced space between them, since negative values are allowed on this property.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use a normal word spacing for its display, as it has a style attribute set to inherit the word-spacing value. [/div.inh1]
[div.inh2] This DIV should use a normal word spacing for its display, as it has a style attribute set to inherit the word-spacing value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-05.htm b/css2/sec16-05.htm new file mode 100755 index 0000000..38a982c --- /dev/null +++ b/css2/sec16-05.htm @@ -0,0 +1 @@ + 16.5 text-transform

CSS2 Test Suite: 16.5 text-transform

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.ttn {text-transform: none;}
.cap {text-transform: capitalize;}
.upp {text-transform: uppercase;}
.low {text-transform: lowercase;}
div.parent {text-transform: none;}
div.inh1 {text-transform: uppercase;}
div.inh2 {text-transform: lowercase;}


[ttn] This page tests the 'text-transform' property of CSS1. This paragraph has no text transformation and should appear normal.

[cap] This paragraph is capitalized and the first letter in each word should therefore appear in uppercase. Words that are in uppercase in the source (e.g. USA) should remain so. There should be a capital letter after a non-breaking space (&nbsp;). Both those characters appear in the previous sentence.

Words with inline elements inside them should only capitalize the first letter of the word. Therefore, the last word in this sentence should have one, and only one, capital [cap] letter.

[upp] This paragraph is uppercased and small characters in the source (e.g. a and å) should therefore appear in uppercase. In the last sentence, however, [ttn] the last eight words should not be uppercase.

[low] This paragraph is lowercased and capital characters in the source (e.g. A and Å) should therefore appear in lowercase.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use no text transformation in for its display, as it has a style attribute set to inherit the text-transform value. [/div.inh1]
[div.inh2] This DIV should use no text transformation in for its display, as it has a style attribute set to inherit the text-transform value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec16-06.htm b/css2/sec16-06.htm new file mode 100755 index 0000000..c67e43f --- /dev/null +++ b/css2/sec16-06.htm @@ -0,0 +1 @@ + 16.6 white-space

CSS2 Test Suite: 16.6 white-space

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {white-space: pre;}
.cl2 {white-space: nowrap;}
.cl3 {white-space: normal;}
div.parent {white-space: normal;}
div.inh1 {white-space: pre;}
div.inh2 {white-space: nowrap;}


[cl1] This paragraph should show extra space where there would ordinarily not be any. There should also be preservation of returns as this sentence very clearly demonstrates.

[cl2] This paragraph should not word-wrap, no matter how long the paragraph might be or over how many lines it would ordinarily wrap, as it has been set to white-space: nowrap and that should have the obvious effect.

[cl1] This paragraph should show extra space, [cl3] except in the second half.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should use normal white space handling for its display, as it has a style attribute set to inherit the white-space value. [/div.inh1]
[div.inh2] This DIV should use normal white space handling for its display, as it has a style attribute set to inherit the white-space value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec17-04-01.htm b/css2/sec17-04-01.htm new file mode 100755 index 0000000..4fccd86 --- /dev/null +++ b/css2/sec17-04-01.htm @@ -0,0 +1 @@ + 17.4.1 caption-side

CSS2 Test Suite: 17.4.1 caption-side

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

table {margin: 20px 150px; background: silver;}
table td {background: #FF9;}
caption {border: 1px dotted purple;}
.cl1 {caption-side: top;}
.cl2 {caption-side: right;}
.cl3 {caption-side: bottom;}
.cl4 {caption-side: left;}


[cl1] Table caption on the top
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
[cl2] Table caption on the right
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
[cl3] Table caption on the bottom
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4
[cl4] Table caption on the left
r1c1r1c2r1c3r1c4
r2c1r2c2r2c3r2c4
r3c1r3c2r3c3r3c4
r4c1r4c2r4c3r4c4

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec17-05-02.htm b/css2/sec17-05-02.htm new file mode 100755 index 0000000..8ff7d45 --- /dev/null +++ b/css2/sec17-05-02.htm @@ -0,0 +1 @@ + 17.5.2 table-layout

CSS2 Test Suite: 17.5.2 table-layout

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

table {background: gray; width: 300px;}
table td {background: #FF9; color: black;}
.r1c2 {width: 100px;}
.r2c1 {width: 150px;}
.r3c3 {width: 100px;}
.cl1 {table-layout: fixed;}
.cl2 {table-layout: auto;}


In the following table, the cells should extend outside of the 'table' element itself, because their aggregate widths are greater than 300px. The table should not expand to contain the cells.

[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

In the following table, the cells should not extend outside of the 'table' element itself, even though their aggregate widths are greater than 300px. The table should instead expand to contain the cells.

[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec17-06-01a.htm b/css2/sec17-06-01a.htm new file mode 100755 index 0000000..eed4daf --- /dev/null +++ b/css2/sec17-06-01a.htm @@ -0,0 +1 @@ + 17.6.1a border-spacing

CSS2 Test Suite: 17.6.1 border-spacing

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

table {background: gray; width: 300px; border-spacing: 6px 3px;}
table td {background: #FF9; color: black;}
.cl1 {border-collapse: separate;}
.cl2 {border-collapse: collapse;}


The cells of the following 'table' element should be separated by six pixels horizontally, and three pixels vertically.

[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

The cells of the following 'table' element should be not be separated.

[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec17-06-01b.htm b/css2/sec17-06-01b.htm new file mode 100755 index 0000000..3d2ee7b --- /dev/null +++ b/css2/sec17-06-01b.htm @@ -0,0 +1 @@ + 17.6.1b empty-cells

CSS2 Test Suite: 17.6.1 empty-cells

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

table {background: gray; width: 300px; border-collapse: separate;}
table td {background: #FF9; color: black; border: 1px solid green;}
.cl1 {empty-cells: show;}
.cl2, .cl3 {empty-cells: hide;}


The empty cell in the middle of the following 'table' element should be rendered, including its background and borders.

[cl1]r1c2r1c3
r2c1r2c3
r3c1r3c2r3c3

The empty cell in the middle of the following 'table' element should not be rendered at all. There should instead be a blank spot in the middle of the 'table'.

[cl2]r1c2r1c3
r2c1r2c3
r3c1r3c2r3c3

The second row in the following 'table' element, which contains only empty cells, should not be rendered at all. The table should be drawn as if the entire row had been set to 'display: none'.

[cl3]r1c2r1c3
r3c1r3c2r3c3

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec17-06.htm b/css2/sec17-06.htm new file mode 100755 index 0000000..c997380 --- /dev/null +++ b/css2/sec17-06.htm @@ -0,0 +1 @@ + 17.6 border-collapse

CSS2 Test Suite: 17.6 border-collapse

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

table {background: gray; width: 300px; padding: 10px; border-spacing: 3px;}
table td {background: #FF9; color: black; border: 2px outset silver;}
.cl1 {border-collapse: separate;}
.cl2 {border-collapse: collapse;}

table.cl3 { border-collapse: collapse; border: 5px solid yellow; }
table.cl3 col#col1 { border: 3px solid black; }
table.cl3 td { border: 1px solid red; padding: 1em; }
table.cl3 td.solid-blue { border: 5px dashed blue; }
table.cl3 td.solid-green { border: 5px solid green; }



The following 'table' element should have 3 pixels of space between its cells (both horizontally and vertically) and 10 pixels of padding around the outer edge of the table. In addition, each cell should have a two-pixel outset border, with each border separate from the others.

[cl1]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

The following 'table' element should not have 3 pixels of space between its cells (both horizontally and vertically), not should it have 10 pixels of padding around the outer edge of the table. The cells should not be separated except by their borders, and the borders should appear to "merge" so that cells share borders.

[cl2]r1c2r1c3
r2c1r2c2r2c3
r3c1r3c2r3c3

The following 'table' element, with a class of 'cl3', is a test of the collapsed-borders model.

1 2 3
4 5 6
7 8 9
10 11 12
13 14 15

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-01.htm b/css2/sec18-01.htm new file mode 100755 index 0000000..2013536 --- /dev/null +++ b/css2/sec18-01.htm @@ -0,0 +1 @@ + 18.1 cursor

CSS2 Test Suite: 18.1 cursor

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

TD {background: white;}
.cl1 {cursor: auto;}
.cl2 {cursor: default;}
.cl3 {cursor: crosshair;}
.cl4 {cursor: pointer;}
.cl5 {cursor: move;}
.cl6 {cursor: n-resize;}
.cl7 {cursor: e-resize;}
.cl8 {cursor: s-resize;}
.cl9 {cursor: w-resize;}
.cl10 {cursor: ne-resize;}
.cl11 {cursor: se-resize;}
.cl12 {cursor: sw-resize;}
.cl13 {cursor: nw-resize;}
.cl14 {cursor: text;}
.cl15 {cursor: wait;}
.cl16 {cursor: help;}
.cl17 {cursor: url(Globe.ani);}
div.parent {cursor: auto;}
div.inh1 {cursor: crosshair;}
div.inh2 {cursor: help;}


[cl1] auto [cl2] default [cl3] crosshair [cl4] pointer [cl5] move
[cl6] n-resize [cl7] e-resize [cl8] s-resize [cl9] w-resize
[cl10] ne-resize [cl11] se-resize [cl12] sw-resize [cl13] nw-resize
[cl14] text [cl15] wait [cl16] help [cl17] url(...)

[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have the usual cursor when the mouse pointer hovers over it, as it has a style attribute set to inherit the cursor value. [/div.inh1]
[div.inh2] This DIV should have the usual cursor when the mouse pointer hovers over it, as it has a style attribute set to inherit the cursor value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-02.htm b/css2/sec18-02.htm new file mode 100755 index 0000000..265bad1 --- /dev/null +++ b/css2/sec18-02.htm @@ -0,0 +1 @@ + 18.2 User preferences for colors

CSS2 Test Suite: 18.2 User preferences for colors

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

.cl1 {color: ActiveBorder;}
.cl2 {color: ActiveCaption;}
.cl3 {color: AppWorkspace;}
.cl4 {color: Background;}
.cl5 {color: ButtonFace;}
.cl6 {color: ButtonHighlight;}
.cl7 {color: ButtonShadow;}
.cl8 {color: ButtonText;}
.cl9 {color: CaptionText;}
.cl10 {color: GrayText;}
.cl11 {color: Highlight;}
.cl12 {color: HighlightText;}
.cl13 {color: InactiveBorder;}
.cl14 {color: InactiveCaption;}
.cl15 {color: InactiveCaptionText;}
.cl16 {color: InfoBackground;}
.cl17 {color: InfoText;}
.cl18 {color: Menu;}
.cl19 {color: MenuText;}
.cl20 {color: Scrollbar;}
.cl21 {color: ThreeDDarkShadow;}
.cl22 {color: ThreeDFace;}
.cl23 {color: ThreeDHighlight;}
.cl24 {color: ThreeDLightShadow;}
.cl25 {color: ThreeDShadow;}
.cl26 {color: Window;}
.cl27 {color: WindowFrame;}
.cl28 {color: WindowText;}


The list items in the following list are all set to various colors. These should match elements of the user agent's operating system or other computing environment.


[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-03.htm b/css2/sec18-03.htm new file mode 100644 index 0000000..c91185f --- /dev/null +++ b/css2/sec18-03.htm @@ -0,0 +1,51 @@ + + + + +18.3 User prferences for fonts + + + + + + +

CSS2 Test Suite: 18.3 User prferences for fonts

+[index page] [section] [Previous] [Next] [Specification] +
+

The style declarations contained within this page:

+
.cl1 {font: caption;}
+.cl2 {font: icon;}
+.cl3 {font: menu;}
+.cl4 {font: message-box;}
+.cl5 {font: small-caption;}
+.cl6 {font: status-bar;}
+
+
+

+[cl1] The text in this element should match the font used by the operating system or other computing environment for captioned controls (e.g., buttons, drop-downs, etc.). +

+

+[cl2] The text in this element should match the font used by the operating system or other computing environment to label icons. +

+

+[cl3] The text in this element should match the font used by the operating system or other computing environment in menus (e.g., dropdown menus and menu lists). +

+

+[cl4] The text in this element should match the font used by the operating system or other computing environment in dialog boxes. +

+

+[cl5] The text in this element should match the font used by the operating system or other computing environment for labeling small controls. +

+

+[cl6] The text in this element should match the font used by the operating system or other computing environment in window status bars. +

+
[index page] [section] [Previous] [Next] [Specification] +
+ + diff --git a/css2/sec18-04a.htm b/css2/sec18-04a.htm new file mode 100755 index 0000000..0bd6fe3 --- /dev/null +++ b/css2/sec18-04a.htm @@ -0,0 +1 @@ + 18.4a outline

CSS2 Test Suite: 18.4 outline

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

INPUT {border: 3px solid gray;}
.cl1 {outline: 2px dotted green;}
.cl2 {outline: 1em double green;}
.cl3 {outline: thick solid invert;}
div.parent {outline: none;}
div.inh1 {outline: 10px solid red;}
div.inh2 {outline: 1em inset red;}

Here's an input whose outline (when in focus) should be 2 pixels wide, dotted, and green. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be 1em wide, double, and green. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be as wide as "thick", solid, and invert the background. The outline should be drawn to the outside of the element border.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have no outline under any circumstances, as it has a style attribute set to inherit the outline value. [/div.inh1]
[div.inh2] This DIV should have no outline under any circumstances, as it has a style attribute set to inherit the outline value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-04b.htm b/css2/sec18-04b.htm new file mode 100755 index 0000000..d147e20 --- /dev/null +++ b/css2/sec18-04b.htm @@ -0,0 +1 @@ + 18.4b outline-width

CSS2 Test Suite: 18.4 outline-width

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

INPUT {border: 3px solid gray; outline-style: solid;}
.cl1 {outline-width: 2px;}
.cl2 {outline-width: 1em;}
.cl3 {outline-width: thick;}
div.parent {outline-width: 1px;}
div.inh1 {outline-width: 10px;}
div.inh2 {outline-width: 1em;}

Note that the following tests are valid only if the property outline-style is supported.

Here's an input whose outline (when in focus) should be 2 pixels wide, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be 1em wide, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be thick, solid, and the same color as the element's foreground (black). The outline should be drawn to the outside of the element border.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have an outline width of 1px when it is in focus, as it has a style attribute set to inherit the outline-width value. [/div.inh1]
[div.inh2] This DIV should have an outline width of 1px when it is in focus, as it has a style attribute set to inherit the outline-width value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-04c.htm b/css2/sec18-04c.htm new file mode 100755 index 0000000..02ab95b --- /dev/null +++ b/css2/sec18-04c.htm @@ -0,0 +1 @@ + 18.4c outline-style

CSS2 Test Suite: 18.4 outline-style

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

INPUT {border: 3px solid gray;}
.cl1 {outline-style: solid;}
.cl2 {outline-style: double;}
.cl3 {outline-style: dotted;}
.cl4 {outline-style: dashed;}
.cl5 {outline-style: inset;}
.cl6 {outline-style: outset;}
.cl7 {outline-style: groove;}
.cl8 {outline-style: ridge;}
div.parent {outline-style: solid;}
div.inh1 {outline-style: inset;}
div.inh2 {outline-style: outset;}

Here's an input whose outline (when in focus) should be solid and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be double and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be dotted and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be dashed and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be inset and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be outset and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be grooved and of medium width. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be ridged and of medium width. The outline should be drawn to the outside of the element border.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have a solid outline when it is in focus, as it has a style attribute set to inherit the outline-style value. [/div.inh1]
[div.inh2] This DIV should have a solid outline when it is in focus, as it has a style attribute set to inherit the outline-style value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/sec18-04d.htm b/css2/sec18-04d.htm new file mode 100755 index 0000000..4ac6e27 --- /dev/null +++ b/css2/sec18-04d.htm @@ -0,0 +1 @@ + 18.4d outline-color

CSS2 Test Suite: 18.4 outline-color

[index page] [section] [Previous] [Next] [Specification]

The style declarations contained within this page:

INPUT {border: 3px solid gray; outline-style: solid;}
.cl1 {outline-color: green;}
.cl2 {outline-color: invert;}
div.parent {outline-color: green;}
div.inh1 {outline-color: maroon;}
div.inh2 {outline-color: red;}

Note that the following tests are valid only if the property outline-style is supported.

Here's an input whose outline (when in focus) should be of medium width, solid, and green. The outline should be drawn to the outside of the element border.

Here's an input whose outline (when in focus) should be of medium width, solid, and invert the background. The outline should be drawn to the outside of the element border.


[div.parent] This DIV has been set with parental styles. The inline elements within this DIV are enclosed in square brackets in order to more easily discern their placement.
[div.inh1] This DIV should have a green outline when it is in focus, as it has a style attribute set to inherit the outline-color value. [/div.inh1]
[div.inh2] This DIV should have a green outline when it is in focus, as it has a style attribute set to inherit the outline-color value. [/div.inh2]
This is the end of the parent DIV. [/div.parent]

[index page] [section] [Previous] [Next] [Specification]
\ No newline at end of file diff --git a/css2/slice b/css2/slice new file mode 100755 index 0000000..aa26449 --- /dev/null +++ b/css2/slice @@ -0,0 +1,2 @@ +rm *.htm +./slicer.pl < pre-torchar.txt diff --git a/css2/slicer.pl b/css2/slicer.pl new file mode 100755 index 0000000..e7e61f2 --- /dev/null +++ b/css2/slicer.pl @@ -0,0 +1,15 @@ +#! /usr/bin/perl + +@file = <>; +while (@file) { + $line = shift @file; + $line =~ s/\t//g; + $line =~ s/\cK/\n/g; + if ($line =~ s/^##### (\S+) #####//) { + open OUTFILE, ">$1"; + print OUTFILE $line; + close OUTFILE; + } else { + print STDERR "Unknown line in file: $line\n"; + } +} diff --git a/css2/styleimport.css b/css2/styleimport.css new file mode 100644 index 0000000..21f48a5 --- /dev/null +++ b/css2/styleimport.css @@ -0,0 +1 @@ +/*Import Test File*/ .styleimport { font-weight: bold; color: green; background: silver none; } .folderstyleimport { color: red; background: yellow none; } \ No newline at end of file diff --git a/css2/updex.html b/css2/updex.html new file mode 100644 index 0000000..d98c88c --- /dev/null +++ b/css2/updex.html @@ -0,0 +1 @@ + 5.2  -  Selector Syntax8 July 2002 / 11:58:50 EST 5.2.1  -  Grouping8 July 2002 / 11:58:49 EST 5.3  -  Universal Selector8 July 2002 / 11:58:49 EST 5.4  -  Type Selectors8 July 2002 / 11:58:49 EST 5.5  -  Descendant Selectors8 July 2002 / 11:58:49 EST 5.6  -  Child Selectors8 July 2002 / 11:58:49 EST 5.7  -  Adjacent Sibling Selectors8 July 2002 / 11:58:49 EST 5.8.1  -  Attribute Selectors8 July 2002 / 11:58:49 EST 5.8.3  -  Class Selectors8 July 2002 / 11:58:49 EST 5.9  -  ID Selectors8 July 2002 / 11:58:49 EST 5.10  -  Pseudo-Class Combinations8 July 2002 / 11:58:49 EST 5.11.1  -  :first-child8 July 2002 / 11:58:49 EST 5.11.2  -  :link and :visited8 July 2002 / 11:58:49 EST 5.11.3  -  :active, :hover, and :focus8 July 2002 / 11:58:49 EST 5.11.4  -  :lang8 July 2002 / 11:58:49 EST 5.12.1  -  :first-line8 July 2002 / 11:58:49 EST 5.12.2  -  :first-letter8 July 2002 / 11:58:49 EST 5.12.3  -  :before and :after8 July 2002 / 11:58:49 EST 6.2.1  -  inherit8 July 2002 / 11:58:49 EST 6.3  -  @import8 July 2002 / 11:58:49 EST 6.4.1  -  Cascading Order8 July 2002 / 11:58:49 EST 6.4.2  -  !important rules8 July 2002 / 11:58:49 EST 6.4.3  -  Calculating specificity8 July 2002 / 11:58:49 EST 6.4.4  -  Precedence of non-CSS hints8 July 2002 / 11:58:49 EST 8.2  -  Margins, padding, borders8 July 2002 / 11:58:49 EST 8.3  -  margin 8 July 2002 / 11:58:49 EST 8.3  -  margin-top8 July 2002 / 11:58:49 EST 8.3  -  margin-right8 July 2002 / 11:58:49 EST 8.3  -  margin-bottom8 July 2002 / 11:58:49 EST 8.3  -  margin-left 8 July 2002 / 11:58:49 EST 8.4  -  padding 8 July 2002 / 11:58:49 EST 8.4  -  padding-bottom8 July 2002 / 11:58:49 EST 8.4  -  padding-right8 July 2002 / 11:58:49 EST 8.4  -  padding-left 8 July 2002 / 11:58:49 EST 8.4  -  padding-top8 July 2002 / 11:58:49 EST 8.5.1  -  border-top-width8 July 2002 / 11:58:49 EST 8.5.1  -  border-width 8 July 2002 / 11:58:49 EST 8.5.1  -  border-right-width8 July 2002 / 11:58:49 EST 8.5.1  -  border-bottom-width8 July 2002 / 11:58:49 EST 8.5.1  -  border-left-width 8 July 2002 / 11:58:49 EST 8.5.2  -  border-color 8 July 2002 / 11:58:48 EST 8.5.2  -  border-top-color8 July 2002 / 11:58:49 EST 8.5.2  -  border-right-color8 July 2002 / 11:58:49 EST 8.5.2  -  border-bottom-color8 July 2002 / 11:58:48 EST 8.5.2  -  border-left-color 8 July 2002 / 11:58:48 EST 8.5.3  -  border-style 8 July 2002 / 11:58:48 EST 8.5.3  -  border-top-style8 July 2002 / 11:58:48 EST 8.5.3  -  border-right-style8 July 2002 / 11:58:48 EST 8.5.3  -  border-bottom-style8 July 2002 / 11:58:48 EST 8.5.3  -  border-left-style 8 July 2002 / 11:58:48 EST 8.5.4  -  border 8 July 2002 / 11:58:48 EST 8.5.4  -  border-top 8 July 2002 / 11:58:48 EST 8.5.4  -  border-right8 July 2002 / 11:58:48 EST 8.5.4  -  border-bottom 8 July 2002 / 11:58:48 EST 8.5.4  -  border-left 8 July 2002 / 11:58:48 EST 9.2.5  -  display8 July 2002 / 11:58:48 EST 9.3.1  -  position8 July 2002 / 11:58:48 EST 9.3.2  -  Box Offsets8 July 2002 / 11:58:48 EST 9.3.2  -  bottom 8 July 2002 / 12:01:22 EST 9.3.2  -  left 8 July 2002 / 12:01:47 EST 9.3.2  -  right 8 July 2002 / 12:01:47 EST 9.3.2  -  top 8 July 2002 / 12:01:47 EST 9.5.1  -  float8 July 2002 / 11:58:48 EST 9.5.2  -  clear8 July 2002 / 11:58:48 EST 9.8.2  -  Relative Positioning8 July 2002 / 11:58:48 EST 9.8.3  -  Floating a Box8 July 2002 / 11:58:48 EST 9.8.4  -  Absolute Positioning8 July 2002 / 11:58:48 EST 9.9.1  -  z-index8 July 2002 / 11:58:48 EST 9.10  -  direction8 July 2002 / 11:58:48 EST 9.10  -  unicode-bidi 8 July 2002 / 12:01:47 EST 10.2  -  width 8 July 2002 / 11:58:48 EST 10.3.1  -  Computing widths and margins: inline, non-replaced elements8 July 2002 / 11:58:48 EST 10.3.2  -  Computing widths and margins: inline, replaced elements8 July 2002 / 11:58:48 EST 10.3.3  -  Computing widths and margins: block-level, non-replaced elements in normal flow8 July 2002 / 11:58:48 EST 10.3.4  -  Computing widths and margins: block-level, replaced elements in normal flow8 July 2002 / 11:58:48 EST 10.3.5  -  Computing widths and margins: floating, non-replaced elements8 July 2002 / 11:58:48 EST 10.3.6  -  Computing widths and margins: floating, replaced elements8 July 2002 / 11:58:48 EST 10.3.7  -  Computing widths and margins: absolutely positioned, non-replaced elements8 July 2002 / 11:58:48 EST 10.3.8  -  Computing widths and margins: absolutely positioned, replaced elements8 July 2002 / 11:58:48 EST 10.4  -  max-width 8 July 2002 / 11:58:48 EST 10.4  -  min-width 8 July 2002 / 11:58:48 EST 10.5  -  height 8 July 2002 / 11:58:48 EST 10.6.1  -  Computing heights and margins: inline, non-replaced elements8 July 2002 / 11:58:48 EST 10.6.2  -  Computing heights and margins: inline, replaced elements; block-level, replaced elements in normal flow; and floating, replaced elements8 July 2002 / 11:58:48 EST 10.6.3  -  Computing heights and margins: block-level, non-replaced elements in normal flow; and floating, non-replaced elements8 July 2002 / 11:58:48 EST 10.6.4  -  Computing heights and margins: absolutely positioned, non-replaced elements8 July 2002 / 11:58:48 EST 10.6.5  -  Computing heights and margins: absolutely positioned, replaced elements8 July 2002 / 11:58:48 EST 10.7  -  max-height 8 July 2002 / 11:58:48 EST 10.7  -  min-height 8 July 2002 / 11:58:48 EST 10.8  -  line-height 8 July 2002 / 12:01:47 EST 10.8  -  vertical-align 8 July 2002 / 12:01:47 EST 11.1.1  -  overflow 8 July 2002 / 11:58:48 EST 11.1.2  -  clip 8 July 2002 / 12:01:47 EST 11.2  -  visibility 8 July 2002 / 11:58:48 EST 12.1  -  :before and :after8 July 2002 / 11:58:48 EST 12.2  -  content8 July 2002 / 11:58:48 EST 12.4.1  -  quotes 8 July 2002 / 11:58:48 EST 12.5  -  counter-increment 8 July 2002 / 11:58:48 EST 12.5  -  counter-reset 8 July 2002 / 11:58:48 EST 12.6.1  -  marker-offset 8 July 2002 / 11:58:48 EST 12.6.2  -  list-style 8 July 2002 / 11:58:48 EST 12.6.2  -  list-style-image 8 July 2002 / 11:58:48 EST 12.6.2  -  list-style-position 8 July 2002 / 11:58:48 EST 12.6.2  -  list-style-type 8 July 2002 / 11:58:48 EST 14.1  -  color 8 July 2002 / 11:58:48 EST 14.2.1  -  background 8 July 2002 / 11:58:48 EST 14.2.1  -  background-attachment8 July 2002 / 11:58:48 EST 14.2.1  -  background-color 8 July 2002 / 11:58:48 EST 14.2.1  -  background-image 8 July 2002 / 11:58:48 EST 14.2.1  -  background-position 8 July 2002 / 11:58:48 EST 14.2.1  -  background-repeat 8 July 2002 / 11:58:48 EST 15.2.2  -  font-family8 July 2002 / 11:58:48 EST 15.2.3  -  font-stretch8 July 2002 / 11:58:48 EST 15.2.3  -  font-style8 July 2002 / 11:58:48 EST 15.2.3  -  font-variant8 July 2002 / 11:58:48 EST 15.2.3  -  font-weight8 July 2002 / 11:58:48 EST 15.2.4  -  font-size8 July 2002 / 11:58:48 EST 15.2.4  -  font-size-adjust8 July 2002 / 11:58:48 EST 15.2.5  -  font8 July 2002 / 11:58:48 EST 16.1  -  text-indent8 July 2002 / 11:58:48 EST 16.2  -  text-align8 July 2002 / 11:58:48 EST 16.3.1  -  text-decoration8 July 2002 / 11:58:48 EST 16.3.2  -  text-shadow8 July 2002 / 11:58:48 EST 16.4  -  letter-spacing8 July 2002 / 11:58:48 EST 16.4  -  word-spacing8 July 2002 / 11:58:48 EST 16.5  -  text-transform8 July 2002 / 11:58:48 EST 16.6  -  white-space8 July 2002 / 11:58:48 EST 17.4.1  -  caption-side 8 July 2002 / 11:58:48 EST 17.5.2  -  table-layout 8 July 2002 / 11:58:48 EST 17.6  -  border-collapse 8 July 2002 / 11:58:48 EST 17.6.1  -  border-spacing 8 July 2002 / 11:58:48 EST 17.6.1  -  empty-cells 8 July 2002 / 11:58:48 EST 18.1  -  cursor8 July 2002 / 11:58:48 EST 18.2  -  User preferences for colors8 July 2002 / 11:58:48 EST 18.4  -  outline8 July 2002 / 11:58:48 EST 18.4  -  outline-width8 July 2002 / 11:58:48 EST 18.4  -  outline-style8 July 2002 / 11:58:48 EST 18.4  -  outline-color8 July 2002 / 11:58:48 EST \ No newline at end of file diff --git a/css3-mediaq/aspect-ratio.html b/css3-mediaq/aspect-ratio.html new file mode 100644 index 0000000..042d14d --- /dev/null +++ b/css3-mediaq/aspect-ratio.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-mediaq/colordepth.html b/css3-mediaq/colordepth.html new file mode 100644 index 0000000..542ce26 --- /dev/null +++ b/css3-mediaq/colordepth.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-mediaq/device-aspect-ratio.html b/css3-mediaq/device-aspect-ratio.html new file mode 100644 index 0000000..b12e304 --- /dev/null +++ b/css3-mediaq/device-aspect-ratio.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-mediaq/device-size-2.html b/css3-mediaq/device-size-2.html new file mode 100644 index 0000000..796557d --- /dev/null +++ b/css3-mediaq/device-size-2.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-mediaq/device-size.html b/css3-mediaq/device-size.html new file mode 100644 index 0000000..a6de132 --- /dev/null +++ b/css3-mediaq/device-size.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-mediaq/viewport-size.html b/css3-mediaq/viewport-size.html new file mode 100644 index 0000000..2d82a62 --- /dev/null +++ b/css3-mediaq/viewport-size.html @@ -0,0 +1 @@ + CSS Media Query test

Howdy.

Specification \ No newline at end of file diff --git a/css3-tests/ bare.html b/css3-tests/ bare.html new file mode 100644 index 0000000..0b19010 --- /dev/null +++ b/css3-tests/ bare.html @@ -0,0 +1,19 @@ + + + +CSS3 test: + + + + + +

+ +
+ +
+ + + diff --git a/css3-tests/align-items.html b/css3-tests/align-items.html new file mode 100644 index 0000000..5eed973 --- /dev/null +++ b/css3-tests/align-items.html @@ -0,0 +1,66 @@ + + + +CSS3 test: align-items + + + + + +

http://www.w3.org/TR/css3-flexbox/#align-items

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3-tests/align-self.html b/css3-tests/align-self.html new file mode 100644 index 0000000..fe678c2 --- /dev/null +++ b/css3-tests/align-self.html @@ -0,0 +1,68 @@ + + + +CSS3 test: align-self + + + + + + +

http://www.w3.org/TR/css3-flexbox/#align-self

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3-tests/alignment-adjust.html b/css3-tests/alignment-adjust.html new file mode 100644 index 0000000..0511042 --- /dev/null +++ b/css3-tests/alignment-adjust.html @@ -0,0 +1,47 @@ + + + +CSS3 test: alignment-adjust + + + + + +

http://www.w3.org/TR/css3-linebox/#alignment-adjust

+ +

+Plain text. +. +. +. +. +. +. +. +. +. +. +. +. +. +. +

+ + + diff --git a/css3-tests/alignment-baseline.html b/css3-tests/alignment-baseline.html new file mode 100644 index 0000000..684cea4 --- /dev/null +++ b/css3-tests/alignment-baseline.html @@ -0,0 +1,43 @@ + + + +CSS3 test: alignment-baseline + + + + + +

http://www.w3.org/TR/css3-linebox/#alignment-baseline

+ +

+Plain text. +. +. +. +. +. +. +. +. +. +. +. +. +

+ + + diff --git a/css3-tests/appearance.html b/css3-tests/appearance.html new file mode 100644 index 0000000..2b406a3 --- /dev/null +++ b/css3-tests/appearance.html @@ -0,0 +1,69 @@ + + + +CSS3 test: appearance + + + + + +

http://www.w3.org/TR/css3-ui/#appearance0

+ +

span #s01

+

span #s02

+

span #s03

+

span #s04

+

span #s05

+

span #s06

+

span #s07

+

span #s08

+

span #s09

+

span #s10

+

span #s11

+

span #s12

+

span #s13

+

span #s14

+

span #s15

+

span #s16

+

span #s17

+

span #s18

+

span #s19

+

span #s20

+

span #s21

+

span #s22

+

span #s23

+

span #s24

+

span #s25

+

span #s26

+

span #s27

+ + + diff --git a/css3-tests/background-attachment.html b/css3-tests/background-attachment.html new file mode 100644 index 0000000..81492eb --- /dev/null +++ b/css3-tests/background-attachment.html @@ -0,0 +1,52 @@ + + + +CSS3 test: background-attachment + + + + + +

http://www.w3.org/TR/css3-background/#the-background-attachment

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ +

Filler text follows:

+ +

+ + +Newburgh heights anne heche cleveland claritatem dolore et et sam sheppard andre norton eros adipiscing ruby dee possim typi vel investigationes. Linndale insitam clari odio lius legunt, lakeview cemetary iis facilisi enim warrensville heights, praesent vel facilisis mark mothersbaugh nulla litterarum cleveland heights. Gund arena broadview heights paul newman lobortis bernie kosar fairview park joe shuster consectetuer tempor nobis luptatum option uss cod quinta nonummy mazim. Superhost nibh lorem liber zzril mutationem non joel grey dignissim placerat fiant vero halle berry parum. Dignissim velit kenny lofton blandit, decima philip johnson in futurum dolor lebron departum arena depressum metro quatro annum returnum celebra gigantus. Nihil me qui at ullamcorper usus erat claram jim tressel humanitatis euismod est magna bratenahl vel duis. Jesse owens suscipit notare fiant ad nobis nam olmsted falls. Claritas euclid augue feugiat jim backus littera lobortis, commodo quam brecksville william g. mather iriure esse dolor. Squire’s castle harvey pekar bobby knight solon ut eorum east cleveland ghoulardi saepius wisi. +

+

+Cuyahoga river sammy kaye quod tation cuyahoga valley delenit. Iusto dolore amet ut sollemnes quarta dolore margaret hamilton luptatum tation jacobs field rocky river. Eric carmen formas duis autem quinta, nunc iusto humanitatis claritas the metroparks laoreet assum. Langston hughes molestie don king cuyahoga heights option playhouse square amet bay village. Commodo soluta nobis eros diam in augue, mazim amet parma heights claritatem in clari don shula lorem steve harvey. Investigationes quam qui id brooklyn heights burgess meredith gothica feugait saepius, parum brad daugherty elit suscipit eu. Pierogies oakwood drew carey ipsum tempor brooklyn hendrerit putamus at adipiscing euclid beach processus. Congue screamin’ jay hawkins ad demonstraverunt zzril, modo accumsan the innerbelt berea litterarum bob golic highland heights. Eum paul brown imperdiet olmsted township eleifend seven hills patricia heaton, sit bob hope chagrin falls township mutationem polka hall of fame et consuetudium dynamicus lake erie. Facilisis dolor strongsville shaker heights liber notare eum parma decima dolore lorem qui. Nibh geauga lake aliquip veniam qui qui per habent, michael symon, tincidunt parum jim brown laoreet tincidunt vulputate diam. Ipsum valley view michael ruhlman veniam congue cum quam cavaliers me dolore. +

+

+Sequitur nostrud doug dieken minim qui placerat, quis claritatem. Lectores ut est exerci lebron james chrissie hynde consequat iriure erat cedar point toni morrison putamus. Molly shannon quarta possim richmond heights facit te. Dynamicus legere tracy chapman consequat in rock & roll hall of fame university heights decima id ii. Bowling assum ea independence james a. garfield soluta seacula north olmsted est eorum littera the gold coast consequat exerci claritatem elit aliquip nulla. Anteposuerit phil donahue consequat moreland hills great lakes science center feugait carl b. stokes facer. Modo ut the arcade dolor woodmere in arsenio hall etiam iis facilisi legentis facer videntur decima henry mancini non aliquam wisi. Videntur ut quis walton hills mike golic nulla tremont eu tim conway bedford quod, imperdiet delenit praesent. Nobis in beachwood frank yankovic demonstraverunt amet qui typi nisl, gates mills nisl quod lew wasserman brook park. Legunt dead man’s curve bentleyville sed dolor claram. Maple heights volutpat esse legere nihil facit odio harlan ellison quod lectores hunting valley in doming per. North royalton lorem seacula autem garfield heights sit metroparks zoo te north randall michael stanley indians glenwillow eleifend magna sandy alomar consectetuer. +

+

+Futurum lectorum typi eric metcalf major everett insitam, est ipsum formas illum duis est mirum nunc east side sed. Illum pepper pike nostrud wes craven mentor headlands sit ozzie newsome quam, cum, nulla, george steinbrenner parum john d. rockefeller nunc. Dennis kucinich the flats ut browns feugiat doming. Vulputate gothica vel nunc legentis, typi vero processus. Roger zelazny usus south euclid aliquam lakewood qui eodem cleveland museum of art. Mark price consuetudium dolore et mayfield heights sit habent clay mathews west side peter b. lewis, accumsan nonummy dorothy dandridge ex. +

+

+Ullamcorper mirum severance hall urban meyer in, hal holbrook dolor nam bob feller velit middleburg heights sollemnes. Duis highland hills hendrerit fred willard debra winger euismod westlake emerald necklace. Omar vizquel john w. heisman enim ea eodem bedford heights ohio city ipsum sequitur molestie, minim lectorum ii lius volutpat et collision bend anteposuerit. Etiam ex orange children’s museum chagrin falls mayfield village. Municipal stadium university circle est jerry siegel jim lovell george voinovich lyndhurst, et blandit ↺ id. Putamus littera jacobs field sequitur ipsum eros jim backus, facilisi lyndhurst tincidunt. In orange magna squire’s castle minim iis warrensville heights highland heights eum sandy alomar formas broadview heights oakwood wisi lectores harlan ellison tracy chapman dynamicus. Vulputate hendrerit south euclid laoreet laoreet lectores consuetudium quod feugiat typi luptatum suscipit gund arena dolor geauga lake at. Etiam doming sed futurum margaret hamilton exerci est vero maple heights carl b. stokes william g. mather emerald necklace quarta kenny lofton ghoulardi mirum saepius pierogies. Iriure jesse owens dolore odio cuyahoga valley exerci, te dolor. Seven hills dolor enim claritas option amet me qui paul newman possim. Eric metcalf lorem pepper pike futurum doming clay mathews, consequat nunc est habent ad ex. +

+ + + diff --git a/css3-tests/background-clip.html b/css3-tests/background-clip.html new file mode 100644 index 0000000..dfe3050 --- /dev/null +++ b/css3-tests/background-clip.html @@ -0,0 +1,30 @@ + + + +CSS3 test: background-clip + + + + + +

http://www.w3.org/TR/css3-background/#the-background-clip

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ + + diff --git a/css3-tests/background-image-2.html b/css3-tests/background-image-2.html new file mode 100644 index 0000000..8feb504 --- /dev/null +++ b/css3-tests/background-image-2.html @@ -0,0 +1,33 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex00]
+
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3-tests/background-image-3.html b/css3-tests/background-image-3.html new file mode 100644 index 0000000..ef9b36f --- /dev/null +++ b/css3-tests/background-image-3.html @@ -0,0 +1,31 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3-tests/background-image-4.html b/css3-tests/background-image-4.html new file mode 100644 index 0000000..ac538d5 --- /dev/null +++ b/css3-tests/background-image-4.html @@ -0,0 +1,31 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3-tests/background-image.html b/css3-tests/background-image.html new file mode 100644 index 0000000..914534b --- /dev/null +++ b/css3-tests/background-image.html @@ -0,0 +1,29 @@ + + + +CSS3 test: background-image + + + + + +

http://www.w3.org/TR/css3-background/#the-background-image

+ +
+ +
[#d00]
+ +
[#d01]
+ +
+ + + diff --git a/css3-tests/background-origin.html b/css3-tests/background-origin.html new file mode 100644 index 0000000..15d1677 --- /dev/null +++ b/css3-tests/background-origin.html @@ -0,0 +1,30 @@ + + + +CSS3 test: background-origin + + + + + +

http://www.w3.org/TR/css3-background/#the-background-origin

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ + + diff --git a/css3-tests/background-position.html b/css3-tests/background-position.html new file mode 100644 index 0000000..217e07b --- /dev/null +++ b/css3-tests/background-position.html @@ -0,0 +1,91 @@ + + + +CSS3 test: background-position + + + + + +

http://www.w3.org/TR/css3-background/#the-background-position

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d11]
+
[#d12]
+
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+
[#d17]
+
[#d18]
+ +
[#d21]
+
[#d22]
+
[#d23]
+
[#d24]
+
[#d25]
+
[#d26]
+
[#d27]
+
[#d28]
+ +
[#d31]
+
[#d32]
+
[#d33]
+
[#d34]
+
[#d35]
+
[#d36]
+
[#d37]
+
[#d38]
+ +
+ + + diff --git a/css3-tests/background-repeat-2.html b/css3-tests/background-repeat-2.html new file mode 100644 index 0000000..58b1879 --- /dev/null +++ b/css3-tests/background-repeat-2.html @@ -0,0 +1,58 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
+ + + diff --git a/css3-tests/background-repeat-3.html b/css3-tests/background-repeat-3.html new file mode 100644 index 0000000..5c15f45 --- /dev/null +++ b/css3-tests/background-repeat-3.html @@ -0,0 +1,57 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[.s01 .tl]
+
[.s01]
+
[.s02 .tl]
+
[.s02]
+
[.s03 .tl]
+
[.s03]
+
[.s04 .tl]
+
[.s04]
+
[.s05 .tl]
+
[.s05]
+
[.s06 .tl]
+
[.s06]
+
[.s07 .tl]
+
[.s07]
+
[.s08 .tl]
+
[.s08]
+
[.s09 .tl]
+
[.s09]
+ +
+ + + diff --git a/css3-tests/background-repeat.html b/css3-tests/background-repeat.html new file mode 100644 index 0000000..a3da984 --- /dev/null +++ b/css3-tests/background-repeat.html @@ -0,0 +1,78 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
[#d17]
+
[#d18]
+
[#d19]
+
[#d20]
+ +
[#d21]
+
[#d22]
+
[#d23]
+
[#d24]
+ +
+ + + diff --git a/css3-tests/background-size.html b/css3-tests/background-size.html new file mode 100644 index 0000000..095af30 --- /dev/null +++ b/css3-tests/background-size.html @@ -0,0 +1,59 @@ + + + +CSS3 test: background-size + + + + + +

http://www.w3.org/TR/css3-background/#the-background-size

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
+ + + diff --git a/css3-tests/baseline-shift.html b/css3-tests/baseline-shift.html new file mode 100644 index 0000000..36b535c --- /dev/null +++ b/css3-tests/baseline-shift.html @@ -0,0 +1,29 @@ + + + +CSS3 test: baseline-shift + + + + + +

http://www.w3.org/TR/css3-linebox/#baseline-shift-prop

+ +

+Plain text. +. +. +. +. +. +

+ + + diff --git a/css3-tests/bookmark-label.html b/css3-tests/bookmark-label.html new file mode 100644 index 0000000..4dd7d0b --- /dev/null +++ b/css3-tests/bookmark-label.html @@ -0,0 +1,30 @@ + + + +CSS3 test: bookmark-label + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-label

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3-tests/bookmark-level.html b/css3-tests/bookmark-level.html new file mode 100644 index 0000000..70223af --- /dev/null +++ b/css3-tests/bookmark-level.html @@ -0,0 +1,31 @@ + + + +CSS3 test: bookmark-level + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-level

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3-tests/bookmark-state.html b/css3-tests/bookmark-state.html new file mode 100644 index 0000000..87f26af --- /dev/null +++ b/css3-tests/bookmark-state.html @@ -0,0 +1,29 @@ + + + +CSS3 test: bookmark-state + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-state

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3-tests/bookmark-target.html b/css3-tests/bookmark-target.html new file mode 100644 index 0000000..0d53827 --- /dev/null +++ b/css3-tests/bookmark-target.html @@ -0,0 +1,30 @@ + + + +CSS3 test: bookmark-target + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-target

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3-tests/border-image.html b/css3-tests/border-image.html new file mode 100644 index 0000000..d18a93f --- /dev/null +++ b/css3-tests/border-image.html @@ -0,0 +1,36 @@ + + + +CSS3 test: border-image + + + + + +

http://www.w3.org/TR/css3-background/#the-border-image

+ +
+ +

+[#p01] This is a paragraph that should have an image border using the following image: . +

+

+[#p02] This is a paragraph that should have an image border using the following image: . +

+

+[#p03] This is a paragraph that should have an image border using the following image: . +

+

+[#p04] This is a paragraph that should have an image border using the following image: . +

+ +
+ + + diff --git a/css3-tests/border-radius.html b/css3-tests/border-radius.html new file mode 100644 index 0000000..a7cf43e --- /dev/null +++ b/css3-tests/border-radius.html @@ -0,0 +1,23 @@ + + + +CSS3 test: border-radius + + + + + +

http://www.w3.org/TR/css3-background/#the-border-radius

+ +
+ +

[p01] A paragraph.

+

[p02] Another paragraph.

+ +
+ + + diff --git a/css3-tests/box-decoration-break.html b/css3-tests/box-decoration-break.html new file mode 100644 index 0000000..4e2a8a4 --- /dev/null +++ b/css3-tests/box-decoration-break.html @@ -0,0 +1,25 @@ + + + +CSS3 test: box-decoration-break + + + + + +

http://www.w3.org/TR/css3-background/#the-box-decoration-break

+ +

+[#p01] This is a paragraph. It contains within it a span element. This inline element has been decorated and backgrounded in order to test the outcome of box-decoration-break. There should be two different effects between the first test and the second. Let us hope it is so. +

+

+[#p02] This is a paragraph. It contains within it a span element. This inline element has been decorated and backgrounded in order to test the outcome of box-decoration-break. There should be two different effects between the first test and the second. Let us hope it is so. +

+ + + diff --git a/css3-tests/box-shadow.html b/css3-tests/box-shadow.html new file mode 100644 index 0000000..cc85070 --- /dev/null +++ b/css3-tests/box-shadow.html @@ -0,0 +1,52 @@ + + + +CSS3 test: box-shadow + + + + + +

http://www.w3.org/TR/css3-background/#the-box-shadow

+ +
+ +

+[#p01] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p02] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p03] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p04] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p05] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p06] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p07] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p08] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+ +
+ + + diff --git a/css3-tests/box-sizing.html b/css3-tests/box-sizing.html new file mode 100644 index 0000000..884ac4a --- /dev/null +++ b/css3-tests/box-sizing.html @@ -0,0 +1,28 @@ + + + +CSS3 test: box-sizing + + + + + +

http://www.w3.org/TR/css3-background/#the-box-sizing

+ +
+ +

+[#p01] This is a paragraph. +

+

+[#p02] This is a paragraph. +

+ +
+ + + diff --git a/css3-tests/c/base.css b/css3-tests/c/base.css new file mode 100644 index 0000000..b1c4ebd --- /dev/null +++ b/css3-tests/c/base.css @@ -0,0 +1,32 @@ +head {display: block;} +style#tests {display: block; + max-height: 20.33em; + overflow: auto; + white-space: pre; + font: small/1 monospace, serif; + padding: 0 1em 0.75em; + border-bottom: 3px double #999; + background: #DDD; color: #333;} +style[contenteditable]#tests {background: #DED;} +body {margin-top: 0; padding: 0 0 2em;} +p#specref {margin: 0 -8px; padding: 0.5em; + background: #DDD; + border-bottom: 1px solid; + font-style: italic;} +ul#nav {position: fixed; bottom: 0; right: 0; left: 0; + text-align: center; + padding: 0.25em 1em 0.33em; margin: 0; + border-top: 3px double #888; + background: #E8E8E8;} +ul#nav li {display: inline; list-style: none; margin: 0 0.75em;} +ul#nav a:hover {color: rgb(216,0,0);} +ul#nav #i {position: absolute; right: 0; top: 0.33em;} +ul#nav #r {position: absolute; left: 0; top: 0.33em;} +vhr.clr {clear: both; visibility: hidden;} + +.warning {color: maroon; background: #FFC;} +.note {color: #222; background: #EEE; font-style: italic;} +.warning, .note {padding: 0.42em 0.67em 0.23em; margin: 0.5em -0.5em;} +.warning + .note {margin-top: -0.25em;} + +.arena {margin-top: 1.5em;} \ No newline at end of file diff --git a/css3-tests/caption-side.html b/css3-tests/caption-side.html new file mode 100644 index 0000000..2901b8c --- /dev/null +++ b/css3-tests/caption-side.html @@ -0,0 +1,62 @@ + + + +CSS3 test: caption-side + + + + + +

http://www.w3.org/TR/css3-background/#the-caption-side

+ +
+ + + + + + + + + + + + + + + + + + + + +
[#c01] Caption!
HeaderDataDataDataDataData
HeaderDataDataDataDataData
+ + + + + + + + + + + + + + + + + + + +
[#c02] Caption!
HeaderDataDataDataDataData
HeaderDataDataDataDataData
+ +
+ + + diff --git a/css3-tests/column-count.html b/css3-tests/column-count.html new file mode 100644 index 0000000..e1a188a --- /dev/null +++ b/css3-tests/column-count.html @@ -0,0 +1,73 @@ + + + +CSS3 test: column-count + + + + + +

http://www.w3.org/TR/css3-multicol/#column-count

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Three columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-gap.html b/css3-tests/column-gap.html new file mode 100644 index 0000000..fd69fc2 --- /dev/null +++ b/css3-tests/column-gap.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-gap + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-gap

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-rule-color.html b/css3-tests/column-rule-color.html new file mode 100644 index 0000000..281e3d6 --- /dev/null +++ b/css3-tests/column-rule-color.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-color + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-color

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-rule-style.html b/css3-tests/column-rule-style.html new file mode 100644 index 0000000..48884e1 --- /dev/null +++ b/css3-tests/column-rule-style.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-style + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-style

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-rule-width.html b/css3-tests/column-rule-width.html new file mode 100644 index 0000000..1c23de2 --- /dev/null +++ b/css3-tests/column-rule-width.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-width + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-width

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-rule.html b/css3-tests/column-rule.html new file mode 100644 index 0000000..74341ac --- /dev/null +++ b/css3-tests/column-rule.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-span.html b/css3-tests/column-span.html new file mode 100644 index 0000000..16610db --- /dev/null +++ b/css3-tests/column-span.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-span + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-span

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/column-width.html b/css3-tests/column-width.html new file mode 100644 index 0000000..22849dd --- /dev/null +++ b/css3-tests/column-width.html @@ -0,0 +1,73 @@ + + + +CSS3 test: column-width + + + + + +

http://www.w3.org/TR/css3-multicol/#column-width

+ +
+ +
+

"15em" columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

"25em" columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/columns.html b/css3-tests/columns.html new file mode 100644 index 0000000..61ff8f5 --- /dev/null +++ b/css3-tests/columns.html @@ -0,0 +1,73 @@ + + + +CSS3 test: columns + + + + + +

http://www.w3.org/TR/css3-multicol/#columns

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Three columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/content.html b/css3-tests/content.html new file mode 100644 index 0000000..c26bf6b --- /dev/null +++ b/css3-tests/content.html @@ -0,0 +1,27 @@ + + + +CSS3 test: content + + + + + +

http://www.w3.org/TR/css3-content/#content

+ +
+ +

+This is a paragraph containing a span element within its content. +

+

+This is a paragraph containing a span element within its content. +

+ +
+ + + diff --git a/css3-tests/crop.html b/css3-tests/crop.html new file mode 100644 index 0000000..4a2b33d --- /dev/null +++ b/css3-tests/crop.html @@ -0,0 +1,22 @@ + + + +CSS3 test: crop + + + + + +

http://www.w3.org/TR/css3-content/#the-crop

+ +
+

This paragraph contains an uncropped image.

+

This paragraph contains an image cropped to only show "ONE" with the surrounding white area and a pixel of blue to each side byeond that.

+

This paragraph contains an image cropped to only show "ONE" with the surrounding white area and a pixel of blue to each side byeond that.

+
+ + + diff --git a/css3-tests/cursor.html b/css3-tests/cursor.html new file mode 100644 index 0000000..65d4947 --- /dev/null +++ b/css3-tests/cursor.html @@ -0,0 +1,94 @@ + + + +CSS3 test: cursor + + + + + +

http://www.w3.org/TR/css3-ui/#cursor0

+ +
+ +

[#p01]

+

[#p02]

+

[#p03]

+

[#p04]

+

[#p05]

+

[#p06]

+

[#p07]

+

[#p08]

+

[#p09]

+

[#p10]

+

[#p11]

+

[#p12]

+

[#p13]

+

[#p14]

+

[#p15]

+

[#p16]

+

[#p17]

+

[#p18]

+

[#p19]

+

[#p20]

+

[#p21]

+

[#p22]

+

[#p23]

+

[#p24]

+

[#p25]

+

[#p26]

+

[#p27]

+

[#p28]

+

[#p29]

+

[#p30]

+

[#p31]

+

[#p32]

+

[#p33]

+

[#p34]

+

[#p35]

+ +
+ +

-

+ + + diff --git a/css3-tests/f/Anivers-Regular.otf b/css3-tests/f/Anivers-Regular.otf new file mode 100644 index 0000000..0b9adbb Binary files /dev/null and b/css3-tests/f/Anivers-Regular.otf differ diff --git a/css3-tests/f/Diavlo_MEDIUM_II_37.otf b/css3-tests/f/Diavlo_MEDIUM_II_37.otf new file mode 100644 index 0000000..1cfea27 Binary files /dev/null and b/css3-tests/f/Diavlo_MEDIUM_II_37.otf differ diff --git a/css3-tests/f/Futura.ttc b/css3-tests/f/Futura.ttc new file mode 100644 index 0000000..06e229b Binary files /dev/null and b/css3-tests/f/Futura.ttc differ diff --git a/css3-tests/f/MyriadPro-Bold.otf b/css3-tests/f/MyriadPro-Bold.otf new file mode 100644 index 0000000..a4c78b0 Binary files /dev/null and b/css3-tests/f/MyriadPro-Bold.otf differ diff --git a/css3-tests/f/MyriadPro-Cond.otf b/css3-tests/f/MyriadPro-Cond.otf new file mode 100644 index 0000000..c85dd1b Binary files /dev/null and b/css3-tests/f/MyriadPro-Cond.otf differ diff --git a/css3-tests/f/MyriadPro-Regular.otf b/css3-tests/f/MyriadPro-Regular.otf new file mode 100644 index 0000000..57a953b Binary files /dev/null and b/css3-tests/f/MyriadPro-Regular.otf differ diff --git a/css3-tests/f/Nadyezhda SL One.ttf b/css3-tests/f/Nadyezhda SL One.ttf new file mode 100644 index 0000000..6ea7c9b Binary files /dev/null and b/css3-tests/f/Nadyezhda SL One.ttf differ diff --git a/css3-tests/f/Skia.ttf b/css3-tests/f/Skia.ttf new file mode 100644 index 0000000..be29869 Binary files /dev/null and b/css3-tests/f/Skia.ttf differ diff --git a/css3-tests/f/SourceSansPro-Bold.ttf b/css3-tests/f/SourceSansPro-Bold.ttf new file mode 100644 index 0000000..b8d40c0 Binary files /dev/null and b/css3-tests/f/SourceSansPro-Bold.ttf differ diff --git a/css3-tests/f/SourceSansPro-Regular.otf b/css3-tests/f/SourceSansPro-Regular.otf new file mode 100644 index 0000000..b9c6c5d Binary files /dev/null and b/css3-tests/f/SourceSansPro-Regular.otf differ diff --git a/css3-tests/f/SwitzeraADF-Bold.otf b/css3-tests/f/SwitzeraADF-Bold.otf new file mode 100644 index 0000000..ace7802 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Bold.otf differ diff --git a/css3-tests/f/SwitzeraADF-BoldExt.otf b/css3-tests/f/SwitzeraADF-BoldExt.otf new file mode 100644 index 0000000..699b15a Binary files /dev/null and b/css3-tests/f/SwitzeraADF-BoldExt.otf differ diff --git a/css3-tests/f/SwitzeraADF-BoldItalic.otf b/css3-tests/f/SwitzeraADF-BoldItalic.otf new file mode 100644 index 0000000..2c75d37 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-BoldItalic.otf differ diff --git a/css3-tests/f/SwitzeraADF-Cond.otf b/css3-tests/f/SwitzeraADF-Cond.otf new file mode 100644 index 0000000..8aa25e5 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Cond.otf differ diff --git a/css3-tests/f/SwitzeraADF-Ext.otf b/css3-tests/f/SwitzeraADF-Ext.otf new file mode 100644 index 0000000..366eddc Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Ext.otf differ diff --git a/css3-tests/f/SwitzeraADF-Italic.otf b/css3-tests/f/SwitzeraADF-Italic.otf new file mode 100644 index 0000000..2f536e0 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Italic.otf differ diff --git a/css3-tests/f/SwitzeraADF-LightCond.otf b/css3-tests/f/SwitzeraADF-LightCond.otf new file mode 100644 index 0000000..8c69a3f Binary files /dev/null and b/css3-tests/f/SwitzeraADF-LightCond.otf differ diff --git a/css3-tests/f/SwitzeraADF-Regular.eot b/css3-tests/f/SwitzeraADF-Regular.eot new file mode 100644 index 0000000..dd4a6ad Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Regular.eot differ diff --git a/css3-tests/f/SwitzeraADF-Regular.otf b/css3-tests/f/SwitzeraADF-Regular.otf new file mode 100644 index 0000000..33c34e5 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Regular.otf differ diff --git a/css3-tests/f/SwitzeraADF-Regular.svg b/css3-tests/f/SwitzeraADF-Regular.svg new file mode 100644 index 0000000..522067c --- /dev/null +++ b/css3-tests/f/SwitzeraADF-Regular.svg @@ -0,0 +1,245 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/css3-tests/f/SwitzeraADF-Regular.ttf b/css3-tests/f/SwitzeraADF-Regular.ttf new file mode 100644 index 0000000..3612a3c Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Regular.ttf differ diff --git a/css3-tests/f/SwitzeraADF-Regular.woff b/css3-tests/f/SwitzeraADF-Regular.woff new file mode 100644 index 0000000..724aad0 Binary files /dev/null and b/css3-tests/f/SwitzeraADF-Regular.woff differ diff --git a/css3-tests/f/Ubuntu-R.ttf b/css3-tests/f/Ubuntu-R.ttf new file mode 100644 index 0000000..45a038b Binary files /dev/null and b/css3-tests/f/Ubuntu-R.ttf differ diff --git a/css3-tests/flex-direction.html b/css3-tests/flex-direction.html new file mode 100644 index 0000000..ecfc29c --- /dev/null +++ b/css3-tests/flex-direction.html @@ -0,0 +1,43 @@ + + + +CSS3 test: flex-wrap + + + + + +

http://www.w3.org/TR/css3-flexbox/#flex-direction-property

+ +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
+ +
+ + + diff --git a/css3-tests/flex-wrap.html b/css3-tests/flex-wrap.html new file mode 100644 index 0000000..4f21527 --- /dev/null +++ b/css3-tests/flex-wrap.html @@ -0,0 +1,64 @@ + + + +CSS3 test: flex-wrap + + + + + + +

http://www.w3.org/TR/css3-flexbox/#flex-wrap-property

+ +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
  9. +
  10. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
  9. +
  10. +
  11. +
  12. +
+ +
+ + + diff --git a/css3-tests/float-offset.html b/css3-tests/float-offset.html new file mode 100644 index 0000000..00f77eb --- /dev/null +++ b/css3-tests/float-offset.html @@ -0,0 +1,27 @@ + + + +CSS3 test: float-offset + + + + + +

http://www.w3.org/TR/css3-gcpm/#float-offset

+ +
+ +

[#p01] A paragraph containing a floated image.

+

[#p02] A paragraph containing a floated image.

+

[#p03] A paragraph containing a floated image.

+ +
+ + + diff --git a/css3-tests/font-face-2.html b/css3-tests/font-face-2.html new file mode 100644 index 0000000..4dd73a4 --- /dev/null +++ b/css3-tests/font-face-2.html @@ -0,0 +1,37 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph containing text inside a span as well as text without.

+

[#p02] A paragraph containing text inside a span as well as text without.

+

[#p03] A paragraph containing text inside a span as well as text without.

+ +
+ + + diff --git a/css3-tests/font-face-3.html b/css3-tests/font-face-3.html new file mode 100644 index 0000000..71b278c --- /dev/null +++ b/css3-tests/font-face-3.html @@ -0,0 +1,52 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph of text.

+

[#p02] A paragraph of text.

+

[#p03] A paragraph of text.

+

[#p04] A paragraph of text.

+

[#p05] A paragraph of text.

+ +
+ + + diff --git a/css3-tests/font-face.html b/css3-tests/font-face.html new file mode 100644 index 0000000..1b97983 --- /dev/null +++ b/css3-tests/font-face.html @@ -0,0 +1,77 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p02] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p03] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p04] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+ +
+ + + diff --git a/css3-tests/font-feature-settings-2.html b/css3-tests/font-feature-settings-2.html new file mode 100644 index 0000000..c761ad1 --- /dev/null +++ b/css3-tests/font-feature-settings-2.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-feature-settings + + + + + + +

+ +
+ +

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+ +
+ + + diff --git a/css3-tests/font-feature-settings.html b/css3-tests/font-feature-settings.html new file mode 100644 index 0000000..bd1ac9c --- /dev/null +++ b/css3-tests/font-feature-settings.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-feature-settings + + + + + + +

+ +
+ +

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+ +
+ + + diff --git a/css3-tests/font-kerning.html b/css3-tests/font-kerning.html new file mode 100644 index 0000000..7275694 --- /dev/null +++ b/css3-tests/font-kerning.html @@ -0,0 +1,43 @@ + + + +CSS3 test: font-kerning + + + + + + +

http://w3.org/TR/css3-fonts/#font-kerning-prop

+ +
+ +

[.t1.c1] A paragraph of text.

+

[.t1.c2] A paragraph of text.

+

[.t1.c3] A paragraph of text.

+ +

[.t2.c1] A paragraph of text.

+

[.t2.c2] A paragraph of text.

+

[.t2.c3] A paragraph of text.

+ +
+ + + diff --git a/css3-tests/font-size-adjust.html b/css3-tests/font-size-adjust.html new file mode 100644 index 0000000..4c673d5 --- /dev/null +++ b/css3-tests/font-size-adjust.html @@ -0,0 +1,25 @@ + + + +CSS3 test: font-size-adjust + + + + + +

http://www.w3.org/TR/css3-fonts/#font-size-adjust

+ +

NOTE: if the two characters following are the same size, the user agent has failed this test. A passing result shows the second character almost twice the size of the first—specifically [100px × (1 ÷ 0.52) = 192.3px].

+ +
+ +

bb

+ +
+ + + diff --git a/css3-tests/font-stretch.html b/css3-tests/font-stretch.html new file mode 100644 index 0000000..7bf5894 --- /dev/null +++ b/css3-tests/font-stretch.html @@ -0,0 +1,50 @@ + + + +CSS3 test: font-stretch + + + + + + +

http://w3.org/TR/css3-fonts/#font-stretch-prop

+ +

+WARNING: this test will only pass if the font family in use has width-variant faces. Therefore, a user agent can support font-stretch and still appear to fail this test. +

+

NOTE: this test uses faces of SwitzeraADF, assigning various individual faces to various stretch levels (and cheating by using a light condensed face to substitue for “ultra-condensed” and a bold extended face for “ultra-expanded”). If the following paragraphs are in a serif font, then the font has failed to load. If they are sans-serif, then the font has most likely loaded and the test should be valid.

+ +
+ +

[#p01] A paragraph of text.

+

[#p02] A paragraph of text.

+

[#p03] A paragraph of text.

+

[#p04] A paragraph of text.

+

[#p05] A paragraph of text.

+

[#p06] A paragraph of text.

+

[#p07] A paragraph of text.

+

[#p08] A paragraph of text.

+

[#p09] A paragraph of text.

+ +
+ + + diff --git a/css3-tests/font-style.html b/css3-tests/font-style.html new file mode 100644 index 0000000..941ddd1 --- /dev/null +++ b/css3-tests/font-style.html @@ -0,0 +1,38 @@ + + + +CSS3 test: font-style + + + + + +

http://w3.org/TR/css3-fonts/#font-style

+ +
+ +

[#p00] A paragraph of text with some italic text and then some oblique text.

+

[#p01] A paragraph of text with some italic text and then some oblique text.

+

[#p02] A paragraph of text with some italic text and then some oblique text.

+

[#p03] A paragraph of text with some italic text and then some oblique text.

+

[#p04] A paragraph of text with some italic text and then some oblique text.

+

[#p05] A paragraph of text with some italic text and then some oblique text.

+

[#p06] A paragraph of text with some italic text and then some oblique text.

+

[#p07] A paragraph of text with some italic text and then some oblique text.

+ +
+ + + diff --git a/css3-tests/font-synthesis.html b/css3-tests/font-synthesis.html new file mode 100644 index 0000000..af90587 --- /dev/null +++ b/css3-tests/font-synthesis.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-synthesis + + + + + +

http://w3.org/TR/css3-fonts/#font-synthesis

+ +

WARNING: this test can only be passed if the font family in use lacks bold and italic faces. Therefore, a user agent can support font-synthesis and still appear to fail this test.

+

NOTE: this test uses the font face Myriad Pro Regular. This single face was specifically selected because it lacks both bold and italic faces. If the following paragraphs are in a serif font, then the font has failed to load. If they are sans-serif, then the font has most likely loaded and the test should be valid.

+ +
+

[#p01] This is a paragraph with bold and italic children. There should be neither bold nor italic.

+

[#p02] This is a paragraph with bold and italic children. There should be bold, but not italic.

+

[#p03] This is a paragraph with bold and italic children. There should be italic, but not bold.

+

[#p04] This is a paragraph with bold and italic children. There should be both bold and italic.

+ +
+ + + diff --git a/css3-tests/font-variant-ligatures.html b/css3-tests/font-variant-ligatures.html new file mode 100644 index 0000000..89d25a5 --- /dev/null +++ b/css3-tests/font-variant-ligatures.html @@ -0,0 +1,110 @@ + + + +CSS3 test: font-variant-ligatures + + + + + + +

http://www.w3.org/TR/css3-fonts/.font-variant-ligatures-prop

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row ID.on.off
[.t01]if fi ff tf ft jf fjif fi ff tf ft jf fj
[.t02]most Jesuit effectsmost Jesuit effects
[.t03]most Jesuit effectsmost Jesuit effects
[.t04]this & thatthis & that
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row ID.on.off
[.t01]ao bxao bx
[.t02]avav
[.t03]bjbj
[.t04]alal
+ +
+aa ab ac ad ae af ag ah ai aj ak al am 
+an ao ap aq ar as at au av aw ax ay az
+ba bb bc bd be bf bg bh bi bj bk bl bm 
+bn bo bp bq br bs bt bu bv bw bx by bz
+ca cb cc cd ce cf cg ch ci cj ck cl cm 
+cn co cp cq cr cs ct cu cv cw cx cy cz
+da db dc dd de df dg dh di dj dk dl dm 
+dn do dp dq dr ds dt du dv dw dx dy dz
+ea eb ec ed ee ef eg eh ei ej ek el em 
+en eo ep eq er es et eu ev ew ex ey ez
+
+ +
+ + + diff --git a/css3-tests/font-variant-numeric.html b/css3-tests/font-variant-numeric.html new file mode 100644 index 0000000..556db1f --- /dev/null +++ b/css3-tests/font-variant-numeric.html @@ -0,0 +1,117 @@ + + + +CSS3 test: font-variant-numeric + + + + + + +

http://www.w3.org/TR/css3-fonts/.font-variant-ligatures-prop

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row IDraw.st1.st2
[.t01]1,234
5,678
9,012
1,234
5,678
9,012
1,234
5,678
9,012
[.t02]1,234
5,678
9,012
1,234
5,678
9,012
1,234
5,678
9,012
[.t03]33 1/333 1/333 1/3
[.t04]900090009000
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row IDraw.st1.st2
[.t01]bz clbzcl
[.t02]cr emcrem
[.t03]bc aebcae
[.t04]cn ezcnez
+ +
+aa ab ac ad ae af ag ah ai aj ak al am 
+an ao ap aq ar as at au av aw ax ay az
+ba bb bc bd be bf bg bh bi bj bk bl bm 
+bn bo bp bq br bs bt bu bv bw bx by bz
+ca cb cc cd ce cf cg ch ci cj ck cl cm 
+cn co cp cq cr cs ct cu cv cw cx cy cz
+da db dc dd de df dg dh di dj dk dl dm 
+dn do dp dq dr ds dt du dv dw dx dy dz
+ea eb ec ed ee ef eg eh ei ej ek el em 
+en eo ep eq er es et eu ev ew ex ey ez
+
+ +
+ + + diff --git a/css3-tests/font-weight.html b/css3-tests/font-weight.html new file mode 100644 index 0000000..de3dab5 --- /dev/null +++ b/css3-tests/font-weight.html @@ -0,0 +1,125 @@ + + + +CSS3 test: font-style + + + + + +

http://w3.org/TR/css3-fonts/#font-style

+ +
+ +

[#p00] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p01] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p02] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p03] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p04] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p05] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p06] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p07] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+ +
+ + + diff --git a/css3-tests/hanging-punctuation.html b/css3-tests/hanging-punctuation.html new file mode 100644 index 0000000..1b42099 --- /dev/null +++ b/css3-tests/hanging-punctuation.html @@ -0,0 +1,22 @@ + + + +CSS3 test: hanging-punctuation + + + + + +

http://www.w3.org/TR/css3-text/#hanging-punctuation

+ +
+

“This is a paragraph ([#p01]) with a leading quotation mark. It should hang off the beginning of the first line of text such that the non-quotation characters line up with each other vertically.”

+

“This is a paragraph ([#p02]) with a trailing quotation mark. It should hang off the end of the last line in order to avoid forced line-wrapping.”

+
+ + + diff --git a/css3-tests/hyphenate-character.html b/css3-tests/hyphenate-character.html new file mode 100644 index 0000000..910a876 --- /dev/null +++ b/css3-tests/hyphenate-character.html @@ -0,0 +1,27 @@ + + + +CSS3 test: hyphenate-character + + + + + +

http://www.w3.org/TR/css3-gcpm/#hyphenate-character

+ +
+

It is most likely necessary to resize the viewport to properly evaluate this test.

+ +

[#p01] This is a paragraph with embedded hyphenation hints but no hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p02] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Hyphens should use this character: ℒ. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+ + + diff --git a/css3-tests/hyphens.html b/css3-tests/hyphens.html new file mode 100644 index 0000000..e529206 --- /dev/null +++ b/css3-tests/hyphens.html @@ -0,0 +1,34 @@ + + + +CSS3 test: hyphens + + + + + +

http://www.w3.org/TR/css3-gcpm/#hyphens

+ +
+

It is most likely necessary to resize the viewport to properly evaluate this test.

+ +

[#p01] This is a paragraph with no embedded hyphenation hints and no hyphen-related CSS applied. Corporate gibberish follows. Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness!

+ +

[#p02] This is a paragraph with embedded hyphenation hints but no hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p03] This is a paragraph with no embedded hyphenation hints but hyphen-related CSS applied. Corporate gibberish follows. Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness!

+ +

[#p04] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p05] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness! (NOTE: in this case, the CSS requires hyphenation hints to be ignored.)

+
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+ + + diff --git a/css3-tests/i/Globe.ani b/css3-tests/i/Globe.ani new file mode 100644 index 0000000..3d43df8 Binary files /dev/null and b/css3-tests/i/Globe.ani differ diff --git a/css3-tests/i/blob-green.gif b/css3-tests/i/blob-green.gif new file mode 100644 index 0000000..843aff1 Binary files /dev/null and b/css3-tests/i/blob-green.gif differ diff --git a/css3-tests/i/box-red.gif b/css3-tests/i/box-red.gif new file mode 100644 index 0000000..9c89924 Binary files /dev/null and b/css3-tests/i/box-red.gif differ diff --git a/css3-tests/i/dot-red.gif b/css3-tests/i/dot-red.gif new file mode 100644 index 0000000..b3e84a9 Binary files /dev/null and b/css3-tests/i/dot-red.gif differ diff --git a/css3-tests/i/grid-100.png b/css3-tests/i/grid-100.png new file mode 100644 index 0000000..23d05e8 Binary files /dev/null and b/css3-tests/i/grid-100.png differ diff --git a/css3-tests/i/grid-400.png b/css3-tests/i/grid-400.png new file mode 100644 index 0000000..b7c2a0f Binary files /dev/null and b/css3-tests/i/grid-400.png differ diff --git a/css3-tests/i/hatchgrid-100.png b/css3-tests/i/hatchgrid-100.png new file mode 100644 index 0000000..c28d229 Binary files /dev/null and b/css3-tests/i/hatchgrid-100.png differ diff --git a/css3-tests/i/hatchgrid-100.psd b/css3-tests/i/hatchgrid-100.psd new file mode 100644 index 0000000..9375ada Binary files /dev/null and b/css3-tests/i/hatchgrid-100.psd differ diff --git a/css3-tests/i/hatchgrid-150.png b/css3-tests/i/hatchgrid-150.png new file mode 100644 index 0000000..168b7e0 Binary files /dev/null and b/css3-tests/i/hatchgrid-150.png differ diff --git a/css3-tests/i/hatchgrid-150.psd b/css3-tests/i/hatchgrid-150.psd new file mode 100644 index 0000000..5d298a8 Binary files /dev/null and b/css3-tests/i/hatchgrid-150.psd differ diff --git a/css3-tests/i/hatchgrid.png b/css3-tests/i/hatchgrid.png new file mode 100644 index 0000000..1c30361 Binary files /dev/null and b/css3-tests/i/hatchgrid.png differ diff --git a/css3-tests/i/hatchgrid.psd b/css3-tests/i/hatchgrid.psd new file mode 100644 index 0000000..740d228 Binary files /dev/null and b/css3-tests/i/hatchgrid.psd differ diff --git a/css3-tests/i/one-two.gif b/css3-tests/i/one-two.gif new file mode 100644 index 0000000..a5bbc39 Binary files /dev/null and b/css3-tests/i/one-two.gif differ diff --git a/css3-tests/i/target.gif b/css3-tests/i/target.gif new file mode 100644 index 0000000..fa41622 Binary files /dev/null and b/css3-tests/i/target.gif differ diff --git a/css3-tests/i/target.png b/css3-tests/i/target.png new file mode 100644 index 0000000..404c979 Binary files /dev/null and b/css3-tests/i/target.png differ diff --git a/css3-tests/icon.html b/css3-tests/icon.html new file mode 100644 index 0000000..10aab8d --- /dev/null +++ b/css3-tests/icon.html @@ -0,0 +1,28 @@ + + + +CSS3 test: icon + + + + + +

http://www.w3.org/TR/css3-ui/#icon

+ +
+ +

+[#p01] Consider an image () and an icon (). Then replace the image with the icon: . +

+

+[#p02] Consider a span. Then replace one with an icon: am I an icon yet? +

+ +
+ + + diff --git a/css3-tests/image-resolution.html b/css3-tests/image-resolution.html new file mode 100644 index 0000000..7913a25 --- /dev/null +++ b/css3-tests/image-resolution.html @@ -0,0 +1,30 @@ + + + +CSS3 test: image-resolution + + + + + +

http://www.w3.org/TR/css3-gcpm/#image-resolution0

+ +
+ +

+[#p01] This is a paragraph containing an image. +

+

+[#p02] This is a paragraph containing an image. +

+

+[#p03] This is a paragraph containing an image. +

+ +
+ + + diff --git a/css3-tests/justify-content.html b/css3-tests/justify-content.html new file mode 100644 index 0000000..3312dc7 --- /dev/null +++ b/css3-tests/justify-content.html @@ -0,0 +1,65 @@ + + + +CSS3 test: justify-content + + + + + + +

http://www.w3.org/TR/css3-flexbox/#justify-content-property

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3-tests/line-break.html b/css3-tests/line-break.html new file mode 100644 index 0000000..d9b085e --- /dev/null +++ b/css3-tests/line-break.html @@ -0,0 +1,41 @@ + + + +CSS3 test: line-break + + + + + +

http://www.w3.org/TR/css3-text/#line-break

+

+This page is currently a placeholder. For some super-crazy-detailed tests of this property, see http://www.w3.org/International/tests/html-css/line-break-ja-zh/results-ja. +

+ +
+ +

+[noID] +

+

+[#p01] +

+

+[#p02] +

+

+[#p03] +

+

+[#p04] +

+ + + + diff --git a/css3-tests/line-height.html b/css3-tests/line-height.html new file mode 100644 index 0000000..f5327e2 --- /dev/null +++ b/css3-tests/line-height.html @@ -0,0 +1,28 @@ + + + +CSS3 test: line-height + + + + + +

http://www.w3.org/TR/css3-linebox/#line-height

+ +
+ +
+[#d01] This is a div in which resides a paragraph. The line-height of the div has been increased to one-and-one-half times the font size of the div. +

+This is the paragrph. It should use the same line-height as the div even though its font size is much smaller and it starts out with an even smaller line-height. The latter should be overridden by 'none'. +

+ +
+ +
+ + + diff --git a/css3-tests/list-style-type.html b/css3-tests/list-style-type.html new file mode 100644 index 0000000..5fd3117 --- /dev/null +++ b/css3-tests/list-style-type.html @@ -0,0 +1,269 @@ + + + +CSS3 test: list-style-type + + + + + + +

http://www.w3.org/TR/css3-lists/#list-style-type

+ +
+ +
+

[#d01] Glyph list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
+ +
+

[#d02] Symbolic (et cetera) list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
+ +
+

[#d03] "Non-repeating" list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
+ +
+

[#d04] Algorithmic list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
+ +
+

[#d05] Numeric list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
  • [.l18]
  • two
  • three
+
  • [.l19]
  • two
  • three
+
  • [.l20]
  • two
  • three
+
  • [.l21]
  • two
  • three
+
  • [.l22]
  • two
  • three
+
  • [.l23]
  • two
  • three
+
  • [.l24]
  • two
  • three
+
+ +
+

[#d06] Alphabetic list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
  • [.l18]
  • two
  • three
+
  • [.l19]
  • two
  • three
+
  • [.l20]
  • two
  • three
+
  • [.l21]
  • two
  • three
+
  • [.l22]
  • two
  • three
+
  • [.l23]
  • two
  • three
+
  • [.l24]
  • two
  • three
+
  • [.l25]
  • two
  • three
+
  • [.l26]
  • two
  • three
+
  • [.l27]
  • two
  • three
+
  • [.l28]
  • two
  • three
+
  • [.l29]
  • two
  • three
+
  • [.l30]
  • two
  • three
+
  • [.l31]
  • two
  • three
+
  • [.l32]
  • two
  • three
+
  • [.l33]
  • two
  • three
+
  • [.l34]
  • two
  • three
+
  • [.l35]
  • two
  • three
+
  • [.l36]
  • two
  • three
+
  • [.l37]
  • two
  • three
+
  • [.l38]
  • two
  • three
+
  • [.l39]
  • two
  • three
+
  • [.l40]
  • two
  • three
+
  • [.l41]
  • two
  • three
+
  • [.l42]
  • two
  • three
+
  • [.l43]
  • two
  • three
+
+ +
+ +
+ + + diff --git a/css3-tests/object-fit.html b/css3-tests/object-fit.html new file mode 100644 index 0000000..06e6faf --- /dev/null +++ b/css3-tests/object-fit.html @@ -0,0 +1,25 @@ + + + +CSS3 test: object-fit + + + + + +

http://www.w3.org/TR/css3-page/#fit

+ +
+ +

A paragraph containing an un-fit image. The next two paragraphs will contain fit images.

+

+

+ +
+ + + diff --git a/css3-tests/order.html b/css3-tests/order.html new file mode 100644 index 0000000..5e8a66f --- /dev/null +++ b/css3-tests/order.html @@ -0,0 +1,46 @@ + + + +CSS3 test: order + + + + + +

http://www.w3.org/TR/css3-flexbox/#order-property

+ +
+ +[#l01] +
    +
  1. List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
  7. List item 4
  8. +
  9. List item 5
  10. +
+ +[#l02] +
    +
  1. List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
  7. List item 4
  8. +
  9. List item 5
  10. +
+ +
+ + + diff --git a/css3-tests/outline-offset.html b/css3-tests/outline-offset.html new file mode 100644 index 0000000..db5d3c2 --- /dev/null +++ b/css3-tests/outline-offset.html @@ -0,0 +1,32 @@ + + + +CSS3 test: outline-offset + + + + + +

http://www.w3.org/TR/css3-ui/#outline-offset0

+ +
+ +

+[#p01] This is a paragraph containing a span whose outline has been offset. +

+

+[#p02] This is a paragraph containing a span whose outline has been offset. +

+

+[#p03] This is a paragraph containing a span whose outline may have been offset even though the specification forbids it. If it is two pixels, orange, dashed, or offset inward, then the browser has gone beyond the specification. +

+ +
+ + + diff --git a/css3-tests/overflow-style.html b/css3-tests/overflow-style.html new file mode 100644 index 0000000..c18b4e8 --- /dev/null +++ b/css3-tests/overflow-style.html @@ -0,0 +1,26 @@ + + + +CSS3 test: overflow-style + + + + + +

http://www.w3.org/TR/css3-marquee/#overflow-style

+ +
+

+[#p01] This is a paragraph of text. It should marquee horizontally in cases where it overflows its parent element. +

+

+[#p02] This is a paragraph of text. It should marquee vertically in cases where it overflows its parent element. +

+
+ + + diff --git a/css3-tests/overflow-wrap.html b/css3-tests/overflow-wrap.html new file mode 100644 index 0000000..9f7c66b --- /dev/null +++ b/css3-tests/overflow-wrap.html @@ -0,0 +1,30 @@ + + + +CSS3 test: overflow-wrap + + + + + +

http://www.w3.org/TR/css3-text/#overflow-wrap

+

See also the test for word-wrap, which is an alternate name for overflow-wrap.

+ +
+ +

+[#p01] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+

+[#p02] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/overflow-x.html b/css3-tests/overflow-x.html new file mode 100644 index 0000000..3969cb7 --- /dev/null +++ b/css3-tests/overflow-x.html @@ -0,0 +1,39 @@ + + + +CSS3 test: overflow-x + + + + + +

http://www.w3.org/TR/css3-box/#overflow-x

+ +
+
+[#d01] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d02] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d03] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+ + + diff --git a/css3-tests/overflow-y.html b/css3-tests/overflow-y.html new file mode 100644 index 0000000..7fbf282 --- /dev/null +++ b/css3-tests/overflow-y.html @@ -0,0 +1,39 @@ + + + +CSS3 test: overflow-x + + + + + +

http://www.w3.org/TR/css3-box/#overflow-y

+ +
+
+[#d01] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d02] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d03] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+ + + diff --git a/css3-tests/overflow.html b/css3-tests/overflow.html new file mode 100644 index 0000000..cb7886f --- /dev/null +++ b/css3-tests/overflow.html @@ -0,0 +1,61 @@ + + + +CSS3 test: overflow + + + + + +

http://www.w3.org/TR/css3-marquee/#overflow

+ +
+
+[#d01] visible +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d02] hidden +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d03] scroll +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d04] auto +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d05] no-display +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d06] no-content +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+ + + diff --git a/css3-tests/perspective-origin.html b/css3-tests/perspective-origin.html new file mode 100644 index 0000000..f451fab --- /dev/null +++ b/css3-tests/perspective-origin.html @@ -0,0 +1,39 @@ + + + + +CSS3 test: perspective-origin + + + + + +

+ +
+ +
+[#d01] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d02] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d03] Following is a div with some perspective (we hope). +
Total perspective!
+
+ +
+ + + diff --git a/css3-tests/perspective.html b/css3-tests/perspective.html new file mode 100644 index 0000000..5ce5e0d --- /dev/null +++ b/css3-tests/perspective.html @@ -0,0 +1,39 @@ + + + + +CSS3 test: perspective + + + + + +

+ +
+ +
+[#d01] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d02] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d03] Following is a div with some perspective (we hope). +
Total perspective!
+
+ +
+ + + diff --git a/css3-tests/punctuation-trim.html b/css3-tests/punctuation-trim.html new file mode 100644 index 0000000..638f151 --- /dev/null +++ b/css3-tests/punctuation-trim.html @@ -0,0 +1,31 @@ + + + +CSS3 test: punctuation-trim + + + + + +

http://www.w3.org/TR/css3-text/#punctuation-trim

+ +
+ +
    +
  1. [#li01] (( •( )( )• ))
  2. +
  3. [#li02] (( •( )( )• ))
  4. +
  5. [#li03] (( •( )( )• ))
  6. +
  7. [#li04] (( •( )( )• ))
  8. +
  9. [#li05] (( •( )( )• ))
  10. +
+ +
+ + + diff --git a/css3-tests/resize.html b/css3-tests/resize.html new file mode 100644 index 0000000..97f8e98 --- /dev/null +++ b/css3-tests/resize.html @@ -0,0 +1,30 @@ + + + +CSS3 test: resize + + + + + +

http://www.w3.org/TR/css3-ui/#resize0

+ +
+

+[#p01] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+

+[#p02] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+

+[#p03] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+
+ + + diff --git a/css3-tests/rotation.html b/css3-tests/rotation.html new file mode 100644 index 0000000..2940eaf --- /dev/null +++ b/css3-tests/rotation.html @@ -0,0 +1,32 @@ + + + +CSS3 test: rotation + + + + + +

http://www.w3.org/TR/css3-box/#rotating +

+ +
+ +

+[#p01] This is a paragraph of text. +

+

+[#p02] This is a paragraph of text. +

+

+[#p03] This is a paragraph of text. +

+ +
+ + + diff --git a/css3-tests/sel-selection.html b/css3-tests/sel-selection.html new file mode 100644 index 0000000..0f44335 --- /dev/null +++ b/css3-tests/sel-selection.html @@ -0,0 +1,32 @@ + + + +CSS3 test: the element selector + + + + + +

+

+ +
+Here's some div text. + +

+This is a paragraph. Inside it we find a span element which should style differently. +

+ +More div text. +
+ + + diff --git a/css3-tests/tab-size.html b/css3-tests/tab-size.html new file mode 100644 index 0000000..2fc7d0a --- /dev/null +++ b/css3-tests/tab-size.html @@ -0,0 +1,50 @@ + + + +CSS3 test: tab-size + + + + + +

http://www.w3.org/TR/css3-text/#tab-size

+ +
+ +

+ There are twenty-four spaces before this text. (no ID) +

+

+ There are three tabs before this text. (no ID) +

+

+ [#p01] There are three tabs before this text. +

+

+ [#p02] There are three tabs before this text. +

+

+ [#p03] There are three tabs before this text. +

+

+ [#p04] There are three tabs before this text. +

+

+ [#p05] There are three tabs before this text. +

+

+ [#p06] There are three tabs before this text. +

+ +
+ + + diff --git a/css3-tests/text-align-last.html b/css3-tests/text-align-last.html new file mode 100644 index 0000000..0f8d2e1 --- /dev/null +++ b/css3-tests/text-align-last.html @@ -0,0 +1,45 @@ + + + +CSS3 test: text-align-last + + + + + +

http://www.w3.org/TR/css3-text/#text-align-last

+ +
+ +

+[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+

+[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+

+[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+

+[#p04] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+

+[#p05] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+

+[#p06] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/text-align.html b/css3-tests/text-align.html new file mode 100644 index 0000000..4a1d577 --- /dev/null +++ b/css3-tests/text-align.html @@ -0,0 +1,105 @@ + + + +CSS3 test: text-align + + + + + + +

http://www.w3.org/TR/css3-text/#text-align

+ +
+ +

+[.p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p01] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

+ +
+ +

+[.p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p02] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B? +

+ +
+ +

+[.p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p03] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

+ +
+ +

+[.p04] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p04] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B? +

+ +
+ +

+[.p05] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p05] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

+ +
+ +

+[.p06] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B?
At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

+

+[.p06] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B?
في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

+ +
+ +
+

[.d01 p] This is a paragraph, and it should be right-justified.

+

[.d01 p + p] This is a paragraph, and it should be centered.

+
+ + + + + + + + + + +
Row 1ABCDEFG
Row 2GABCDEF
Row 3FGABCDE
Row 4EFGABCD
Row 5DEFGABC
Row 6CDEFGAB
Row 7BCDEFGA
Row 81234567
+ +
+

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com. Arabic and Hebrew translations courtesy Google Translate.

+ + + diff --git a/css3-tests/text-justify.html b/css3-tests/text-justify.html new file mode 100644 index 0000000..d592e3e --- /dev/null +++ b/css3-tests/text-justify.html @@ -0,0 +1,33 @@ + + + +CSS3 test: text-justify + + + + + +

http://www.w3.org/TR/css3-text/#text-justify

+ +
+ +

+[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/text-outline.html b/css3-tests/text-outline.html new file mode 100644 index 0000000..da1c171 --- /dev/null +++ b/css3-tests/text-outline.html @@ -0,0 +1,25 @@ + + + +CSS3 test: text-outline + + + + + +

http://www.w3.org/TR/css3-text/#text-outline

+ +
+ +

Heading 1

+

Heading 2

+

Heading 3

+ +
+ + + diff --git a/css3-tests/text-rendering-2.html b/css3-tests/text-rendering-2.html new file mode 100644 index 0000000..384026c --- /dev/null +++ b/css3-tests/text-rendering-2.html @@ -0,0 +1,91 @@ + + + +CSS3 test: text-rendering + + + + + + +

+ +
+ +

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+ +
+ + + diff --git a/css3-tests/text-rendering.html b/css3-tests/text-rendering.html new file mode 100644 index 0000000..f582392 --- /dev/null +++ b/css3-tests/text-rendering.html @@ -0,0 +1,60 @@ + + + +CSS3 test: text-rendering + + + + + + +

+ +
+ +

+OX ox OC oc Te te FF ff Fi fi FL fl +

+

+OX ox OC oc Te te FF ff Fi fi FL fl +

+

+OX ox OC oc Te te FF ff Fi fi FL fl +

+

+OX ox OC oc Te te FF ff Fi fi FL fl +

+

+OX ox OC oc Te te FF ff Fi fi FL fl +

+ +
+ +

+Vestibulum id ligua porta felis eusimod semper. +

+

+Vestibulum id ligua porta felis eusimod semper. +

+

+Vestibulum id ligua porta felis eusimod semper. +

+

+Vestibulum id ligua porta felis eusimod semper. +

+

+Vestibulum id ligua porta felis eusimod semper. +

+ + +
+ + + diff --git a/css3-tests/text-shadow.html b/css3-tests/text-shadow.html new file mode 100644 index 0000000..a83fe04 --- /dev/null +++ b/css3-tests/text-shadow.html @@ -0,0 +1,25 @@ + + + +CSS3 test: text-shadow + + + + + +

http://www.w3.org/TR/css3-text/#text-shadow

+ +
+ +

Heading 1

+

Heading 2

+

Heading 3

+ +
+ + + diff --git a/css3-tests/text-wrap.html b/css3-tests/text-wrap.html new file mode 100644 index 0000000..ad30952 --- /dev/null +++ b/css3-tests/text-wrap.html @@ -0,0 +1,32 @@ + + + +CSS3 test: text-wrap + + + + + +

http://www.w3.org/TR/css3-text/#text-wrap

+ +
+ +

+[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/unicode-range.html b/css3-tests/unicode-range.html new file mode 100644 index 0000000..d405eb3 --- /dev/null +++ b/css3-tests/unicode-range.html @@ -0,0 +1,31 @@ + + + +CSS3 test: unicode-range + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

A paragraph containing a span containing the uppercase alphabet in which A though M should be in SourceSansPro Bold and N through Z should be in a serif font. +ABCDEFGHIJKLMNOPQRSTUVWXYZ.

+

A paragraph containing a span containing the lowercase alphabet in which A though M should be in a serif font and N through Z should be in SourceSansPro Bold. +abcdefghijklmnopqrstuvwxyz.

+ +
+ + + diff --git a/css3-tests/val-calc.html b/css3-tests/val-calc.html new file mode 100644 index 0000000..df238b4 --- /dev/null +++ b/css3-tests/val-calc.html @@ -0,0 +1,31 @@ + + + +CSS3 test: the 'calc' unit + + + + + +

http://www.w3.org/TR/css3-values/#calc

+ +
+ +

+[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
+ +
+ +
+If they are not of equal width, then the browser likely does not support the calc unit. +

+ +
+ + + diff --git a/css3-tests/val-ch.html b/css3-tests/val-ch.html new file mode 100644 index 0000000..6fd82ce --- /dev/null +++ b/css3-tests/val-ch.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'ch' unit + + + + + +

http://www.w3.org/TR/css3-values/#relative0

+ +
+ +

+[#p01] This is a paragraph that contains a span element and an img. The two are separated by a br element and should be of equal width. +
+0000000000000000000000000 +
+ +
+If they are not, then the browser likely does not support the ch unit. +

+

+[#p02] This is a paragraph that contains a span element and an img. The two are separated by a br element and should be of equal width. +
+0000000000000000000000000 +
+ +
+If they are not, then the browser likely does not support the ch unit. +

+ +
+ + + diff --git a/css3-tests/val-colors.html b/css3-tests/val-colors.html new file mode 100644 index 0000000..7f644ac --- /dev/null +++ b/css3-tests/val-colors.html @@ -0,0 +1,42 @@ + + + +CSS3 test: color units + + + + + +

http://www.w3.org/TR/css3-values/#calc

+ +
+ +

This is a paragraph. It is the only one that should have a red background.

+

[#p01] This is a paragraph.

+

[#p02] This is a paragraph.

+

[#p03] This is a paragraph.

+

[#p04] This is a paragraph.

+

[#p05] This is a paragraph.

+

[#p06] This is a paragraph.

+

[#p07] This is a paragraph.

+

[#p08] This is a paragraph.

+

[#p09] This is a paragraph.

+

[#p10] This is a paragraph.

+ +
+ + + diff --git a/css3-tests/val-length-units.html b/css3-tests/val-length-units.html new file mode 100644 index 0000000..f32537b --- /dev/null +++ b/css3-tests/val-length-units.html @@ -0,0 +1,53 @@ + + + +CSS3 test: length units + + + + + +

http://www.w3.org/TR/css3-values/

+ +

Based on http://codepen.io/anon/pen/JLdzg

+ +
+ +
400px - pixels (device pixels)
+
20em - relative unit
+
20rem - root em
+
4.167in - inches
+
10.5833cm - centimeters
+
105.833mm - millimeters
+
300pt - points
+
25pc - picas
+
40ex - x-height
+
40ch - based on width of zero (0) character
+
50vw - viewport width
+
50vh - viewport height
+
50vmin - smaller of vw or vh
+
50vmax - larger of vw or vh
+ +
+ + + diff --git a/css3-tests/val-rem.html b/css3-tests/val-rem.html new file mode 100644 index 0000000..edc90f6 --- /dev/null +++ b/css3-tests/val-rem.html @@ -0,0 +1,33 @@ + + + +CSS3 test: the 'rem' unit + + + + + +

http://www.w3.org/TR/css3-values/#relative0

+ +
+ +

+This is a paragraph without any children. It exists as a control to show the basic font size in use. +

+

+[#p01] This is a paragraph with a span element embedded within it. The span should be larger than the text that surrounds it and match the size of the previous paragraph. +

+

+[#p02] This is a paragraph with a span element embedded within it. The span should be smaller than the text that surrounds it and match the size of text outisde the span in the previous paragraph. +

+ +
+ + + diff --git a/css3-tests/val-toggle.html b/css3-tests/val-toggle.html new file mode 100644 index 0000000..364d4d5 --- /dev/null +++ b/css3-tests/val-toggle.html @@ -0,0 +1,48 @@ + + + +CSS3 test: the 'toggle' unit + + + + + +

http://www.w3.org/TR/css3-values/#toggle

+ +
+ + + +
+ + + diff --git a/css3-tests/val-vh.html b/css3-tests/val-vh.html new file mode 100644 index 0000000..c5c87bc --- /dev/null +++ b/css3-tests/val-vh.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'vh' unit + + + + + +

http://www.w3.org/TR/css3-values/#relative0

+ +
+ +

+[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
+ +
+ +
+ +
+ +
+ +
+If they all appear the same, then the browser likely does not support the vh unit. Note that if supported, the images should change width as the viewport height changes. +

+ +
+ + + diff --git a/css3-tests/val-vmax.html b/css3-tests/val-vmax.html new file mode 100644 index 0000000..cb700a4 --- /dev/null +++ b/css3-tests/val-vmax.html @@ -0,0 +1,44 @@ + + + +CSS3 test: the 'vmax' unit + + + + + +

http://www.w3.org/TR/css3-values/#viewport-relative-lengths

+ +

+The images in this test should be sized according to either the height or width of the viewport, whichever is greater. +

+ +
+ +

+[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
+ +
+ +
+ +
+ +
+ +
+If they all appear the same, then the browser likely does not support the max unit. Note that if supported, the images should change width as the viewport height changes. +

+ +
+ + + diff --git a/css3-tests/val-vmin.html b/css3-tests/val-vmin.html new file mode 100644 index 0000000..d932589 --- /dev/null +++ b/css3-tests/val-vmin.html @@ -0,0 +1,44 @@ + + + +CSS3 test: the 'vmin' unit + + + + + +

http://www.w3.org/TR/css3-values/#viewport-relative-lengths

+ +

+The images in this test should be sized according to either the height or width of the viewport, whichever is lesser. +

+ +
+ +

+[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
+ +
+ +
+ +
+ +
+ +
+If they all appear the same, then the browser likely does not support the vmin unit. Note that if supported, the images should change width as the viewport height changes. +

+ +
+ + + diff --git a/css3-tests/val-vw.html b/css3-tests/val-vw.html new file mode 100644 index 0000000..f58f6a7 --- /dev/null +++ b/css3-tests/val-vw.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'vw' unit + + + + + +

http://www.w3.org/TR/css3-values/#relative0

+ +
+ +

+[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
+ +
+ +
+ +
+ +
+ +
+If they all appear the same, then the browser likely does not support the vw unit. Note that if supported, the images should change width as the viewport width changes. +

+ +
+ + + diff --git a/css3-tests/white-space.html b/css3-tests/white-space.html new file mode 100644 index 0000000..4800ffb --- /dev/null +++ b/css3-tests/white-space.html @@ -0,0 +1,55 @@ + + + +CSS3 test: white-space + + + + + +

http://www.w3.org/TR/css3-text/#white-space

+ +
+ +

+[#p01] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

+

+[#p02] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

+

+[#p03] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

+

+[#p04] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

+

+[#p05] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-tests/word-break.html b/css3-tests/word-break.html new file mode 100644 index 0000000..8c8292e --- /dev/null +++ b/css3-tests/word-break.html @@ -0,0 +1,37 @@ + + + +CSS3 test: word-break + + + + + +

http://www.w3.org/TR/css3-text/#word-break

+

+The following tests use slightly modified text taken from the 13 November 2012 draft of “CSS Text Module Level 3”. It mixes a variety of languages and writing systems. +

+ +
+ +

+[noID] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

+

+[#p01] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

+

+[#p02] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

+

+[#p03] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

+ + + + diff --git a/css3-tests/word-wrap.html b/css3-tests/word-wrap.html new file mode 100644 index 0000000..4f07f05 --- /dev/null +++ b/css3-tests/word-wrap.html @@ -0,0 +1,30 @@ + + + +CSS3 test: word-wrap + + + + + +

http://www.w3.org/TR/css3-text/#word-wrap

+

See also the test for overflow-wrap, which is an alternate name for word-wrap.

+ +
+ +

+[#p01] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+

+[#p02] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3-text/text-align.html b/css3-text/text-align.html new file mode 100644 index 0000000..95af5f1 --- /dev/null +++ b/css3-text/text-align.html @@ -0,0 +1,40 @@ + + + +Align Text + + + + +

+This is a paragraph (p element) that contains ordinary text. It has had text-align-last: right applied to it, so that the last line of text (which will most likely be a partial line) will be right-aligned. +

+ + + + + + + + + + + + + + + + + +
1,834.23
24.77
35,128.00
1,834
2,477,351.28
+ +Specification + + + diff --git a/css3-text/white-space.html b/css3-text/white-space.html new file mode 100644 index 0000000..af6db56 --- /dev/null +++ b/css3-text/white-space.html @@ -0,0 +1,30 @@ + + + +Preserve Spaces + + + + +

This is a paragraph (p element) that contains ordinary text. It is formatted such that the opening and closing tags are at the beginning and end of the single line of source text, with the content text between them. It features two spaces between each sentence, just as God intended. It has had white-space: pre-wrap applied to it, as with all the other p elements in this test.

+

+This is a paragraph (p element) that contains ordinary text. It is formatted such that the opening and closing tags are on lines of their own, with the content text between them. It features two spaces between each sentence, just as God intended. It has had white-space: pre-wrap applied to it, as with all the other p elements in this test. +

+

+This is a paragraph (p element) that contains ordinary text. +It is formatted such that the opening and closing tags are on lines of their own, with the content text between them. +It features a newline between each sentence, which is a bit odd but one can see why it might become a habit. +It has had white-space: pre-wrap applied to it, as with all the other p elements in this test. +

+ +Specification + + + diff --git a/css3-trans-an/focus.png b/css3-trans-an/focus.png new file mode 100644 index 0000000..7a0b3ef Binary files /dev/null and b/css3-trans-an/focus.png differ diff --git a/css3-trans-an/frame-sq.png b/css3-trans-an/frame-sq.png new file mode 100644 index 0000000..b7c2a0f Binary files /dev/null and b/css3-trans-an/frame-sq.png differ diff --git a/css3-trans-an/grid-sq.png b/css3-trans-an/grid-sq.png new file mode 100644 index 0000000..29c4f69 Binary files /dev/null and b/css3-trans-an/grid-sq.png differ diff --git a/css3-trans-an/multieasing.html b/css3-trans-an/multieasing.html new file mode 100644 index 0000000..7648c42 --- /dev/null +++ b/css3-trans-an/multieasing.html @@ -0,0 +1,71 @@ + + + +Bouncy + + + + +
bouncy
+ + + diff --git a/css3-trans-an/nested-fixed.html b/css3-trans-an/nested-fixed.html new file mode 100644 index 0000000..63fb572 --- /dev/null +++ b/css3-trans-an/nested-fixed.html @@ -0,0 +1,88 @@ + + + +Nested Fixed + + + + +
+Outer div. +
+Inner div 1. +
+
+Inner div 2. +
+More outer div. +
+ +
+Outer div. +
+Inner div 1. +
+
+Inner div 2. +
+More outer div. +
+ +

1

+

2

+

3

+

4

+

5

+

6

+

7

+

8

+

9

+

10

+

11

+

12

+

13

+

14

+

15

+

16

+

17

+

18

+

19

+

20

+

21

+

22

+

23

+

24

+

25

+

26

+

27

+

28

+

29

+

30

+

31

+

32

+

33

+

34

+

35

+

36

+

37

+

38

+

39

+

40

+

41

+

42

+ + + diff --git a/css3-trans-an/selectors.html b/css3-trans-an/selectors.html new file mode 100644 index 0000000..0dc4405 --- /dev/null +++ b/css3-trans-an/selectors.html @@ -0,0 +1 @@ + CSS3 Selector Fun
table#checkerboard tr:nth-child(even) td:nth-child(even),
 table#checkerboard tr:nth-child(odd) td:nth-child(odd)
 {color: black; background: white;}
table#checkerboard tr:nth-child(even) td:nth-child(odd),
 table#checkerboard tr:nth-child(odd) td:nth-child(even)
 {color: white; background: black;}
r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
table#alt-row {background: white;}
table#alt-row tr:nth-child(3n+1) {background: silver;}
table#alt-row td:nth-child(2n+4) {font-weight: bold; font-style: italic;}
r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
div.typetest p:first-of-type {color: gray; background: cyan;}
div.typetest p:not-first-of-type {font-style: italic;}
div.typetest p:last-child {text-decoration: underline;}
div.typetest p:not(:last-child) {border: 2px dotted purple;}

This is a paragraph which is first in the DIV.

  • Here's an unordered list...
  • ...with three list items...
  • ...just for fun.

Another paragraph.

Heading-3

And yet another paragraph.

\ No newline at end of file diff --git a/css3-trans-an/transform-containing.html b/css3-trans-an/transform-containing.html new file mode 100644 index 0000000..ae47289 --- /dev/null +++ b/css3-trans-an/transform-containing.html @@ -0,0 +1,68 @@ + + + +Transforms, Transitions, and Containing blocks and Viewports + + + + +
+ +
+This is a fixed-positioned element. Its containing block defaults to the root element but switches to its containing div when that element is transformed by hovering. +
+ +
+This is a normal-flow element. Hover the mouse pointer over the containing div (the green-bordered box surrounding this one) to see the fixed-positioned element shift. +
+ +
+ +
+ +
+This is an absolutely positioned element. Its containing block defaults to the root element but switches to its containing div when that element is transformed by hovering. +
+ +
+This is a normal-flow element. Hover the mouse pointer over the containing div (the green-bordered box surrounding this one) to see the absolutely positioned element shift. +
+ +
+ +
+This div exists to make the page tall enough to force scrolling. That's it. +
+ + + diff --git a/css3-trans-an/transform-sliders.html b/css3-trans-an/transform-sliders.html new file mode 100644 index 0000000..523b584 --- /dev/null +++ b/css3-trans-an/transform-sliders.html @@ -0,0 +1,83 @@ + + + +Rotational Sliders + + + + +

+In the following cases, the animated transforms slide around a bit with non-centered transform origins. This is because all properties are being transformed, including transform-origin. Over the second-long transition, the transform's origin point transforms from 50% 50% (the default) to the new value. That's why the centered case looks fine: it's transitioning from 50% 50% to 50% 50%. Fixes: either set the transform-origin on the unhovered state or only transition the transform property instead of all properties. (Thanks to Richard Herrera for helping me figure this out!) +

+ +
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+ + + diff --git a/css3-trans-an/transition-placement.html b/css3-trans-an/transition-placement.html new file mode 100644 index 0000000..fe8c54d --- /dev/null +++ b/css3-trans-an/transition-placement.html @@ -0,0 +1,57 @@ + + + + +Transforms, Transitions, and Containing blocks and Viewports + + + + +
+[d01] Herein lies a span. The transforms and transitions are both applied in the hover rule. So the span should transform—but will it transition? +
+ +
+[d02] Herein lies a span. The transforms are applied in the hover rule, but the transitions are applied in a different rule. So the span should transform—but will it transition? +
+ + + + diff --git a/css3-values/inherit.html b/css3-values/inherit.html new file mode 100644 index 0000000..5dfc1ac --- /dev/null +++ b/css3-values/inherit.html @@ -0,0 +1,27 @@ + + + +Inherit + + + + +
+This is a div with an id of d01. It should have a one-pixel solid purple border and its text should use Verdana or a fallback sans-serif font. + +

+This is a p with an id of p01. Its border and font family should be the same as its parent element, overriding other values defined by lower-specificity rules. +

+ +
+ +Specification + + + diff --git a/css3-values/initial.html b/css3-values/initial.html new file mode 100644 index 0000000..b4a98d8 --- /dev/null +++ b/css3-values/initial.html @@ -0,0 +1,27 @@ + + + +Initial + + + + +
+This is a div with an id of d01. Its text should be purple and use Verdana or a fallback sans-serif font. + +

+This is a p with an id of p01. Its text color and font family should be the "initial" values. It is assumed that for most browsers this is black and Times or a fallback serif. +

+ +However, since the precise meaning of "initial" is not defined in the Values module, it is hard to be sure exactly what result we should see. + +
+ +Specification + + + diff --git a/css3/ bare.html b/css3/ bare.html new file mode 100644 index 0000000..0b19010 --- /dev/null +++ b/css3/ bare.html @@ -0,0 +1,19 @@ + + + +CSS3 test: + + + + + +

+ +
+ +
+ + + diff --git a/css3/align-items.html b/css3/align-items.html new file mode 100644 index 0000000..5eed973 --- /dev/null +++ b/css3/align-items.html @@ -0,0 +1,66 @@ + + + +CSS3 test: align-items + + + + + +

http://www.w3.org/TR/css3-flexbox/#align-items

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3/align-self.html b/css3/align-self.html new file mode 100644 index 0000000..fe678c2 --- /dev/null +++ b/css3/align-self.html @@ -0,0 +1,68 @@ + + + +CSS3 test: align-self + + + + + + +

http://www.w3.org/TR/css3-flexbox/#align-self

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3/alignment-adjust.html b/css3/alignment-adjust.html new file mode 100644 index 0000000..0511042 --- /dev/null +++ b/css3/alignment-adjust.html @@ -0,0 +1,47 @@ + + + +CSS3 test: alignment-adjust + + + + + +

http://www.w3.org/TR/css3-linebox/#alignment-adjust

+ +

+Plain text. +. +. +. +. +. +. +. +. +. +. +. +. +. +. +

+ + + diff --git a/css3/alignment-baseline.html b/css3/alignment-baseline.html new file mode 100644 index 0000000..684cea4 --- /dev/null +++ b/css3/alignment-baseline.html @@ -0,0 +1,43 @@ + + + +CSS3 test: alignment-baseline + + + + + +

http://www.w3.org/TR/css3-linebox/#alignment-baseline

+ +

+Plain text. +. +. +. +. +. +. +. +. +. +. +. +. +

+ + + diff --git a/css3/appearance.html b/css3/appearance.html new file mode 100644 index 0000000..2b406a3 --- /dev/null +++ b/css3/appearance.html @@ -0,0 +1,69 @@ + + + +CSS3 test: appearance + + + + + +

http://www.w3.org/TR/css3-ui/#appearance0

+ +

span #s01

+

span #s02

+

span #s03

+

span #s04

+

span #s05

+

span #s06

+

span #s07

+

span #s08

+

span #s09

+

span #s10

+

span #s11

+

span #s12

+

span #s13

+

span #s14

+

span #s15

+

span #s16

+

span #s17

+

span #s18

+

span #s19

+

span #s20

+

span #s21

+

span #s22

+

span #s23

+

span #s24

+

span #s25

+

span #s26

+

span #s27

+ + + diff --git a/css3/background-attachment.html b/css3/background-attachment.html new file mode 100644 index 0000000..81492eb --- /dev/null +++ b/css3/background-attachment.html @@ -0,0 +1,52 @@ + + + +CSS3 test: background-attachment + + + + + +

http://www.w3.org/TR/css3-background/#the-background-attachment

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ +

Filler text follows:

+ +

+ + +Newburgh heights anne heche cleveland claritatem dolore et et sam sheppard andre norton eros adipiscing ruby dee possim typi vel investigationes. Linndale insitam clari odio lius legunt, lakeview cemetary iis facilisi enim warrensville heights, praesent vel facilisis mark mothersbaugh nulla litterarum cleveland heights. Gund arena broadview heights paul newman lobortis bernie kosar fairview park joe shuster consectetuer tempor nobis luptatum option uss cod quinta nonummy mazim. Superhost nibh lorem liber zzril mutationem non joel grey dignissim placerat fiant vero halle berry parum. Dignissim velit kenny lofton blandit, decima philip johnson in futurum dolor lebron departum arena depressum metro quatro annum returnum celebra gigantus. Nihil me qui at ullamcorper usus erat claram jim tressel humanitatis euismod est magna bratenahl vel duis. Jesse owens suscipit notare fiant ad nobis nam olmsted falls. Claritas euclid augue feugiat jim backus littera lobortis, commodo quam brecksville william g. mather iriure esse dolor. Squire’s castle harvey pekar bobby knight solon ut eorum east cleveland ghoulardi saepius wisi. +

+

+Cuyahoga river sammy kaye quod tation cuyahoga valley delenit. Iusto dolore amet ut sollemnes quarta dolore margaret hamilton luptatum tation jacobs field rocky river. Eric carmen formas duis autem quinta, nunc iusto humanitatis claritas the metroparks laoreet assum. Langston hughes molestie don king cuyahoga heights option playhouse square amet bay village. Commodo soluta nobis eros diam in augue, mazim amet parma heights claritatem in clari don shula lorem steve harvey. Investigationes quam qui id brooklyn heights burgess meredith gothica feugait saepius, parum brad daugherty elit suscipit eu. Pierogies oakwood drew carey ipsum tempor brooklyn hendrerit putamus at adipiscing euclid beach processus. Congue screamin’ jay hawkins ad demonstraverunt zzril, modo accumsan the innerbelt berea litterarum bob golic highland heights. Eum paul brown imperdiet olmsted township eleifend seven hills patricia heaton, sit bob hope chagrin falls township mutationem polka hall of fame et consuetudium dynamicus lake erie. Facilisis dolor strongsville shaker heights liber notare eum parma decima dolore lorem qui. Nibh geauga lake aliquip veniam qui qui per habent, michael symon, tincidunt parum jim brown laoreet tincidunt vulputate diam. Ipsum valley view michael ruhlman veniam congue cum quam cavaliers me dolore. +

+

+Sequitur nostrud doug dieken minim qui placerat, quis claritatem. Lectores ut est exerci lebron james chrissie hynde consequat iriure erat cedar point toni morrison putamus. Molly shannon quarta possim richmond heights facit te. Dynamicus legere tracy chapman consequat in rock & roll hall of fame university heights decima id ii. Bowling assum ea independence james a. garfield soluta seacula north olmsted est eorum littera the gold coast consequat exerci claritatem elit aliquip nulla. Anteposuerit phil donahue consequat moreland hills great lakes science center feugait carl b. stokes facer. Modo ut the arcade dolor woodmere in arsenio hall etiam iis facilisi legentis facer videntur decima henry mancini non aliquam wisi. Videntur ut quis walton hills mike golic nulla tremont eu tim conway bedford quod, imperdiet delenit praesent. Nobis in beachwood frank yankovic demonstraverunt amet qui typi nisl, gates mills nisl quod lew wasserman brook park. Legunt dead man’s curve bentleyville sed dolor claram. Maple heights volutpat esse legere nihil facit odio harlan ellison quod lectores hunting valley in doming per. North royalton lorem seacula autem garfield heights sit metroparks zoo te north randall michael stanley indians glenwillow eleifend magna sandy alomar consectetuer. +

+

+Futurum lectorum typi eric metcalf major everett insitam, est ipsum formas illum duis est mirum nunc east side sed. Illum pepper pike nostrud wes craven mentor headlands sit ozzie newsome quam, cum, nulla, george steinbrenner parum john d. rockefeller nunc. Dennis kucinich the flats ut browns feugiat doming. Vulputate gothica vel nunc legentis, typi vero processus. Roger zelazny usus south euclid aliquam lakewood qui eodem cleveland museum of art. Mark price consuetudium dolore et mayfield heights sit habent clay mathews west side peter b. lewis, accumsan nonummy dorothy dandridge ex. +

+

+Ullamcorper mirum severance hall urban meyer in, hal holbrook dolor nam bob feller velit middleburg heights sollemnes. Duis highland hills hendrerit fred willard debra winger euismod westlake emerald necklace. Omar vizquel john w. heisman enim ea eodem bedford heights ohio city ipsum sequitur molestie, minim lectorum ii lius volutpat et collision bend anteposuerit. Etiam ex orange children’s museum chagrin falls mayfield village. Municipal stadium university circle est jerry siegel jim lovell george voinovich lyndhurst, et blandit ↺ id. Putamus littera jacobs field sequitur ipsum eros jim backus, facilisi lyndhurst tincidunt. In orange magna squire’s castle minim iis warrensville heights highland heights eum sandy alomar formas broadview heights oakwood wisi lectores harlan ellison tracy chapman dynamicus. Vulputate hendrerit south euclid laoreet laoreet lectores consuetudium quod feugiat typi luptatum suscipit gund arena dolor geauga lake at. Etiam doming sed futurum margaret hamilton exerci est vero maple heights carl b. stokes william g. mather emerald necklace quarta kenny lofton ghoulardi mirum saepius pierogies. Iriure jesse owens dolore odio cuyahoga valley exerci, te dolor. Seven hills dolor enim claritas option amet me qui paul newman possim. Eric metcalf lorem pepper pike futurum doming clay mathews, consequat nunc est habent ad ex. +

+ + + diff --git a/css3/background-clip.html b/css3/background-clip.html new file mode 100644 index 0000000..dfe3050 --- /dev/null +++ b/css3/background-clip.html @@ -0,0 +1,30 @@ + + + +CSS3 test: background-clip + + + + + +

http://www.w3.org/TR/css3-background/#the-background-clip

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ + + diff --git a/css3/background-image-2.html b/css3/background-image-2.html new file mode 100644 index 0000000..8feb504 --- /dev/null +++ b/css3/background-image-2.html @@ -0,0 +1,33 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex00]
+
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3/background-image-3.html b/css3/background-image-3.html new file mode 100644 index 0000000..ef9b36f --- /dev/null +++ b/css3/background-image-3.html @@ -0,0 +1,31 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3/background-image-4.html b/css3/background-image-4.html new file mode 100644 index 0000000..ac538d5 --- /dev/null +++ b/css3/background-image-4.html @@ -0,0 +1,31 @@ + + + +CSS3 test: background-image gradients + + + + + +

http://www.w3.org/TR/css3-images/#gradients

+ +
+ +
[#ex01]
+
[#ex02]
+
[#ex03]
+
[#ex04]
+
[#ex05]
+ +
+ + + diff --git a/css3/background-image.html b/css3/background-image.html new file mode 100644 index 0000000..914534b --- /dev/null +++ b/css3/background-image.html @@ -0,0 +1,29 @@ + + + +CSS3 test: background-image + + + + + +

http://www.w3.org/TR/css3-background/#the-background-image

+ +
+ +
[#d00]
+ +
[#d01]
+ +
+ + + diff --git a/css3/background-origin.html b/css3/background-origin.html new file mode 100644 index 0000000..15d1677 --- /dev/null +++ b/css3/background-origin.html @@ -0,0 +1,30 @@ + + + +CSS3 test: background-origin + + + + + +

http://www.w3.org/TR/css3-background/#the-background-origin

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+ +
+ + + diff --git a/css3/background-position.html b/css3/background-position.html new file mode 100644 index 0000000..217e07b --- /dev/null +++ b/css3/background-position.html @@ -0,0 +1,91 @@ + + + +CSS3 test: background-position + + + + + +

http://www.w3.org/TR/css3-background/#the-background-position

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d11]
+
[#d12]
+
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+
[#d17]
+
[#d18]
+ +
[#d21]
+
[#d22]
+
[#d23]
+
[#d24]
+
[#d25]
+
[#d26]
+
[#d27]
+
[#d28]
+ +
[#d31]
+
[#d32]
+
[#d33]
+
[#d34]
+
[#d35]
+
[#d36]
+
[#d37]
+
[#d38]
+ +
+ + + diff --git a/css3/background-repeat-2.html b/css3/background-repeat-2.html new file mode 100644 index 0000000..58b1879 --- /dev/null +++ b/css3/background-repeat-2.html @@ -0,0 +1,58 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
+ + + diff --git a/css3/background-repeat-3.html b/css3/background-repeat-3.html new file mode 100644 index 0000000..5c15f45 --- /dev/null +++ b/css3/background-repeat-3.html @@ -0,0 +1,57 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[.s01 .tl]
+
[.s01]
+
[.s02 .tl]
+
[.s02]
+
[.s03 .tl]
+
[.s03]
+
[.s04 .tl]
+
[.s04]
+
[.s05 .tl]
+
[.s05]
+
[.s06 .tl]
+
[.s06]
+
[.s07 .tl]
+
[.s07]
+
[.s08 .tl]
+
[.s08]
+
[.s09 .tl]
+
[.s09]
+ +
+ + + diff --git a/css3/background-repeat.html b/css3/background-repeat.html new file mode 100644 index 0000000..a3da984 --- /dev/null +++ b/css3/background-repeat.html @@ -0,0 +1,78 @@ + + + +CSS3 test: background-repeat + + + + + +

http://www.w3.org/TR/css3-background/#the-background-repeat

+ +
+ +
[#d00]
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
[#d17]
+
[#d18]
+
[#d19]
+
[#d20]
+ +
[#d21]
+
[#d22]
+
[#d23]
+
[#d24]
+ +
+ + + diff --git a/css3/background-size.html b/css3/background-size.html new file mode 100644 index 0000000..095af30 --- /dev/null +++ b/css3/background-size.html @@ -0,0 +1,59 @@ + + + +CSS3 test: background-size + + + + + +

http://www.w3.org/TR/css3-background/#the-background-size

+ +
+ +
[#d01]
+
[#d02]
+
[#d03]
+
[#d04]
+ +
[#d05]
+
[#d06]
+
[#d07]
+
[#d08]
+ +
[#d09]
+
[#d10]
+
[#d11]
+
[#d12]
+ +
[#d13]
+
[#d14]
+
[#d15]
+
[#d16]
+ +
+ + + diff --git a/css3/baseline-shift.html b/css3/baseline-shift.html new file mode 100644 index 0000000..36b535c --- /dev/null +++ b/css3/baseline-shift.html @@ -0,0 +1,29 @@ + + + +CSS3 test: baseline-shift + + + + + +

http://www.w3.org/TR/css3-linebox/#baseline-shift-prop

+ +

+Plain text. +. +. +. +. +. +

+ + + diff --git a/css3/bookmark-label.html b/css3/bookmark-label.html new file mode 100644 index 0000000..4dd7d0b --- /dev/null +++ b/css3/bookmark-label.html @@ -0,0 +1,30 @@ + + + +CSS3 test: bookmark-label + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-label

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3/bookmark-level.html b/css3/bookmark-level.html new file mode 100644 index 0000000..70223af --- /dev/null +++ b/css3/bookmark-level.html @@ -0,0 +1,31 @@ + + + +CSS3 test: bookmark-level + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-level

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3/bookmark-state.html b/css3/bookmark-state.html new file mode 100644 index 0000000..87f26af --- /dev/null +++ b/css3/bookmark-state.html @@ -0,0 +1,29 @@ + + + +CSS3 test: bookmark-state + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-state

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3/bookmark-target.html b/css3/bookmark-target.html new file mode 100644 index 0000000..0d53827 --- /dev/null +++ b/css3/bookmark-target.html @@ -0,0 +1,30 @@ + + + +CSS3 test: bookmark-target + + + + + +

http://www.w3.org/TR/css3-gcpm/#bookmark-target

+ +

Heading-1 [#h1]

+

Heading-2 #1 [#h201]

+

Heading-3 #1 [#h301]

+

Heading-3 #2 [#h302]

+

Heading-3 #3 [#h303]

+

Paragraph #1 [#p01]

+

Heading-2 #2 [#h202]

+

Heading-3 #4 [#h304]

+

Heading-3 #5 [#h305]

+

Heading-3 #6 [#h306]

+

Paragraph #2 [#p02]

+ + + + diff --git a/css3/border-image.html b/css3/border-image.html new file mode 100644 index 0000000..d18a93f --- /dev/null +++ b/css3/border-image.html @@ -0,0 +1,36 @@ + + + +CSS3 test: border-image + + + + + +

http://www.w3.org/TR/css3-background/#the-border-image

+ +
+ +

+[#p01] This is a paragraph that should have an image border using the following image: . +

+

+[#p02] This is a paragraph that should have an image border using the following image: . +

+

+[#p03] This is a paragraph that should have an image border using the following image: . +

+

+[#p04] This is a paragraph that should have an image border using the following image: . +

+ +
+ + + diff --git a/css3/border-radius.html b/css3/border-radius.html new file mode 100644 index 0000000..a7cf43e --- /dev/null +++ b/css3/border-radius.html @@ -0,0 +1,23 @@ + + + +CSS3 test: border-radius + + + + + +

http://www.w3.org/TR/css3-background/#the-border-radius

+ +
+ +

[p01] A paragraph.

+

[p02] Another paragraph.

+ +
+ + + diff --git a/css3/box-decoration-break.html b/css3/box-decoration-break.html new file mode 100644 index 0000000..4e2a8a4 --- /dev/null +++ b/css3/box-decoration-break.html @@ -0,0 +1,25 @@ + + + +CSS3 test: box-decoration-break + + + + + +

http://www.w3.org/TR/css3-background/#the-box-decoration-break

+ +

+[#p01] This is a paragraph. It contains within it a span element. This inline element has been decorated and backgrounded in order to test the outcome of box-decoration-break. There should be two different effects between the first test and the second. Let us hope it is so. +

+

+[#p02] This is a paragraph. It contains within it a span element. This inline element has been decorated and backgrounded in order to test the outcome of box-decoration-break. There should be two different effects between the first test and the second. Let us hope it is so. +

+ + + diff --git a/css3/box-shadow.html b/css3/box-shadow.html new file mode 100644 index 0000000..cc85070 --- /dev/null +++ b/css3/box-shadow.html @@ -0,0 +1,52 @@ + + + +CSS3 test: box-shadow + + + + + +

http://www.w3.org/TR/css3-background/#the-box-shadow

+ +
+ +

+[#p01] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p02] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p03] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p04] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p05] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p06] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p07] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+

+[#p08] This is a paragraph. Its box has been shadowed. Will the shadow be visible in many browsers? Only The Shadow knows! +

+ +
+ + + diff --git a/css3/box-sizing.html b/css3/box-sizing.html new file mode 100644 index 0000000..884ac4a --- /dev/null +++ b/css3/box-sizing.html @@ -0,0 +1,28 @@ + + + +CSS3 test: box-sizing + + + + + +

http://www.w3.org/TR/css3-background/#the-box-sizing

+ +
+ +

+[#p01] This is a paragraph. +

+

+[#p02] This is a paragraph. +

+ +
+ + + diff --git a/css3/c/base.css b/css3/c/base.css new file mode 100644 index 0000000..b1c4ebd --- /dev/null +++ b/css3/c/base.css @@ -0,0 +1,32 @@ +head {display: block;} +style#tests {display: block; + max-height: 20.33em; + overflow: auto; + white-space: pre; + font: small/1 monospace, serif; + padding: 0 1em 0.75em; + border-bottom: 3px double #999; + background: #DDD; color: #333;} +style[contenteditable]#tests {background: #DED;} +body {margin-top: 0; padding: 0 0 2em;} +p#specref {margin: 0 -8px; padding: 0.5em; + background: #DDD; + border-bottom: 1px solid; + font-style: italic;} +ul#nav {position: fixed; bottom: 0; right: 0; left: 0; + text-align: center; + padding: 0.25em 1em 0.33em; margin: 0; + border-top: 3px double #888; + background: #E8E8E8;} +ul#nav li {display: inline; list-style: none; margin: 0 0.75em;} +ul#nav a:hover {color: rgb(216,0,0);} +ul#nav #i {position: absolute; right: 0; top: 0.33em;} +ul#nav #r {position: absolute; left: 0; top: 0.33em;} +vhr.clr {clear: both; visibility: hidden;} + +.warning {color: maroon; background: #FFC;} +.note {color: #222; background: #EEE; font-style: italic;} +.warning, .note {padding: 0.42em 0.67em 0.23em; margin: 0.5em -0.5em;} +.warning + .note {margin-top: -0.25em;} + +.arena {margin-top: 1.5em;} \ No newline at end of file diff --git a/css3/caption-side.html b/css3/caption-side.html new file mode 100644 index 0000000..2901b8c --- /dev/null +++ b/css3/caption-side.html @@ -0,0 +1,62 @@ + + + +CSS3 test: caption-side + + + + + +

http://www.w3.org/TR/css3-background/#the-caption-side

+ +
+ + + + + + + + + + + + + + + + + + + + +
[#c01] Caption!
HeaderDataDataDataDataData
HeaderDataDataDataDataData
+ + + + + + + + + + + + + + + + + + + +
[#c02] Caption!
HeaderDataDataDataDataData
HeaderDataDataDataDataData
+ +
+ + + diff --git a/css3/column-count.html b/css3/column-count.html new file mode 100644 index 0000000..e1a188a --- /dev/null +++ b/css3/column-count.html @@ -0,0 +1,73 @@ + + + +CSS3 test: column-count + + + + + +

http://www.w3.org/TR/css3-multicol/#column-count

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Three columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-gap.html b/css3/column-gap.html new file mode 100644 index 0000000..fd69fc2 --- /dev/null +++ b/css3/column-gap.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-gap + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-gap

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-rule-color.html b/css3/column-rule-color.html new file mode 100644 index 0000000..281e3d6 --- /dev/null +++ b/css3/column-rule-color.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-color + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-color

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-rule-style.html b/css3/column-rule-style.html new file mode 100644 index 0000000..48884e1 --- /dev/null +++ b/css3/column-rule-style.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-style + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-style

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-rule-width.html b/css3/column-rule-width.html new file mode 100644 index 0000000..1c23de2 --- /dev/null +++ b/css3/column-rule-width.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule-width + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule-width

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-rule.html b/css3/column-rule.html new file mode 100644 index 0000000..74341ac --- /dev/null +++ b/css3/column-rule.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-rule + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-rule

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-span.html b/css3/column-span.html new file mode 100644 index 0000000..16610db --- /dev/null +++ b/css3/column-span.html @@ -0,0 +1,74 @@ + + + +CSS3 test: column-span + + + + + + +

http://www.w3.org/TR/css3-multicol/#column-span

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/column-width.html b/css3/column-width.html new file mode 100644 index 0000000..22849dd --- /dev/null +++ b/css3/column-width.html @@ -0,0 +1,73 @@ + + + +CSS3 test: column-width + + + + + +

http://www.w3.org/TR/css3-multicol/#column-width

+ +
+ +
+

"15em" columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

"25em" columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/columns.html b/css3/columns.html new file mode 100644 index 0000000..61ff8f5 --- /dev/null +++ b/css3/columns.html @@ -0,0 +1,73 @@ + + + +CSS3 test: columns + + + + + +

http://www.w3.org/TR/css3-multicol/#columns

+ +
+ +
+

Two columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+
+ +
+

Three columns

+

+At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

+

+Quick: do you have a impactful scheme for dealing with emerging C2C2C B2B2C B2B Total Quality Control? +

+

+ConHugeCo practically invented the term "mindshare". Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is! A company that can seize defiantly will (at some undefined point in the future) be able to enable faithfully. Without sufficient returns-on-investment, communities are forced to become 60/24/7/365. If you benchmark globally, you may have to integrate virally. +

+

+Is it more important for something to be plug-and-play or to be user-defined? +

+

+We here at ConHugeCo think we know that it is better to aggregate robustly than to implement vertically. The metrics for C2C management management are more well-understood if they are not ubiquitous. It seems unclear, but it's realistic! The aptitude to morph globally leads to the capability to empower strategically. The biometrics factor can be summed up in one word: enterprise. Imagine a combination of ActionScript and PHP. We believe we know that it is better to visualize perfectly than to target virtually. What does the term "compliance" really mean? The power to architect interactively leads to the power to exploit intuitively. Our technology takes the best aspects of XHTML and SMIL. Quick: do you have a revolutionary plan of action for monitoring new global, integrated synergies? Our functionality is unmatched in the industry, but our clicks-and-mortar e-commerce and newbie-proof configuration is frequently considered a remarkable achievement. +

+

+Our blog-based feature set is unparalleled, but our long-term plug-and-play, virtual, proactive, visionary R&D and newbie-proof operation is frequently considered an amazing achievement. +

+

+We here at ConHugeCo understand that it is better to streamline wirelessly than to strategize strategically. We will unleash the capability of platforms to empower. We will upgrade the term "social-network-based". Our technology takes the best aspects of XSL and SVG. Without content, you will lack methodologies. We apply the proverb "The early bird catches the worm" not only to our accounting but our ability to incentivize. Without well-planned niches, TQC metrics are forced to become C2C2C. It may seem confounding, but it's accurate! Without appropriate methodologies, communities are forced to become social-network-based. Think mega-viral. Think micro-24/7/365. Think cutting-edge. Think blog-based. Think end-to-end, ubiquitous. But don't think all three at the same time. Without user communities, you will lack C2B2B transparent, dot-com research and development. +

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/content.html b/css3/content.html new file mode 100644 index 0000000..c26bf6b --- /dev/null +++ b/css3/content.html @@ -0,0 +1,27 @@ + + + +CSS3 test: content + + + + + +

http://www.w3.org/TR/css3-content/#content

+ +
+ +

+This is a paragraph containing a span element within its content. +

+

+This is a paragraph containing a span element within its content. +

+ +
+ + + diff --git a/css3/core.php b/css3/core.php new file mode 100644 index 0000000..39ce10a --- /dev/null +++ b/css3/core.php @@ -0,0 +1,54 @@ + \ No newline at end of file diff --git a/css3/crop.html b/css3/crop.html new file mode 100644 index 0000000..4a2b33d --- /dev/null +++ b/css3/crop.html @@ -0,0 +1,22 @@ + + + +CSS3 test: crop + + + + + +

http://www.w3.org/TR/css3-content/#the-crop

+ +
+

This paragraph contains an uncropped image.

+

This paragraph contains an image cropped to only show "ONE" with the surrounding white area and a pixel of blue to each side byeond that.

+

This paragraph contains an image cropped to only show "ONE" with the surrounding white area and a pixel of blue to each side byeond that.

+
+ + + diff --git a/css3/cursor.html b/css3/cursor.html new file mode 100644 index 0000000..65d4947 --- /dev/null +++ b/css3/cursor.html @@ -0,0 +1,94 @@ + + + +CSS3 test: cursor + + + + + +

http://www.w3.org/TR/css3-ui/#cursor0

+ +
+ +

[#p01]

+

[#p02]

+

[#p03]

+

[#p04]

+

[#p05]

+

[#p06]

+

[#p07]

+

[#p08]

+

[#p09]

+

[#p10]

+

[#p11]

+

[#p12]

+

[#p13]

+

[#p14]

+

[#p15]

+

[#p16]

+

[#p17]

+

[#p18]

+

[#p19]

+

[#p20]

+

[#p21]

+

[#p22]

+

[#p23]

+

[#p24]

+

[#p25]

+

[#p26]

+

[#p27]

+

[#p28]

+

[#p29]

+

[#p30]

+

[#p31]

+

[#p32]

+

[#p33]

+

[#p34]

+

[#p35]

+ +
+ +

-

+ + + diff --git a/css3/f/Anivers-Regular.otf b/css3/f/Anivers-Regular.otf new file mode 100644 index 0000000..0b9adbb Binary files /dev/null and b/css3/f/Anivers-Regular.otf differ diff --git a/css3/f/Diavlo_MEDIUM_II_37.otf b/css3/f/Diavlo_MEDIUM_II_37.otf new file mode 100644 index 0000000..1cfea27 Binary files /dev/null and b/css3/f/Diavlo_MEDIUM_II_37.otf differ diff --git a/css3/f/Futura.ttc b/css3/f/Futura.ttc new file mode 100644 index 0000000..06e229b Binary files /dev/null and b/css3/f/Futura.ttc differ diff --git a/css3/f/MyriadPro-Bold.otf b/css3/f/MyriadPro-Bold.otf new file mode 100644 index 0000000..a4c78b0 Binary files /dev/null and b/css3/f/MyriadPro-Bold.otf differ diff --git a/css3/f/MyriadPro-Cond.otf b/css3/f/MyriadPro-Cond.otf new file mode 100644 index 0000000..c85dd1b Binary files /dev/null and b/css3/f/MyriadPro-Cond.otf differ diff --git a/css3/f/MyriadPro-Regular.otf b/css3/f/MyriadPro-Regular.otf new file mode 100644 index 0000000..57a953b Binary files /dev/null and b/css3/f/MyriadPro-Regular.otf differ diff --git a/css3/f/Nadyezhda SL One.ttf b/css3/f/Nadyezhda SL One.ttf new file mode 100644 index 0000000..6ea7c9b Binary files /dev/null and b/css3/f/Nadyezhda SL One.ttf differ diff --git a/css3/f/Skia.ttf b/css3/f/Skia.ttf new file mode 100644 index 0000000..be29869 Binary files /dev/null and b/css3/f/Skia.ttf differ diff --git a/css3/f/SourceSansPro-Bold.ttf b/css3/f/SourceSansPro-Bold.ttf new file mode 100644 index 0000000..b8d40c0 Binary files /dev/null and b/css3/f/SourceSansPro-Bold.ttf differ diff --git a/css3/f/SourceSansPro-Regular.otf b/css3/f/SourceSansPro-Regular.otf new file mode 100644 index 0000000..b9c6c5d Binary files /dev/null and b/css3/f/SourceSansPro-Regular.otf differ diff --git a/css3/f/SwitzeraADF-Bold.otf b/css3/f/SwitzeraADF-Bold.otf new file mode 100644 index 0000000..ace7802 Binary files /dev/null and b/css3/f/SwitzeraADF-Bold.otf differ diff --git a/css3/f/SwitzeraADF-BoldExt.otf b/css3/f/SwitzeraADF-BoldExt.otf new file mode 100644 index 0000000..699b15a Binary files /dev/null and b/css3/f/SwitzeraADF-BoldExt.otf differ diff --git a/css3/f/SwitzeraADF-BoldItalic.otf b/css3/f/SwitzeraADF-BoldItalic.otf new file mode 100644 index 0000000..2c75d37 Binary files /dev/null and b/css3/f/SwitzeraADF-BoldItalic.otf differ diff --git a/css3/f/SwitzeraADF-Cond.otf b/css3/f/SwitzeraADF-Cond.otf new file mode 100644 index 0000000..8aa25e5 Binary files /dev/null and b/css3/f/SwitzeraADF-Cond.otf differ diff --git a/css3/f/SwitzeraADF-Ext.otf b/css3/f/SwitzeraADF-Ext.otf new file mode 100644 index 0000000..366eddc Binary files /dev/null and b/css3/f/SwitzeraADF-Ext.otf differ diff --git a/css3/f/SwitzeraADF-Italic.otf b/css3/f/SwitzeraADF-Italic.otf new file mode 100644 index 0000000..2f536e0 Binary files /dev/null and b/css3/f/SwitzeraADF-Italic.otf differ diff --git a/css3/f/SwitzeraADF-LightCond.otf b/css3/f/SwitzeraADF-LightCond.otf new file mode 100644 index 0000000..8c69a3f Binary files /dev/null and b/css3/f/SwitzeraADF-LightCond.otf differ diff --git a/css3/f/SwitzeraADF-Regular.eot b/css3/f/SwitzeraADF-Regular.eot new file mode 100644 index 0000000..dd4a6ad Binary files /dev/null and b/css3/f/SwitzeraADF-Regular.eot differ diff --git a/css3/f/SwitzeraADF-Regular.otf b/css3/f/SwitzeraADF-Regular.otf new file mode 100644 index 0000000..33c34e5 Binary files /dev/null and b/css3/f/SwitzeraADF-Regular.otf differ diff --git a/css3/f/SwitzeraADF-Regular.svg b/css3/f/SwitzeraADF-Regular.svg new file mode 100644 index 0000000..522067c --- /dev/null +++ b/css3/f/SwitzeraADF-Regular.svg @@ -0,0 +1,245 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/css3/f/SwitzeraADF-Regular.ttf b/css3/f/SwitzeraADF-Regular.ttf new file mode 100644 index 0000000..3612a3c Binary files /dev/null and b/css3/f/SwitzeraADF-Regular.ttf differ diff --git a/css3/f/SwitzeraADF-Regular.woff b/css3/f/SwitzeraADF-Regular.woff new file mode 100644 index 0000000..724aad0 Binary files /dev/null and b/css3/f/SwitzeraADF-Regular.woff differ diff --git a/css3/f/Ubuntu-R.ttf b/css3/f/Ubuntu-R.ttf new file mode 100644 index 0000000..45a038b Binary files /dev/null and b/css3/f/Ubuntu-R.ttf differ diff --git a/css3/flex-direction.html b/css3/flex-direction.html new file mode 100644 index 0000000..ecfc29c --- /dev/null +++ b/css3/flex-direction.html @@ -0,0 +1,43 @@ + + + +CSS3 test: flex-wrap + + + + + +

http://www.w3.org/TR/css3-flexbox/#flex-direction-property

+ +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
+ +
+ + + diff --git a/css3/flex-wrap.html b/css3/flex-wrap.html new file mode 100644 index 0000000..4f21527 --- /dev/null +++ b/css3/flex-wrap.html @@ -0,0 +1,64 @@ + + + +CSS3 test: flex-wrap + + + + + + +

http://www.w3.org/TR/css3-flexbox/#flex-wrap-property

+ +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
  9. +
  10. +
+ +
    +
  1. +
  2. +
  3. +
  4. +
  5. +
  6. +
  7. +
  8. +
  9. +
  10. +
  11. +
  12. +
+ +
+ + + diff --git a/css3/float-offset.html b/css3/float-offset.html new file mode 100644 index 0000000..00f77eb --- /dev/null +++ b/css3/float-offset.html @@ -0,0 +1,27 @@ + + + +CSS3 test: float-offset + + + + + +

http://www.w3.org/TR/css3-gcpm/#float-offset

+ +
+ +

[#p01] A paragraph containing a floated image.

+

[#p02] A paragraph containing a floated image.

+

[#p03] A paragraph containing a floated image.

+ +
+ + + diff --git a/css3/font-face-2.html b/css3/font-face-2.html new file mode 100644 index 0000000..4dd73a4 --- /dev/null +++ b/css3/font-face-2.html @@ -0,0 +1,37 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph containing text inside a span as well as text without.

+

[#p02] A paragraph containing text inside a span as well as text without.

+

[#p03] A paragraph containing text inside a span as well as text without.

+ +
+ + + diff --git a/css3/font-face-3.html b/css3/font-face-3.html new file mode 100644 index 0000000..71b278c --- /dev/null +++ b/css3/font-face-3.html @@ -0,0 +1,52 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph of text.

+

[#p02] A paragraph of text.

+

[#p03] A paragraph of text.

+

[#p04] A paragraph of text.

+

[#p05] A paragraph of text.

+ +
+ + + diff --git a/css3/font-face.html b/css3/font-face.html new file mode 100644 index 0000000..1b97983 --- /dev/null +++ b/css3/font-face.html @@ -0,0 +1,77 @@ + + + +CSS3 test: @font-face + + + + + + +

http://w3.org/TR/css3-fonts/

+ +
+ +

[#p01] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p02] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p03] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+

[#p04] A paragraph containing descriptor-styled text and face-styled text and element-styled text.

+ +
+ + + diff --git a/css3/font-feature-settings-2.html b/css3/font-feature-settings-2.html new file mode 100644 index 0000000..c761ad1 --- /dev/null +++ b/css3/font-feature-settings-2.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-feature-settings + + + + + + +

+ +
+ +

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+ +
+ + + diff --git a/css3/font-feature-settings.html b/css3/font-feature-settings.html new file mode 100644 index 0000000..bd1ac9c --- /dev/null +++ b/css3/font-feature-settings.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-feature-settings + + + + + + +

+ +
+ +

+aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

+ +
+ + + diff --git a/css3/font-kerning.html b/css3/font-kerning.html new file mode 100644 index 0000000..7275694 --- /dev/null +++ b/css3/font-kerning.html @@ -0,0 +1,43 @@ + + + +CSS3 test: font-kerning + + + + + + +

http://w3.org/TR/css3-fonts/#font-kerning-prop

+ +
+ +

[.t1.c1] A paragraph of text.

+

[.t1.c2] A paragraph of text.

+

[.t1.c3] A paragraph of text.

+ +

[.t2.c1] A paragraph of text.

+

[.t2.c2] A paragraph of text.

+

[.t2.c3] A paragraph of text.

+ +
+ + + diff --git a/css3/font-size-adjust.html b/css3/font-size-adjust.html new file mode 100644 index 0000000..4c673d5 --- /dev/null +++ b/css3/font-size-adjust.html @@ -0,0 +1,25 @@ + + + +CSS3 test: font-size-adjust + + + + + +

http://www.w3.org/TR/css3-fonts/#font-size-adjust

+ +

NOTE: if the two characters following are the same size, the user agent has failed this test. A passing result shows the second character almost twice the size of the first—specifically [100px × (1 ÷ 0.52) = 192.3px].

+ +
+ +

bb

+ +
+ + + diff --git a/css3/font-stretch.html b/css3/font-stretch.html new file mode 100644 index 0000000..7bf5894 --- /dev/null +++ b/css3/font-stretch.html @@ -0,0 +1,50 @@ + + + +CSS3 test: font-stretch + + + + + + +

http://w3.org/TR/css3-fonts/#font-stretch-prop

+ +

+WARNING: this test will only pass if the font family in use has width-variant faces. Therefore, a user agent can support font-stretch and still appear to fail this test. +

+

NOTE: this test uses faces of SwitzeraADF, assigning various individual faces to various stretch levels (and cheating by using a light condensed face to substitue for “ultra-condensed” and a bold extended face for “ultra-expanded”). If the following paragraphs are in a serif font, then the font has failed to load. If they are sans-serif, then the font has most likely loaded and the test should be valid.

+ +
+ +

[#p01] A paragraph of text.

+

[#p02] A paragraph of text.

+

[#p03] A paragraph of text.

+

[#p04] A paragraph of text.

+

[#p05] A paragraph of text.

+

[#p06] A paragraph of text.

+

[#p07] A paragraph of text.

+

[#p08] A paragraph of text.

+

[#p09] A paragraph of text.

+ +
+ + + diff --git a/css3/font-style.html b/css3/font-style.html new file mode 100644 index 0000000..941ddd1 --- /dev/null +++ b/css3/font-style.html @@ -0,0 +1,38 @@ + + + +CSS3 test: font-style + + + + + +

http://w3.org/TR/css3-fonts/#font-style

+ +
+ +

[#p00] A paragraph of text with some italic text and then some oblique text.

+

[#p01] A paragraph of text with some italic text and then some oblique text.

+

[#p02] A paragraph of text with some italic text and then some oblique text.

+

[#p03] A paragraph of text with some italic text and then some oblique text.

+

[#p04] A paragraph of text with some italic text and then some oblique text.

+

[#p05] A paragraph of text with some italic text and then some oblique text.

+

[#p06] A paragraph of text with some italic text and then some oblique text.

+

[#p07] A paragraph of text with some italic text and then some oblique text.

+ +
+ + + diff --git a/css3/font-synthesis.html b/css3/font-synthesis.html new file mode 100644 index 0000000..af90587 --- /dev/null +++ b/css3/font-synthesis.html @@ -0,0 +1,40 @@ + + + +CSS3 test: font-synthesis + + + + + +

http://w3.org/TR/css3-fonts/#font-synthesis

+ +

WARNING: this test can only be passed if the font family in use lacks bold and italic faces. Therefore, a user agent can support font-synthesis and still appear to fail this test.

+

NOTE: this test uses the font face Myriad Pro Regular. This single face was specifically selected because it lacks both bold and italic faces. If the following paragraphs are in a serif font, then the font has failed to load. If they are sans-serif, then the font has most likely loaded and the test should be valid.

+ +
+

[#p01] This is a paragraph with bold and italic children. There should be neither bold nor italic.

+

[#p02] This is a paragraph with bold and italic children. There should be bold, but not italic.

+

[#p03] This is a paragraph with bold and italic children. There should be italic, but not bold.

+

[#p04] This is a paragraph with bold and italic children. There should be both bold and italic.

+ +
+ + + diff --git a/css3/font-variant-ligatures.html b/css3/font-variant-ligatures.html new file mode 100644 index 0000000..89d25a5 --- /dev/null +++ b/css3/font-variant-ligatures.html @@ -0,0 +1,110 @@ + + + +CSS3 test: font-variant-ligatures + + + + + + +

http://www.w3.org/TR/css3-fonts/.font-variant-ligatures-prop

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row ID.on.off
[.t01]if fi ff tf ft jf fjif fi ff tf ft jf fj
[.t02]most Jesuit effectsmost Jesuit effects
[.t03]most Jesuit effectsmost Jesuit effects
[.t04]this & thatthis & that
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row ID.on.off
[.t01]ao bxao bx
[.t02]avav
[.t03]bjbj
[.t04]alal
+ +
+aa ab ac ad ae af ag ah ai aj ak al am 
+an ao ap aq ar as at au av aw ax ay az
+ba bb bc bd be bf bg bh bi bj bk bl bm 
+bn bo bp bq br bs bt bu bv bw bx by bz
+ca cb cc cd ce cf cg ch ci cj ck cl cm 
+cn co cp cq cr cs ct cu cv cw cx cy cz
+da db dc dd de df dg dh di dj dk dl dm 
+dn do dp dq dr ds dt du dv dw dx dy dz
+ea eb ec ed ee ef eg eh ei ej ek el em 
+en eo ep eq er es et eu ev ew ex ey ez
+
+ +
+ + + diff --git a/css3/font-variant-numeric.html b/css3/font-variant-numeric.html new file mode 100644 index 0000000..556db1f --- /dev/null +++ b/css3/font-variant-numeric.html @@ -0,0 +1,117 @@ + + + +CSS3 test: font-variant-numeric + + + + + + +

http://www.w3.org/TR/css3-fonts/.font-variant-ligatures-prop

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row IDraw.st1.st2
[.t01]1,234
5,678
9,012
1,234
5,678
9,012
1,234
5,678
9,012
[.t02]1,234
5,678
9,012
1,234
5,678
9,012
1,234
5,678
9,012
[.t03]33 1/333 1/333 1/3
[.t04]900090009000
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Row IDraw.st1.st2
[.t01]bz clbzcl
[.t02]cr emcrem
[.t03]bc aebcae
[.t04]cn ezcnez
+ +
+aa ab ac ad ae af ag ah ai aj ak al am 
+an ao ap aq ar as at au av aw ax ay az
+ba bb bc bd be bf bg bh bi bj bk bl bm 
+bn bo bp bq br bs bt bu bv bw bx by bz
+ca cb cc cd ce cf cg ch ci cj ck cl cm 
+cn co cp cq cr cs ct cu cv cw cx cy cz
+da db dc dd de df dg dh di dj dk dl dm 
+dn do dp dq dr ds dt du dv dw dx dy dz
+ea eb ec ed ee ef eg eh ei ej ek el em 
+en eo ep eq er es et eu ev ew ex ey ez
+
+ +
+ + + diff --git a/css3/font-weight.html b/css3/font-weight.html new file mode 100644 index 0000000..de3dab5 --- /dev/null +++ b/css3/font-weight.html @@ -0,0 +1,125 @@ + + + +CSS3 test: font-style + + + + + +

http://w3.org/TR/css3-fonts/#font-style

+ +
+ +

[#p00] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p01] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p02] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p03] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p04] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p05] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p06] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+

[#p07] +100 +200 +300 +400 +500 +600 +700 +800 +900 +

+ +
+ + + diff --git a/css3/hanging-punctuation.html b/css3/hanging-punctuation.html new file mode 100644 index 0000000..1b42099 --- /dev/null +++ b/css3/hanging-punctuation.html @@ -0,0 +1,22 @@ + + + +CSS3 test: hanging-punctuation + + + + + +

http://www.w3.org/TR/css3-text/#hanging-punctuation

+ +
+

“This is a paragraph ([#p01]) with a leading quotation mark. It should hang off the beginning of the first line of text such that the non-quotation characters line up with each other vertically.”

+

“This is a paragraph ([#p02]) with a trailing quotation mark. It should hang off the end of the last line in order to avoid forced line-wrapping.”

+
+ + + diff --git a/css3/hyphenate-character.html b/css3/hyphenate-character.html new file mode 100644 index 0000000..910a876 --- /dev/null +++ b/css3/hyphenate-character.html @@ -0,0 +1,27 @@ + + + +CSS3 test: hyphenate-character + + + + + +

http://www.w3.org/TR/css3-gcpm/#hyphenate-character

+ +
+

It is most likely necessary to resize the viewport to properly evaluate this test.

+ +

[#p01] This is a paragraph with embedded hyphenation hints but no hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p02] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Hyphens should use this character: ℒ. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+ + + diff --git a/css3/hyphens.html b/css3/hyphens.html new file mode 100644 index 0000000..e529206 --- /dev/null +++ b/css3/hyphens.html @@ -0,0 +1,34 @@ + + + +CSS3 test: hyphens + + + + + +

http://www.w3.org/TR/css3-gcpm/#hyphens

+ +
+

It is most likely necessary to resize the viewport to properly evaluate this test.

+ +

[#p01] This is a paragraph with no embedded hyphenation hints and no hyphen-related CSS applied. Corporate gibberish follows. Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness!

+ +

[#p02] This is a paragraph with embedded hyphenation hints but no hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p03] This is a paragraph with no embedded hyphenation hints but hyphen-related CSS applied. Corporate gibberish follows. Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness!

+ +

[#p04] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness!

+ +

[#p05] This is a paragraph with embedded hyphenation hints and hyphen-related CSS applied. Corp­orate gibb­erish fol­lows. Think vision­ary. If you gener­ate pro­actively, you may have to e-enable inter­actively. We apply the pro­verb "Grass doesn't grow on a race­track" not only to our re-pur­posing but our pow­er to mat­rix. If all of this comes off as dumb­founding to you, that's be­cause it is! Our feat­ure set is un­paral­leled in the in­dus­try, but our reality-based sys­tems and sim­ple use is usu­ally con­sid­ered a re­mark­able achieve­ment. The power to brand ro­bustly leads to the apti­tude to em­brace seam­lessly. What do we stream­line? Any­thing and every­thing, re­gard­less of re­con­diteness! (NOTE: in this case, the CSS requires hyphenation hints to be ignored.)

+
+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+ + + diff --git a/css3/i/Globe.ani b/css3/i/Globe.ani new file mode 100755 index 0000000..3d43df8 Binary files /dev/null and b/css3/i/Globe.ani differ diff --git a/css3/i/blob-green.gif b/css3/i/blob-green.gif new file mode 100644 index 0000000..843aff1 Binary files /dev/null and b/css3/i/blob-green.gif differ diff --git a/css3/i/box-red.gif b/css3/i/box-red.gif new file mode 100644 index 0000000..9c89924 Binary files /dev/null and b/css3/i/box-red.gif differ diff --git a/css3/i/dot-red.gif b/css3/i/dot-red.gif new file mode 100644 index 0000000..b3e84a9 Binary files /dev/null and b/css3/i/dot-red.gif differ diff --git a/css3/i/grid-100.png b/css3/i/grid-100.png new file mode 100644 index 0000000..23d05e8 Binary files /dev/null and b/css3/i/grid-100.png differ diff --git a/css3/i/grid-400.png b/css3/i/grid-400.png new file mode 100644 index 0000000..b7c2a0f Binary files /dev/null and b/css3/i/grid-400.png differ diff --git a/css3/i/hatchgrid-100.png b/css3/i/hatchgrid-100.png new file mode 100644 index 0000000..c28d229 Binary files /dev/null and b/css3/i/hatchgrid-100.png differ diff --git a/css3/i/hatchgrid-100.psd b/css3/i/hatchgrid-100.psd new file mode 100644 index 0000000..9375ada Binary files /dev/null and b/css3/i/hatchgrid-100.psd differ diff --git a/css3/i/hatchgrid-150.png b/css3/i/hatchgrid-150.png new file mode 100644 index 0000000..168b7e0 Binary files /dev/null and b/css3/i/hatchgrid-150.png differ diff --git a/css3/i/hatchgrid-150.psd b/css3/i/hatchgrid-150.psd new file mode 100644 index 0000000..5d298a8 Binary files /dev/null and b/css3/i/hatchgrid-150.psd differ diff --git a/css3/i/hatchgrid.png b/css3/i/hatchgrid.png new file mode 100644 index 0000000..1c30361 Binary files /dev/null and b/css3/i/hatchgrid.png differ diff --git a/css3/i/hatchgrid.psd b/css3/i/hatchgrid.psd new file mode 100644 index 0000000..740d228 Binary files /dev/null and b/css3/i/hatchgrid.psd differ diff --git a/css3/i/one-two.gif b/css3/i/one-two.gif new file mode 100644 index 0000000..a5bbc39 Binary files /dev/null and b/css3/i/one-two.gif differ diff --git a/css3/i/target.gif b/css3/i/target.gif new file mode 100755 index 0000000..fa41622 Binary files /dev/null and b/css3/i/target.gif differ diff --git a/css3/i/target.png b/css3/i/target.png new file mode 100644 index 0000000..404c979 Binary files /dev/null and b/css3/i/target.png differ diff --git a/css3/icon.html b/css3/icon.html new file mode 100644 index 0000000..10aab8d --- /dev/null +++ b/css3/icon.html @@ -0,0 +1,28 @@ + + + +CSS3 test: icon + + + + + +

http://www.w3.org/TR/css3-ui/#icon

+ +
+ +

+[#p01] Consider an image () and an icon (). Then replace the image with the icon: . +

+

+[#p02] Consider a span. Then replace one with an icon: am I an icon yet? +

+ +
+ + + diff --git a/css3/image-resolution.html b/css3/image-resolution.html new file mode 100644 index 0000000..7913a25 --- /dev/null +++ b/css3/image-resolution.html @@ -0,0 +1,30 @@ + + + +CSS3 test: image-resolution + + + + + +

http://www.w3.org/TR/css3-gcpm/#image-resolution0

+ +
+ +

+[#p01] This is a paragraph containing an image. +

+

+[#p02] This is a paragraph containing an image. +

+

+[#p03] This is a paragraph containing an image. +

+ +
+ + + diff --git a/css3/index-val.php b/css3/index-val.php new file mode 100644 index 0000000..e5d216e --- /dev/null +++ b/css3/index-val.php @@ -0,0 +1,52 @@ + + + + +CSS3 tests: index + + + + + + +

CSS3 Tests

+

+NOTE: this is a personal test suite and is neither meant to be fully comprehensive nor conform to the latest best practices in testing. It works for me and that's really it was ever intended to do. Reports of errors and inaccuracies in the tests themselves are always welcome. +

+

+WARNING: the URIs within this test suite are NOT guaranteed to be cool, though the URI of this page will remain cool. Bookmark or link individual tests at your own risk. +

+ +\r"; +echo "Property(prefixed)"; +foreach ($files as $prop) { + echo ""; + echo "$prop"; + if ($p = '-'.get_prefix().'-') { + echo "" . $p . "$prop"; + } + echo "\r"; +} + +echo "\r"; + +?> + + + + diff --git a/css3/index.php b/css3/index.php new file mode 100644 index 0000000..772ba45 --- /dev/null +++ b/css3/index.php @@ -0,0 +1,52 @@ + + + + +CSS3 tests: index + + + + + + +

CSS3 Tests

+

+NOTE: this is a personal test suite and is neither meant to be fully comprehensive nor conform to the latest best practices in testing. It works for me and that's really it was ever intended to do. Reports of errors and inaccuracies in the tests themselves are always welcome. +

+

+WARNING: the URIs within this test suite are NOT guaranteed to be cool, though the URI of this page will remain cool. Bookmark or link individual tests at your own risk. +

+ +\r"; +echo "Property(prefixed)"; +foreach ($files as $prop) { + echo ""; + echo "$prop"; + if ($p = '-'.get_prefix().'-') { + echo "" . $p . "$prop"; + } + echo "\r"; +} + +echo "\r"; + +?> + + + + diff --git a/css3/justify-content.html b/css3/justify-content.html new file mode 100644 index 0000000..3312dc7 --- /dev/null +++ b/css3/justify-content.html @@ -0,0 +1,65 @@ + + + +CSS3 test: justify-content + + + + + + +

http://www.w3.org/TR/css3-flexbox/#justify-content-property

+ +

Check the box or focus (not hover) the link to switch flex direction.

+ +switch direction + +
+ +
    +
  1. [#l01] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l02] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l03] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l04] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
    +
  1. [#l05] List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
+ +
+ + + diff --git a/css3/line-break.html b/css3/line-break.html new file mode 100644 index 0000000..d9b085e --- /dev/null +++ b/css3/line-break.html @@ -0,0 +1,41 @@ + + + +CSS3 test: line-break + + + + + +

http://www.w3.org/TR/css3-text/#line-break

+

+This page is currently a placeholder. For some super-crazy-detailed tests of this property, see http://www.w3.org/International/tests/html-css/line-break-ja-zh/results-ja. +

+ +
+ +

+[noID] +

+

+[#p01] +

+

+[#p02] +

+

+[#p03] +

+

+[#p04] +

+ + + + diff --git a/css3/line-height.html b/css3/line-height.html new file mode 100644 index 0000000..f5327e2 --- /dev/null +++ b/css3/line-height.html @@ -0,0 +1,28 @@ + + + +CSS3 test: line-height + + + + + +

http://www.w3.org/TR/css3-linebox/#line-height

+ +
+ +
+[#d01] This is a div in which resides a paragraph. The line-height of the div has been increased to one-and-one-half times the font size of the div. +

+This is the paragrph. It should use the same line-height as the div even though its font size is much smaller and it starts out with an even smaller line-height. The latter should be overridden by 'none'. +

+ +
+ +
+ + + diff --git a/css3/list-style-type.html b/css3/list-style-type.html new file mode 100644 index 0000000..5fd3117 --- /dev/null +++ b/css3/list-style-type.html @@ -0,0 +1,269 @@ + + + +CSS3 test: list-style-type + + + + + + +

http://www.w3.org/TR/css3-lists/#list-style-type

+ +
+ +
+

[#d01] Glyph list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
+ +
+

[#d02] Symbolic (et cetera) list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
+ +
+

[#d03] "Non-repeating" list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
+ +
+

[#d04] Algorithmic list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
+ +
+

[#d05] Numeric list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
  • [.l18]
  • two
  • three
+
  • [.l19]
  • two
  • three
+
  • [.l20]
  • two
  • three
+
  • [.l21]
  • two
  • three
+
  • [.l22]
  • two
  • three
+
  • [.l23]
  • two
  • three
+
  • [.l24]
  • two
  • three
+
+ +
+

[#d06] Alphabetic list types

+
  • [.l01]
  • two
  • three
+
  • [.l02]
  • two
  • three
+
  • [.l03]
  • two
  • three
+
  • [.l04]
  • two
  • three
+
  • [.l05]
  • two
  • three
+
  • [.l06]
  • two
  • three
+
  • [.l07]
  • two
  • three
+
  • [.l08]
  • two
  • three
+
  • [.l09]
  • two
  • three
+
  • [.l10]
  • two
  • three
+
  • [.l11]
  • two
  • three
+
  • [.l12]
  • two
  • three
+
  • [.l13]
  • two
  • three
+
  • [.l14]
  • two
  • three
+
  • [.l15]
  • two
  • three
+
  • [.l16]
  • two
  • three
+
  • [.l17]
  • two
  • three
+
  • [.l18]
  • two
  • three
+
  • [.l19]
  • two
  • three
+
  • [.l20]
  • two
  • three
+
  • [.l21]
  • two
  • three
+
  • [.l22]
  • two
  • three
+
  • [.l23]
  • two
  • three
+
  • [.l24]
  • two
  • three
+
  • [.l25]
  • two
  • three
+
  • [.l26]
  • two
  • three
+
  • [.l27]
  • two
  • three
+
  • [.l28]
  • two
  • three
+
  • [.l29]
  • two
  • three
+
  • [.l30]
  • two
  • three
+
  • [.l31]
  • two
  • three
+
  • [.l32]
  • two
  • three
+
  • [.l33]
  • two
  • three
+
  • [.l34]
  • two
  • three
+
  • [.l35]
  • two
  • three
+
  • [.l36]
  • two
  • three
+
  • [.l37]
  • two
  • three
+
  • [.l38]
  • two
  • three
+
  • [.l39]
  • two
  • three
+
  • [.l40]
  • two
  • three
+
  • [.l41]
  • two
  • three
+
  • [.l42]
  • two
  • three
+
  • [.l43]
  • two
  • three
+
+ +
+ +
+ + + diff --git a/css3/object-fit.html b/css3/object-fit.html new file mode 100644 index 0000000..06e6faf --- /dev/null +++ b/css3/object-fit.html @@ -0,0 +1,25 @@ + + + +CSS3 test: object-fit + + + + + +

http://www.w3.org/TR/css3-page/#fit

+ +
+ +

A paragraph containing an un-fit image. The next two paragraphs will contain fit images.

+

+

+ +
+ + + diff --git a/css3/order.html b/css3/order.html new file mode 100644 index 0000000..5e8a66f --- /dev/null +++ b/css3/order.html @@ -0,0 +1,46 @@ + + + +CSS3 test: order + + + + + +

http://www.w3.org/TR/css3-flexbox/#order-property

+ +
+ +[#l01] +
    +
  1. List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
  7. List item 4
  8. +
  9. List item 5
  10. +
+ +[#l02] +
    +
  1. List item 1
  2. +
  3. List item 2
  4. +
  5. List item 3
  6. +
  7. List item 4
  8. +
  9. List item 5
  10. +
+ +
+ + + diff --git a/css3/outline-offset.html b/css3/outline-offset.html new file mode 100644 index 0000000..db5d3c2 --- /dev/null +++ b/css3/outline-offset.html @@ -0,0 +1,32 @@ + + + +CSS3 test: outline-offset + + + + + +

http://www.w3.org/TR/css3-ui/#outline-offset0

+ +
+ +

+[#p01] This is a paragraph containing a span whose outline has been offset. +

+

+[#p02] This is a paragraph containing a span whose outline has been offset. +

+

+[#p03] This is a paragraph containing a span whose outline may have been offset even though the specification forbids it. If it is two pixels, orange, dashed, or offset inward, then the browser has gone beyond the specification. +

+ +
+ + + diff --git a/css3/overflow-style.html b/css3/overflow-style.html new file mode 100644 index 0000000..c18b4e8 --- /dev/null +++ b/css3/overflow-style.html @@ -0,0 +1,26 @@ + + + +CSS3 test: overflow-style + + + + + +

http://www.w3.org/TR/css3-marquee/#overflow-style

+ +
+

+[#p01] This is a paragraph of text. It should marquee horizontally in cases where it overflows its parent element. +

+

+[#p02] This is a paragraph of text. It should marquee vertically in cases where it overflows its parent element. +

+
+ + + diff --git a/css3/overflow-wrap.html b/css3/overflow-wrap.html new file mode 100644 index 0000000..9f7c66b --- /dev/null +++ b/css3/overflow-wrap.html @@ -0,0 +1,30 @@ + + + +CSS3 test: overflow-wrap + + + + + +

http://www.w3.org/TR/css3-text/#overflow-wrap

+

See also the test for word-wrap, which is an alternate name for overflow-wrap.

+ +
+ +

+[#p01] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+

+[#p02] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

+ +

Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

+
+ + + diff --git a/css3/overflow-x.html b/css3/overflow-x.html new file mode 100644 index 0000000..3969cb7 --- /dev/null +++ b/css3/overflow-x.html @@ -0,0 +1,39 @@ + + + +CSS3 test: overflow-x + + + + + +

http://www.w3.org/TR/css3-box/#overflow-x

+ +
+
+[#d01] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d02] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d03] Following is a paragraph containing an image. It should have an x-axis overflow effect where it overflows its parent element. +

+ +

+
+
+ + + diff --git a/css3/overflow-y.html b/css3/overflow-y.html new file mode 100644 index 0000000..7fbf282 --- /dev/null +++ b/css3/overflow-y.html @@ -0,0 +1,39 @@ + + + +CSS3 test: overflow-x + + + + + +

http://www.w3.org/TR/css3-box/#overflow-y

+ +
+
+[#d01] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d02] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+[#d03] Following is a paragraph containing an image. It should have an y-axis overflow effect where it overflows its parent element. +

+ +

+
+
+ + + diff --git a/css3/overflow.html b/css3/overflow.html new file mode 100644 index 0000000..cb7886f --- /dev/null +++ b/css3/overflow.html @@ -0,0 +1,61 @@ + + + +CSS3 test: overflow + + + + + +

http://www.w3.org/TR/css3-marquee/#overflow

+ +
+
+[#d01] visible +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d02] hidden +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d03] scroll +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d04] auto +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d05] no-display +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+[#d06] no-content +

+This is a paragraph of text. Its content should overflow the element box. +

+
+
+ + + diff --git a/css3/perspective-origin.html b/css3/perspective-origin.html new file mode 100644 index 0000000..f451fab --- /dev/null +++ b/css3/perspective-origin.html @@ -0,0 +1,39 @@ + + + + +CSS3 test: perspective-origin + + + + + +

+ +
+ +
+[#d01] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d02] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d03] Following is a div with some perspective (we hope). +
Total perspective!
+
+ +
+ + + diff --git a/css3/perspective.html b/css3/perspective.html new file mode 100644 index 0000000..5ce5e0d --- /dev/null +++ b/css3/perspective.html @@ -0,0 +1,39 @@ + + + + +CSS3 test: perspective + + + + + +

+ +
+ +
+[#d01] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d02] Following is a div with some perspective (we hope). +
Total perspective!
+
+
+[#d03] Following is a div with some perspective (we hope). +
Total perspective!
+
+ +
+ + + diff --git a/css3/punctuation-trim.html b/css3/punctuation-trim.html new file mode 100644 index 0000000..638f151 --- /dev/null +++ b/css3/punctuation-trim.html @@ -0,0 +1,31 @@ + + + +CSS3 test: punctuation-trim + + + + + +

http://www.w3.org/TR/css3-text/#punctuation-trim

+ +
+ +
    +
  1. [#li01] (( •( )( )• ))
  2. +
  3. [#li02] (( •( )( )• ))
  4. +
  5. [#li03] (( •( )( )• ))
  6. +
  7. [#li04] (( •( )( )• ))
  8. +
  9. [#li05] (( •( )( )• ))
  10. +
+ +
+ + + diff --git a/css3/resize.html b/css3/resize.html new file mode 100644 index 0000000..97f8e98 --- /dev/null +++ b/css3/resize.html @@ -0,0 +1,30 @@ + + + +CSS3 test: resize + + + + + +

http://www.w3.org/TR/css3-ui/#resize0

+ +
+

+[#p01] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+

+[#p02] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+

+[#p03] This is a paragraph of text. It should have an x-axis overflow effect where it overflows its parent element. +

+
+ + + diff --git a/css3/rotation.html b/css3/rotation.html new file mode 100644 index 0000000..2940eaf --- /dev/null +++ b/css3/rotation.html @@ -0,0 +1,32 @@ + + + +CSS3 test: rotation + + + + + +

http://www.w3.org/TR/css3-box/#rotating +

+ +
+ +

+[#p01] This is a paragraph of text. +

+

+[#p02] This is a paragraph of text. +

+

+[#p03] This is a paragraph of text. +

+ +
+ + + diff --git a/css3/sel-selection.html b/css3/sel-selection.html new file mode 100644 index 0000000..0f44335 --- /dev/null +++ b/css3/sel-selection.html @@ -0,0 +1,32 @@ + + + +CSS3 test: the element selector + + + + + +

+

+ +
+Here's some div text. + +

+This is a paragraph. Inside it we find a span element which should style differently. +

+ +More div text. +
+ + + diff --git a/css3/show.php b/css3/show.php new file mode 100644 index 0000000..47b3e52 --- /dev/null +++ b/css3/show.php @@ -0,0 +1,65 @@ +#",$temp[0],$extras); + if ($check) { + $properties = explode(" ",trim($extras[1])); + } else { + $properties = array(); + } + array_unshift($properties,$property); + foreach ($properties as $prop) { + $temp[0] = str_replace($prop.":",$prefix.$prop.":",$temp[0]); + } + $test = join("\r"; +$nav .= "
  • Index
  • \r"; +if ($prev) $nav .= "
  • $prefix$prev
  • \r"; +if ($prefix) { + $nav .= "
  • $url
  • "; +} else { + $pre = get_prefix(); + $nav .= "
  • -$pre-$url
  • "; +} +if ($next) $nav .= "
  • $prefix$next
  • \r"; +$nav .= "
  • ‘raw’ file
  • "; +$nav .= "\r"; + +$test = str_replace("",$nav."",$test); + +echo $test; + +?> \ No newline at end of file diff --git a/css3/tab-size.html b/css3/tab-size.html new file mode 100644 index 0000000..2fc7d0a --- /dev/null +++ b/css3/tab-size.html @@ -0,0 +1,50 @@ + + + +CSS3 test: tab-size + + + + + +

    http://www.w3.org/TR/css3-text/#tab-size

    + +
    + +

    + There are twenty-four spaces before this text. (no ID) +

    +

    + There are three tabs before this text. (no ID) +

    +

    + [#p01] There are three tabs before this text. +

    +

    + [#p02] There are three tabs before this text. +

    +

    + [#p03] There are three tabs before this text. +

    +

    + [#p04] There are three tabs before this text. +

    +

    + [#p05] There are three tabs before this text. +

    +

    + [#p06] There are three tabs before this text. +

    + +
    + + + diff --git a/css3/text-align-last.html b/css3/text-align-last.html new file mode 100644 index 0000000..0f8d2e1 --- /dev/null +++ b/css3/text-align-last.html @@ -0,0 +1,45 @@ + + + +CSS3 test: text-align-last + + + + + +

    http://www.w3.org/TR/css3-text/#text-align-last

    + +
    + +

    +[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    +

    +[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    +

    +[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    +

    +[#p04] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    +

    +[#p05] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    +

    +[#p06] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed.
    The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +

    + +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

    +
    + + + diff --git a/css3/text-align.html b/css3/text-align.html new file mode 100644 index 0000000..4a1d577 --- /dev/null +++ b/css3/text-align.html @@ -0,0 +1,105 @@ + + + +CSS3 test: text-align + + + + + + +

    http://www.w3.org/TR/css3-text/#text-align

    + +
    + +

    +[.p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p01] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

    + +
    + +

    +[.p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p02] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B? +

    + +
    + +

    +[.p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p03] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

    + +
    + +

    +[.p04] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p04] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B? +

    + +
    + +

    +[.p05] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p05] في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

    + +
    + +

    +[.p06] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B?
    At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? +

    +

    +[.p06] فבConHugeCo, אנחנו מבינים איך לנצל בצורה אנכית. האם יש לך תכנית להפוך B2C2B?
    في ConHugeCo، ونحن نفهم كيفية استغلال عموديا. هل لديك خطة لتصبح B2C2B؟ +

    + +
    + +
    +

    [.d01 p] This is a paragraph, and it should be right-justified.

    +

    [.d01 p + p] This is a paragraph, and it should be centered.

    +
    + + + + + + + + + + +
    Row 1ABCDEFG
    Row 2GABCDEF
    Row 3FGABCDE
    Row 4EFGABCD
    Row 5DEFGABC
    Row 6CDEFGAB
    Row 7BCDEFGA
    Row 81234567
    + +
    +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com. Arabic and Hebrew translations courtesy Google Translate.

    + + + diff --git a/css3/text-justify.html b/css3/text-justify.html new file mode 100644 index 0000000..d592e3e --- /dev/null +++ b/css3/text-justify.html @@ -0,0 +1,33 @@ + + + +CSS3 test: text-justify + + + + + +

    http://www.w3.org/TR/css3-text/#text-justify

    + +
    + +

    +[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    +

    +[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    +

    +[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    + +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

    +
    + + + diff --git a/css3/text-outline.html b/css3/text-outline.html new file mode 100644 index 0000000..da1c171 --- /dev/null +++ b/css3/text-outline.html @@ -0,0 +1,25 @@ + + + +CSS3 test: text-outline + + + + + +

    http://www.w3.org/TR/css3-text/#text-outline

    + +
    + +

    Heading 1

    +

    Heading 2

    +

    Heading 3

    + +
    + + + diff --git a/css3/text-rendering-2.html b/css3/text-rendering-2.html new file mode 100644 index 0000000..384026c --- /dev/null +++ b/css3/text-rendering-2.html @@ -0,0 +1,91 @@ + + + +CSS3 test: text-rendering + + + + + + +

    + +
    + +

    +aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

    +

    +aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

    +

    +aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

    +

    +aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

    +

    +aa ab ac ad ae af ag ah ai aj ak al am +an ao ap aq ar as at au av aw ax ay az +ba bb bc bd be bf bg bh bi bj bk bl bm +bn bo bp bq br bs bt bu bv bw bx by bz +ca cb cc cd ce cf cg ch ci cj ck cl cm +cn co cp cq cr cs ct cu cv cw cx cy cz +da db dc dd de df dg dh di dj dk dl dm +dn do dp dq dr ds dt du dv dw dx dy dz +ea eb ec ed ee ef eg eh ei ej ek el em +en eo ep eq er es et eu ev ew ex ey ez +

    + +
    + + + diff --git a/css3/text-rendering.html b/css3/text-rendering.html new file mode 100644 index 0000000..f582392 --- /dev/null +++ b/css3/text-rendering.html @@ -0,0 +1,60 @@ + + + +CSS3 test: text-rendering + + + + + + +

    + +
    + +

    +OX ox OC oc Te te FF ff Fi fi FL fl +

    +

    +OX ox OC oc Te te FF ff Fi fi FL fl +

    +

    +OX ox OC oc Te te FF ff Fi fi FL fl +

    +

    +OX ox OC oc Te te FF ff Fi fi FL fl +

    +

    +OX ox OC oc Te te FF ff Fi fi FL fl +

    + +
    + +

    +Vestibulum id ligua porta felis eusimod semper. +

    +

    +Vestibulum id ligua porta felis eusimod semper. +

    +

    +Vestibulum id ligua porta felis eusimod semper. +

    +

    +Vestibulum id ligua porta felis eusimod semper. +

    +

    +Vestibulum id ligua porta felis eusimod semper. +

    + + +
    + + + diff --git a/css3/text-shadow.html b/css3/text-shadow.html new file mode 100644 index 0000000..a83fe04 --- /dev/null +++ b/css3/text-shadow.html @@ -0,0 +1,25 @@ + + + +CSS3 test: text-shadow + + + + + +

    http://www.w3.org/TR/css3-text/#text-shadow

    + +
    + +

    Heading 1

    +

    Heading 2

    +

    Heading 3

    + +
    + + + diff --git a/css3/text-wrap.html b/css3/text-wrap.html new file mode 100644 index 0000000..ad30952 --- /dev/null +++ b/css3/text-wrap.html @@ -0,0 +1,32 @@ + + + +CSS3 test: text-wrap + + + + + +

    http://www.w3.org/TR/css3-text/#text-wrap

    + +
    + +

    +[#p01] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    +

    +[#p02] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    +

    +[#p03] At ConHugeCo, we understand how to exploit vertically. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions! +

    + +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

    +
    + + + diff --git a/css3/unicode-range.html b/css3/unicode-range.html new file mode 100644 index 0000000..d405eb3 --- /dev/null +++ b/css3/unicode-range.html @@ -0,0 +1,31 @@ + + + +CSS3 test: unicode-range + + + + + + +

    http://w3.org/TR/css3-fonts/

    + +
    + +

    A paragraph containing a span containing the uppercase alphabet in which A though M should be in SourceSansPro Bold and N through Z should be in a serif font. +ABCDEFGHIJKLMNOPQRSTUVWXYZ.

    +

    A paragraph containing a span containing the lowercase alphabet in which A though M should be in a serif font and N through Z should be in SourceSansPro Bold. +abcdefghijklmnopqrstuvwxyz.

    + +
    + + + diff --git a/css3/val-calc.html b/css3/val-calc.html new file mode 100644 index 0000000..df238b4 --- /dev/null +++ b/css3/val-calc.html @@ -0,0 +1,31 @@ + + + +CSS3 test: the 'calc' unit + + + + + +

    http://www.w3.org/TR/css3-values/#calc

    + +
    + +

    +[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
    + +
    + +
    +If they are not of equal width, then the browser likely does not support the calc unit. +

    + +
    + + + diff --git a/css3/val-ch.html b/css3/val-ch.html new file mode 100644 index 0000000..6fd82ce --- /dev/null +++ b/css3/val-ch.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'ch' unit + + + + + +

    http://www.w3.org/TR/css3-values/#relative0

    + +
    + +

    +[#p01] This is a paragraph that contains a span element and an img. The two are separated by a br element and should be of equal width. +
    +0000000000000000000000000 +
    + +
    +If they are not, then the browser likely does not support the ch unit. +

    +

    +[#p02] This is a paragraph that contains a span element and an img. The two are separated by a br element and should be of equal width. +
    +0000000000000000000000000 +
    + +
    +If they are not, then the browser likely does not support the ch unit. +

    + +
    + + + diff --git a/css3/val-colors.html b/css3/val-colors.html new file mode 100644 index 0000000..7f644ac --- /dev/null +++ b/css3/val-colors.html @@ -0,0 +1,42 @@ + + + +CSS3 test: color units + + + + + +

    http://www.w3.org/TR/css3-values/#calc

    + +
    + +

    This is a paragraph. It is the only one that should have a red background.

    +

    [#p01] This is a paragraph.

    +

    [#p02] This is a paragraph.

    +

    [#p03] This is a paragraph.

    +

    [#p04] This is a paragraph.

    +

    [#p05] This is a paragraph.

    +

    [#p06] This is a paragraph.

    +

    [#p07] This is a paragraph.

    +

    [#p08] This is a paragraph.

    +

    [#p09] This is a paragraph.

    +

    [#p10] This is a paragraph.

    + +
    + + + diff --git a/css3/val-length-units.html b/css3/val-length-units.html new file mode 100644 index 0000000..f32537b --- /dev/null +++ b/css3/val-length-units.html @@ -0,0 +1,53 @@ + + + +CSS3 test: length units + + + + + +

    http://www.w3.org/TR/css3-values/

    + +

    Based on http://codepen.io/anon/pen/JLdzg

    + +
    + +
    400px - pixels (device pixels)
    +
    20em - relative unit
    +
    20rem - root em
    +
    4.167in - inches
    +
    10.5833cm - centimeters
    +
    105.833mm - millimeters
    +
    300pt - points
    +
    25pc - picas
    +
    40ex - x-height
    +
    40ch - based on width of zero (0) character
    +
    50vw - viewport width
    +
    50vh - viewport height
    +
    50vmin - smaller of vw or vh
    +
    50vmax - larger of vw or vh
    + +
    + + + diff --git a/css3/val-rem.html b/css3/val-rem.html new file mode 100644 index 0000000..edc90f6 --- /dev/null +++ b/css3/val-rem.html @@ -0,0 +1,33 @@ + + + +CSS3 test: the 'rem' unit + + + + + +

    http://www.w3.org/TR/css3-values/#relative0

    + +
    + +

    +This is a paragraph without any children. It exists as a control to show the basic font size in use. +

    +

    +[#p01] This is a paragraph with a span element embedded within it. The span should be larger than the text that surrounds it and match the size of the previous paragraph. +

    +

    +[#p02] This is a paragraph with a span element embedded within it. The span should be smaller than the text that surrounds it and match the size of text outisde the span in the previous paragraph. +

    + +
    + + + diff --git a/css3/val-toggle.html b/css3/val-toggle.html new file mode 100644 index 0000000..364d4d5 --- /dev/null +++ b/css3/val-toggle.html @@ -0,0 +1,48 @@ + + + +CSS3 test: the 'toggle' unit + + + + + +

    http://www.w3.org/TR/css3-values/#toggle

    + +
    + +
      +
    • A list item. +
        +
      • A list item. +
          +
        • A list item. +
            +
          • A list item. +
              +
            • A list item. +
                +
              • A list item. +
                  +
                • A list item. +
                • +
                +
              • +
              +
            • +
            +
          • +
          +
        • +
        +
      • +
      +
    • +
    + +
    + + + diff --git a/css3/val-vh.html b/css3/val-vh.html new file mode 100644 index 0000000..c5c87bc --- /dev/null +++ b/css3/val-vh.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'vh' unit + + + + + +

    http://www.w3.org/TR/css3-values/#relative0

    + +
    + +

    +[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
    + +
    + +
    + +
    + +
    + +
    +If they all appear the same, then the browser likely does not support the vh unit. Note that if supported, the images should change width as the viewport height changes. +

    + +
    + + + diff --git a/css3/val-vmax.html b/css3/val-vmax.html new file mode 100644 index 0000000..cb700a4 --- /dev/null +++ b/css3/val-vmax.html @@ -0,0 +1,44 @@ + + + +CSS3 test: the 'vmax' unit + + + + + +

    http://www.w3.org/TR/css3-values/#viewport-relative-lengths

    + +

    +The images in this test should be sized according to either the height or width of the viewport, whichever is greater. +

    + +
    + +

    +[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
    + +
    + +
    + +
    + +
    + +
    +If they all appear the same, then the browser likely does not support the max unit. Note that if supported, the images should change width as the viewport height changes. +

    + +
    + + + diff --git a/css3/val-vmin.html b/css3/val-vmin.html new file mode 100644 index 0000000..d932589 --- /dev/null +++ b/css3/val-vmin.html @@ -0,0 +1,44 @@ + + + +CSS3 test: the 'vmin' unit + + + + + +

    http://www.w3.org/TR/css3-values/#viewport-relative-lengths

    + +

    +The images in this test should be sized according to either the height or width of the viewport, whichever is lesser. +

    + +
    + +

    +[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
    + +
    + +
    + +
    + +
    + +
    +If they all appear the same, then the browser likely does not support the vmin unit. Note that if supported, the images should change width as the viewport height changes. +

    + +
    + + + diff --git a/css3/val-vw.html b/css3/val-vw.html new file mode 100644 index 0000000..f58f6a7 --- /dev/null +++ b/css3/val-vw.html @@ -0,0 +1,40 @@ + + + +CSS3 test: the 'vw' unit + + + + + +

    http://www.w3.org/TR/css3-values/#relative0

    + +
    + +

    +[#p01] This is a paragraph that contains img elements, each of which refers to the same image ( ). They are separated by br elements. +
    + +
    + +
    + +
    + +
    + +
    +If they all appear the same, then the browser likely does not support the vw unit. Note that if supported, the images should change width as the viewport width changes. +

    + +
    + + + diff --git a/css3/white-space.html b/css3/white-space.html new file mode 100644 index 0000000..4800ffb --- /dev/null +++ b/css3/white-space.html @@ -0,0 +1,55 @@ + + + +CSS3 test: white-space + + + + + +

    http://www.w3.org/TR/css3-text/#white-space

    + +
    + +

    +[#p01] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

    +

    +[#p02] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

    +

    +[#p03] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

    +

    +[#p04] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

    +

    +[#p05] +At ConHugeCo, we understand how to exploit vertically. + Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? +Think visionary. +

    + +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

    +
    + + + diff --git a/css3/word-break.html b/css3/word-break.html new file mode 100644 index 0000000..8c8292e --- /dev/null +++ b/css3/word-break.html @@ -0,0 +1,37 @@ + + + +CSS3 test: word-break + + + + + +

    http://www.w3.org/TR/css3-text/#word-break

    +

    +The following tests use slightly modified text taken from the 13 November 2012 draft of “CSS Text Module Level 3”. It mixes a variety of languages and writing systems. +

    + +
    + +

    +[noID] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

    +

    +[#p01] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

    +

    +[#p02] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

    +

    +[#p03] 这是一些汉字, and a short testing-specific and an apprehensively extensive sequence of Latin text, و کمی نوشتنن عربی, และตัวอย่างการเขียนภาษาไทย. +

    + + + + diff --git a/css3/word-wrap.html b/css3/word-wrap.html new file mode 100644 index 0000000..4f07f05 --- /dev/null +++ b/css3/word-wrap.html @@ -0,0 +1,30 @@ + + + +CSS3 test: word-wrap + + + + + +

    http://www.w3.org/TR/css3-text/#word-wrap

    +

    See also the test for overflow-wrap, which is an alternate name for word-wrap.

    + +
    + +

    +[#p01] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

    +

    +[#p02] AtConHugeCo,weunderstandhowtoexploitvertically.DoyouhaveaschemetobecomeB2C2B?Withoutmeticulously-planneddot-comaggregation,e-servicesareforcedtobecomevirally-distributed.Themarketsfactorcanbesummedupinoneword:C2C2B.Whatdoestheterm"socialnetworks"reallymean?Thinkvisionary.Ifyougenerateproactively,youmayhavetoe-enableinteractively.Weapplytheproverb"Grassdoesn'tgrowonaracetrack"notonlytoourre-purposingbutourpowertomatrix.Ifallofthiscomesoffasdumbfoundingtoyou,that'sbecauseitis!Ourfeaturesetisunparalleledintheindustry,butourreality-basedsystemsandsimpleuseisusuallyconsideredaremarkableachievement.Thepowertobrandrobustlyleadstotheaptitudetoembraceseamlessly.Whatdowestreamline?Anythingandeverything,regardlessofreconditeness!Weinvariablyevolveholisticusers.Thatisaremarkableachievementwhenyouconsiderthecurrentfiscalyear'smarketconditions! +

    + +

    Corporate gibberish courtesy the Corporate Gibberish Generator on AndrewDavidson.com

    +
    + + + diff --git a/css3select.html b/css3select.html new file mode 100644 index 0000000..0dc4405 --- /dev/null +++ b/css3select.html @@ -0,0 +1 @@ + CSS3 Selector Fun
    table#checkerboard tr:nth-child(even) td:nth-child(even),
     table#checkerboard tr:nth-child(odd) td:nth-child(odd)
     {color: black; background: white;}
    table#checkerboard tr:nth-child(even) td:nth-child(odd),
     table#checkerboard tr:nth-child(odd) td:nth-child(even)
     {color: white; background: black;}
    
    r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
    r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
    r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
    r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
    r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
    r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
    r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
    r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
    table#alt-row {background: white;}
    table#alt-row tr:nth-child(3n+1) {background: silver;}
    table#alt-row td:nth-child(2n+4) {font-weight: bold; font-style: italic;}
    
    r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
    r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
    r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
    r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
    r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
    r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
    r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
    r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
    div.typetest p:first-of-type {color: gray; background: cyan;}
    div.typetest p:not-first-of-type {font-style: italic;}
    div.typetest p:last-child {text-decoration: underline;}
    div.typetest p:not(:last-child) {border: 2px dotted purple;}
    

    This is a paragraph which is first in the DIV.

    • Here's an unordered list...
    • ...with three list items...
    • ...just for fun.

    Another paragraph.

    Heading-3

    And yet another paragraph.

    \ No newline at end of file diff --git a/cursors.html b/cursors.html new file mode 100644 index 0000000..75271f9 --- /dev/null +++ b/cursors.html @@ -0,0 +1 @@ + Cursors!
    .one {cursor: help;}
    .two {cursor: hand; cursor: pointer;}
    .three {cursor: pointer; cursor: hand;}
    

    CNN (one)

    CNN (two)

    CNN (three)

    one two three
    \ No newline at end of file diff --git a/divcap.html b/divcap.html new file mode 100644 index 0000000..6a56a8e --- /dev/null +++ b/divcap.html @@ -0,0 +1 @@ + Capping a DIV

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/doctype1.html b/doctype1.html new file mode 100644 index 0000000..9f07e5f --- /dev/null +++ b/doctype1.html @@ -0,0 +1 @@ + DOCTYPE 1

    This is a paragraph which is a child of the BODY. Its text should be twice the size of the user default.

    This is a table which is a child of the BODY. The text in this table should be twice the size of the user default, but in most browsers is not, thanks to legacy behaviors and bugs.

    This is a paragraph which is a child of the BODY. Its text should be twice the size of the user default.

    [check this page with a DOCTYPE]

    \ No newline at end of file diff --git a/doctype2.html b/doctype2.html new file mode 100644 index 0000000..09e3a27 --- /dev/null +++ b/doctype2.html @@ -0,0 +1 @@ + DOCTYPE 2

    This is a paragraph which is a child of the BODY. Its text should be twice the size of the user default.

    This is a table which is a child of the BODY. The text in this table should be twice the size of the user default, but in many browsers is not, thanks to legacy behaviors and bugs. Those which are known to do "DOCTYPE switching" should show the text at the correct (doubled) size.

    This is a paragraph which is a child of the BODY. Its text should be twice the size of the user default.

    [check this page without a DOCTYPE]

    \ No newline at end of file diff --git a/dropcaps.html b/dropcaps.html new file mode 100644 index 0000000..02ec767 --- /dev/null +++ b/dropcaps.html @@ -0,0 +1 @@ + DropCap Tests

    This paragraph has an id of one. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    This paragraph has an id of two. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    This paragraph has an id of three. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    This paragraph has an id of four. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    This paragraph has an id of five. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/droppop.html b/droppop.html new file mode 100644 index 0000000..7c6d5ec --- /dev/null +++ b/droppop.html @@ -0,0 +1 @@ + DropPop Test
    \ No newline at end of file diff --git a/dtype/doctypes.html b/dtype/doctypes.html new file mode 100644 index 0000000..e45444c --- /dev/null +++ b/dtype/doctypes.html @@ -0,0 +1 @@ + DOCTYPE tests

    DOCTYPE tests

    1. The absence of a DOCTYPE
    2. A DOCTYPE declaration that cannot be understood (e.g., no matching quote).
    3. (unknown + URI)
    4. (nonversion)
    5. (nonversion + URI)
    6. <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    7. (2.0 + URI)
    8. (3.0)
    9. (3.0 + URI)
    10. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
    11. (3.2 + URI)
    12. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
    13. (4.0 + URI)
    14. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
    15. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" "http://www.w3.org/TR/REC-html40/frameset.dtd">
    16. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    17. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
    18. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
    19. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
    20. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
    21. (4.01 + URI)
    22. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">
    23. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
    24. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    25. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"
    26. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Strict//EN">
    27. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Strict//EN" "http://www.w3.org/TR/REC-html4/strict.dtd">
    28. <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN">
    29. ( + URI)
    30. <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
    31. ( + URI)
    32. <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN">
    33. ( + URI)
    \ No newline at end of file diff --git a/dtype/dtype-grid.html b/dtype/dtype-grid.html new file mode 100644 index 0000000..51aac9c --- /dev/null +++ b/dtype/dtype-grid.html @@ -0,0 +1 @@ + DOCTYPE grid
    EntryMeaning
    QQuirks mode
    SStrict mode
    -Status unknown
    DOCTYPE givenNN6.01NN6.1NN6.2IE5/MacIE6/Win
    No DOCTYPE given Q Q Q Q Q
    Unrecognized DOCTYPE Q Q Q S S
    Unrecognized DOCTYPE + URL Q Q Q S S
    HTML (no version given) Q Q Q Q Q
    HTML (no version given) + URL Q Q Q Q Q
    HTML 2.0 Q Q Q Q Q
    HTML 2.0 + URL Q Q Q Q Q
    HTML 3.0 Q Q Q Q Q
    HTML 3.0 + URL Q Q Q Q Q
    HTML 3.2 Q Q Q Q Q
    HTML 3.2 + URL Q Q Q Q Q
    HTML 4.0 (no type given) S S S S S
    HTML 4.0 (no type given) + URL S S S S S
    HTML 4.0 Frameset Q Q Q Q Q
    HTML 4.0 Frameset + URL Q Q Q S S
    HTML 4.0 Transitional Q Q Q Q Q
    HTML 4.0 Transitional + URL Q Q Q S S
    HTML 4.0 Strict S S S Q S
    HTML 4.0 Strict + URL S S S S S
    HTML 4.01 (no type given) S S S Q S
    HTML 4.01 (no type given) + URL S S S S S
    HTML 4.01 Frameset Q Q Q Q Q
    HTML 4.01 Frameset + URL S S S S S
    HTML 4.01 Transitional Q Q Q Q Q
    HTML 4.01 Transitional + URL S S S S S
    HTML 4.01 Strict S S S Q S
    HTML 4.01 Strict + URL S S S S S
    Any XHTML version S S S S S
    Any XHTML version + URL S S S S S
    Any XML S S S S S
    Any XML + URL S S S S S
    \ No newline at end of file diff --git a/dtype/dtype-test.css b/dtype/dtype-test.css new file mode 100644 index 0000000..de57785 --- /dev/null +++ b/dtype/dtype-test.css @@ -0,0 +1 @@ +body {font-family: Verdana; font-size: 200%; color: green;} h1 {font-size: 110%; border-bottom: 2px solid green; margin: 0;} h1+p {margin-top: 0; font-size: 50%; text-align: right; padding-right: 0.25em; border-right: 1px solid green;} table {border: 1px solid #9C9;} td {border: 1px solid #BDB;} \ No newline at end of file diff --git a/dtype/dtype-test00.html b/dtype/dtype-test00.html new file mode 100644 index 0000000..91488d1 --- /dev/null +++ b/dtype/dtype-test00.html @@ -0,0 +1 @@ + Doctype Tester

    No DOCTYPE present

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test01.html b/dtype/dtype-test01.html new file mode 100644 index 0000000..826aded --- /dev/null +++ b/dtype/dtype-test01.html @@ -0,0 +1 @@ + Doctype Tester

    Unknown DOCTYPE

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test02.html b/dtype/dtype-test02.html new file mode 100644 index 0000000..dc556df --- /dev/null +++ b/dtype/dtype-test02.html @@ -0,0 +1 @@ + Doctype Tester

    Unknown DOCTYPE + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test03.html b/dtype/dtype-test03.html new file mode 100644 index 0000000..4f4eee0 --- /dev/null +++ b/dtype/dtype-test03.html @@ -0,0 +1 @@ + Doctype Tester

    HTML (no version given)

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test04.html b/dtype/dtype-test04.html new file mode 100644 index 0000000..473ce3d --- /dev/null +++ b/dtype/dtype-test04.html @@ -0,0 +1 @@ + Doctype Tester

    HTML (no version given) + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test05.html b/dtype/dtype-test05.html new file mode 100644 index 0000000..d87beb1 --- /dev/null +++ b/dtype/dtype-test05.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 2.0

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test06.html b/dtype/dtype-test06.html new file mode 100644 index 0000000..fd6f2e6 --- /dev/null +++ b/dtype/dtype-test06.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 2.0 + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test07.html b/dtype/dtype-test07.html new file mode 100644 index 0000000..febbbcd --- /dev/null +++ b/dtype/dtype-test07.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 3.0

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test08.html b/dtype/dtype-test08.html new file mode 100644 index 0000000..6bcb1f9 --- /dev/null +++ b/dtype/dtype-test08.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 3.0 + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test09.html b/dtype/dtype-test09.html new file mode 100644 index 0000000..4d2903b --- /dev/null +++ b/dtype/dtype-test09.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 3.2

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test10.html b/dtype/dtype-test10.html new file mode 100644 index 0000000..63921a0 --- /dev/null +++ b/dtype/dtype-test10.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 3.2 + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test11.html b/dtype/dtype-test11.html new file mode 100644 index 0000000..429b0bd --- /dev/null +++ b/dtype/dtype-test11.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 (no type given)

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test12.html b/dtype/dtype-test12.html new file mode 100644 index 0000000..b9508a7 --- /dev/null +++ b/dtype/dtype-test12.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 (no type given) + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test13.html b/dtype/dtype-test13.html new file mode 100644 index 0000000..730e192 --- /dev/null +++ b/dtype/dtype-test13.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Frameset

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test14.html b/dtype/dtype-test14.html new file mode 100644 index 0000000..3297a47 --- /dev/null +++ b/dtype/dtype-test14.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Frameset + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test15.html b/dtype/dtype-test15.html new file mode 100644 index 0000000..d9ca3c2 --- /dev/null +++ b/dtype/dtype-test15.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Transitional

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test16.html b/dtype/dtype-test16.html new file mode 100644 index 0000000..3d270e0 --- /dev/null +++ b/dtype/dtype-test16.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Transitional + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test17.html b/dtype/dtype-test17.html new file mode 100644 index 0000000..d8833f8 --- /dev/null +++ b/dtype/dtype-test17.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Strict

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test18.html b/dtype/dtype-test18.html new file mode 100644 index 0000000..3f80e66 --- /dev/null +++ b/dtype/dtype-test18.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.0 Strict + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test19.html b/dtype/dtype-test19.html new file mode 100644 index 0000000..a74c20c --- /dev/null +++ b/dtype/dtype-test19.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 (no type given)

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test20.html b/dtype/dtype-test20.html new file mode 100644 index 0000000..0c6d69a --- /dev/null +++ b/dtype/dtype-test20.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 (no type given) + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test21.html b/dtype/dtype-test21.html new file mode 100644 index 0000000..9dd1d62 --- /dev/null +++ b/dtype/dtype-test21.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Frameset

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test22.html b/dtype/dtype-test22.html new file mode 100644 index 0000000..8bbcfd9 --- /dev/null +++ b/dtype/dtype-test22.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Frameset + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test23.html b/dtype/dtype-test23.html new file mode 100644 index 0000000..0427088 --- /dev/null +++ b/dtype/dtype-test23.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Transitional

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test24.html b/dtype/dtype-test24.html new file mode 100644 index 0000000..5d6965c --- /dev/null +++ b/dtype/dtype-test24.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Transitional + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test25.html b/dtype/dtype-test25.html new file mode 100644 index 0000000..52efd50 --- /dev/null +++ b/dtype/dtype-test25.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Strict

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dtype/dtype-test26.html b/dtype/dtype-test26.html new file mode 100644 index 0000000..f407082 --- /dev/null +++ b/dtype/dtype-test26.html @@ -0,0 +1 @@ + Doctype Tester

    HTML 4.01 Strict + URI

    next test

    This is paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    This is table text. It should inherit the BODY styles in strict mode, but not inherit one or more styles from the BODY if in quirks mode.

    This is more paragraph text which should inherit all BODY styles no matter what mode the browser uses.

    \ No newline at end of file diff --git a/dualclass.html b/dualclass.html new file mode 100644 index 0000000..66e6fa9 --- /dev/null +++ b/dualclass.html @@ -0,0 +1 @@ + meyer's 5.8.3 chart selector issue

    The Fox Jumped Over The Lazy Dog.

    (1) This sentence has a class in the <p> element, '.outside'.

    (2) This sentence has a class in the <p> element, '.inside'.

    (3) This sentence has a class in the <p> element ('.outside') but this inline <span> has the '.inside' class in it.

    (4) This sentence has both the '.outside' and '.inside' classes attributed to the <p> element.

    (5) This sentence has both the '.outside' and '.insidesep' classes attributed to the <p> element.

    \ No newline at end of file diff --git a/edit-styles.html b/edit-styles.html new file mode 100644 index 0000000..e145bec --- /dev/null +++ b/edit-styles.html @@ -0,0 +1,64 @@ + + + +Style Editing + + + + + +

    Heading-1

    +

    A paragraph. Do you have a scheme to become B2C2B? Without meticulously-planned dot-com aggregation, e-services are forced to become virally-distributed. The markets factor can be summed up in one word: C2C2B. What does the term "social networks" really mean? Think visionary. If you generate proactively, you may have to e-enable interactively. We apply the proverb "Grass doesn't grow on a racetrack" not only to our re-purposing but our power to matrix.

    + +

    Heading-2

    +

    A paragraph. If all of this comes off as dumbfounding to you, that's because it is! Our feature set is unparalleled in the industry, but our reality-based systems and simple use is usually considered a remarkable achievement. The power to brand robustly leads to the aptitude to embrace seamlessly. What do we streamline? Anything and everything, regardless of reconditeness! We invariably evolve holistic users. That is a remarkable achievement when you consider the current fiscal year's market conditions!

    + +
      +
    • An unordered list.
    • +
    • With list items.
    • +
    • Like this one.
    • +
    + +

    Heading-3

    +

    A paragraph. Do you have a game plan to become strategic? Think mega-mega-intra-affiliate-based. What do we utilize? Anything and everything, regardless of abstruseness! We will incentivize the capability of user-centric technologies to orchestrate. We will evolve the term "next-generation". What does the buzzword "real-time" really mean? We pride ourselves not only on our sticky feature set, but our user-proof administration and newbie-proof configuration. Imagine a combination of PHP and CSS. If all of this seems perplexing to you, that's because it is!

    + + + + + + + + + + + + + + + + + + + + + + + + + + +
    r1c1r1c2r1c3r1c4r1c5r1c6r1c7r1c8
    r2c1r2c2r2c3r2c4r2c5r2c6r2c7r2c8
    r3c1r3c2r3c3r3c4r3c5r3c6r3c7r3c8
    r4c1r4c2r4c3r4c4r4c5r4c6r4c7r4c8
    r5c1r5c2r5c3r5c4r5c5r5c6r5c7r5c8
    r6c1r6c2r6c3r6c4r6c5r6c6r6c7r6c8
    r7c1r7c2r7c3r7c4r7c5r7c6r7c7r7c8
    r8c1r8c2r8c3r8c4r8c5r8c6r8c7r8c8
    + + + + diff --git a/element-reference.html b/element-reference.html new file mode 100644 index 0000000..303be6d --- /dev/null +++ b/element-reference.html @@ -0,0 +1,27 @@ + + + + +Element-reference images + + + + + +
    bg
    + +
    SHOW
    + + + diff --git a/empty-bare.html b/empty-bare.html new file mode 100644 index 0000000..4414dd4 --- /dev/null +++ b/empty-bare.html @@ -0,0 +1,54 @@ + + + +Bare :empty + + + + + +un-elemented text (so it's a node of the body) + +

    Empties

    +
      +
    • empty line item, a return-only, and a space-only line item follow (in that order):
    • +
    • +
    • +
    • +
    • +
    • empty span [ ]
    • +
    • all of the text in this list item is inside a span
    • +
    • missing image [ ]
    • +
    • loaded image [ blah ]
    • +
    • break element [
      ]
    • +
    • a form with... +
        +
      • a text input [ ]
      • +
      • a text input with a value [ ]
      • +
      • a radio input [ ]
      • +
      • a checkbox input [ ]
      • +
      • a submit input [ ]
      • +
      • a textarea [ ]
      • +
      • a textarea with content [ ]
      • +
      +
    • +
    + + + diff --git a/escape-parse.html b/escape-parse.html new file mode 100644 index 0000000..63f8b88 --- /dev/null +++ b/escape-parse.html @@ -0,0 +1 @@ + Escape test

    This paragraph should have a green background. If the background is red, then it has not properly parsed the encoded letter in the property name.

    \ No newline at end of file diff --git a/escape-period.html b/escape-period.html new file mode 100644 index 0000000..0603d9f --- /dev/null +++ b/escape-period.html @@ -0,0 +1 @@ + Escape test

    This paragraph should have a green background. If the background is red, then it has not properly parsed the escaped period (.) in the selector.

    This paragraph should have a green background. If the background is red, then it has not properly parsed the escaped period (.) in the selector.

    \ No newline at end of file diff --git a/firefox-font-tab.html b/firefox-font-tab.html new file mode 100644 index 0000000..b524f2c --- /dev/null +++ b/firefox-font-tab.html @@ -0,0 +1 @@ + Font Tab testing
    foo
    foo
    foo foo
    \ No newline at end of file diff --git a/fixed-bg.html b/fixed-bg.html new file mode 100644 index 0000000..1a97ae6 --- /dev/null +++ b/fixed-bg.html @@ -0,0 +1 @@ + Fixed background test

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto.

    Haec disserens qua de re agatur et in quo causa consistat non videt. Non enim si alii ad alia propensiores sunt propter causas naturales et antecedentes, idciro etiam nostrarum voluntatum atque appetitionum sunt causae naturales at antecedentes; nam nihil esset in nostra potestate si res ita se haberet.

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto.

    Haec disserens qua de re agatur et in quo causa consistat non videt. Non enim si alii ad alia propensiores sunt propter causas naturales et antecedentes, idciro etiam nostrarum voluntatum atque appetitionum sunt causae naturales at antecedentes; nam nihil esset in nostra potestate si res ita se haberet.

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto.

    Haec disserens qua de re agatur et in quo causa consistat non videt. Non enim si alii ad alia propensiores sunt propter causas naturales et antecedentes, idciro etiam nostrarum voluntatum atque appetitionum sunt causae naturales at antecedentes; nam nihil esset in nostra potestate si res ita se haberet.

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto.

    Haec disserens qua de re agatur et in quo causa consistat non videt. Non enim si alii ad alia propensiores sunt propter causas naturales et antecedentes, idciro etiam nostrarum voluntatum atque appetitionum sunt causae naturales at antecedentes; nam nihil esset in nostra potestate si res ita se haberet.

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto.

    Haec disserens qua de re agatur et in quo causa consistat non videt. Non enim si alii ad alia propensiores sunt propter causas naturales et antecedentes, idciro etiam nostrarum voluntatum atque appetitionum sunt causae naturales at antecedentes; nam nihil esset in nostra potestate si res ita se haberet.

    \ No newline at end of file diff --git a/fixed-test.html b/fixed-test.html new file mode 100644 index 0000000..15e8f13 --- /dev/null +++ b/fixed-test.html @@ -0,0 +1 @@ + Fixed...

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    It's an H1 element!

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    It's an H2 element!

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/flexbox-a11y.html b/flexbox-a11y.html new file mode 100644 index 0000000..e304bf6 --- /dev/null +++ b/flexbox-a11y.html @@ -0,0 +1,64 @@ + + + +Flexible Box Accessibility Testing + + + + +

    This is an accessibility test. Its results can only be evaluated in a screen reader, speaking browser, or similar audio medium. +

    +

    Whatever you see cannot be taken as either true or false.

    + +
    + +

    What comes next is false.

    +

    The content is heard in layout order, not source order.

    +

    What comes next is true.

    +

    The content is heard in source order, not layout order.

    + +
    + +

    The test is now concluded.

    + + + diff --git a/flexbox01.html b/flexbox01.html new file mode 100644 index 0000000..96420f8 --- /dev/null +++ b/flexbox01.html @@ -0,0 +1,64 @@ + + + +Flexbox Float Follies + + + + +

    +Hover over the div in WebKit to demonstrate a bug when you combine flexbox and float. Note that hovering is not required to trigger this bug—just floating a flexbox. +

    + +
    +

    +Have you ever been unable to optimize your viral, next-generation, viral feature set? Without having to purchase expensive support contracts? The re-sizing factor is dot-com. We believe we know that it is better to harness intuitively than to synergize dynamically. What does it really mean to strategize "perfectly"? What does it really mean to reinvent "perfectly"? What does it really mean to maximize "extensibly"? The e-commerce metrics factor can be summed up in one word: efficient. Our feature set is unparalleled, but our visionary infomediaries and simple use is invariably considered an amazing achievement. We apply the proverb "You can lead a horse to water, but you can't make it drink" not only to our power shifts but our power to integrate. The capacity to aggregate intuitively leads to the capacity to iterate micro-virally. +

    +

    +The deliverables factor can be summed up in one word: C2C2B. Complex Spiral Consulting practically invented the term "re-sizing reports". Think turn-key, real-world, value-added. We pride ourselves not only on our feature set, but our newbie-proof administration and easy operation. Our feature set is unmatched, but our customized data hygiene and easy operation is often considered a terrific achievement. Do you have a plan to become real-world? We think we know that it is better to iterate wirelessly than to seize proactively. Without appropriate markets, platforms are forced to become turn-key. We realize that it is better to morph seamlessly than to streamline wirelessly. Think B2C2B. A company that can streamline defiantly will (one day) be able to drive easily. Quick: do you have a reality-based plan for dealing with new subscriber communities? The metrics for M&A are more well-understood if they are not B2B. +

    +

    +Have you ever been unable to optimize your viral, next-generation, viral feature set? Without having to purchase expensive support contracts? The re-sizing factor is dot-com. We believe we know that it is better to harness intuitively than to synergize dynamically. What does it really mean to strategize "perfectly"? What does it really mean to reinvent "perfectly"? What does it really mean to maximize "extensibly"? The e-commerce metrics factor can be summed up in one word: efficient. Our feature set is unparalleled, but our visionary infomediaries and simple use is invariably considered an amazing achievement. We apply the proverb "You can lead a horse to water, but you can't make it drink" not only to our power shifts but our power to integrate. The capacity to aggregate intuitively leads to the capacity to iterate micro-virally. +

    +

    +Complex Spiral Consulting practically invented the term "re-sizing reports". Think turn-key, real-world, value-added. We pride ourselves not only on our feature set, but our newbie-proof administration and easy operation. Our feature set is unmatched, but our customized data hygiene and easy operation is often considered a terrific achievement. Do you have a plan to become real-world? We think we know that it is better to iterate wirelessly than to seize proactively. Without appropriate markets, platforms are forced to become turn-key. We realize that it is better to morph seamlessly than to streamline wirelessly. Think B2C2B. A company that can streamline defiantly will (one day) be able to drive easily. Quick: do you have a reality-based plan for dealing with new subscriber communities? The metrics for M&A are more well-understood if they are not B2B. +

    +
    + + + diff --git a/float-contain.html b/float-contain.html new file mode 100644 index 0000000..e4b0042 --- /dev/null +++ b/float-contain.html @@ -0,0 +1,33 @@ + + + +IE/Win float test + + + + +
    + +
    topper (675px)
    + +
    main (63%)
    + + + + + +
    + + + diff --git a/float-inline.html b/float-inline.html new file mode 100644 index 0000000..57470eb --- /dev/null +++ b/float-inline.html @@ -0,0 +1,74 @@ + + + +Floats and Inline Boxes + + + + +

    Normal Flow

    + +

    This is an H3

    +

    This is an h4

    + +
    + +

    This is an inline H3

    +

    This is an h4

    + +
    + +

    This is an inline-block H3

    +

    This is an h4

    + + + +

    Float Right

    + +

    This is an H3

    +

    This is a floated h4

    + +
    + +

    This is an inline H3

    +

    This is a floated h4

    + +
    + +

    This is an inline-block H3

    +

    This is a floated h4

    + + + +

    Float Left

    + +

    This is an H3

    +

    This is a floated h4

    + +
    + +

    This is an inline H3

    +

    This is a floated h4

    + +
    + +

    This is an inline-block H3

    +

    This is a floated h4

    + + + diff --git a/float-inline2.html b/float-inline2.html new file mode 100644 index 0000000..df82bcf --- /dev/null +++ b/float-inline2.html @@ -0,0 +1,51 @@ + + + +Floats and Inline Boxes + + + + +
    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is an inline H3

    +

    This is a block h4

    +
    +
    +Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. +

    This is an inline h4

    +
    + + + diff --git a/float-jump.html b/float-jump.html new file mode 100644 index 0000000..47f5b2f --- /dev/null +++ b/float-jump.html @@ -0,0 +1 @@ + Float-jump

    Introducing float bugs

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/float-negmar.html b/float-negmar.html new file mode 100644 index 0000000..bb0db4e --- /dev/null +++ b/float-negmar.html @@ -0,0 +1 @@ + Negative-margin float test
    \ No newline at end of file diff --git a/floatpos100.html b/floatpos100.html new file mode 100644 index 0000000..951b2f5 --- /dev/null +++ b/floatpos100.html @@ -0,0 +1 @@ + Untitled
    This is a menu or a sidebar or another interesting element. You could put images and words here, and I don't mean the Dream Theater album. Audio streaming is a bit much to ask of an example this simple.
    This is a menu or a sidebar or another interesting element. You could put images and words here, and I don't mean the Dream Theater album. Audio streaming is a bit much to ask of an example this simple.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/focustest.html b/focustest.html new file mode 100644 index 0000000..aa2270c --- /dev/null +++ b/focustest.html @@ -0,0 +1 @@ + focus test
    \ No newline at end of file diff --git a/font-name-case-test.html b/font-name-case-test.html new file mode 100644 index 0000000..d6e4805 --- /dev/null +++ b/font-name-case-test.html @@ -0,0 +1 @@ + Font Name Case Testing
    p.font-name-1 {font-family: helvetica;}
    p.font-name-2 {font-family: Helvetica;}
    p.font-name-3 {font-family: "comic sans ms";}
    p.font-name-4 {font-family: "Comic Sans MS";}
    p.font-name-5 {font-family: comic sans ms;}
    p.font-name-6 {font-family: courier, monospace;}
    p.font-name-7 {font-family: Courier, monospace;}
    p.font-name-8 {font-family: MonoSpace;}
    

    The paragraph has not been styled, and the font should appear different from following paragraphs.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    This is a paragraph meant to test the case sensitivity of font names and their interpretation by Web browsers.

    \ No newline at end of file diff --git a/font-size-rounding.html b/font-size-rounding.html new file mode 100644 index 0000000..80be8fd --- /dev/null +++ b/font-size-rounding.html @@ -0,0 +1,56 @@ + + + +Font Size Rounding + + + + + +insert getComputedStyle sizes + +
    +

    b {font-size: 1.04em;}

    +

    +Nesting: (1(2(3(4(5(6(7(8(9(10)))))))))) +

    +
    + +
    +

    b {font-size: 1.2em;}

    +

    +Nesting: (1(2(3(4(5(6(7(8(9(10)))))))))) +

    +
    + +
    +

    (Sub-pixel font sizing, running from 10px to 11px)

    +

    +OOOOOOOOOOOOO

    +
    + + + + diff --git a/forms.html b/forms.html new file mode 100644 index 0000000..481b8a5 --- /dev/null +++ b/forms.html @@ -0,0 +1,58 @@ + + + +Form elements + + + + + +
    + +
      + +
    1. (text input)
    2. +
    3. (password input)
    4. +
    5. (radio input)
    6. +
    7. (checkbox input)
    8. +
    9. (button input)
    10. +
    11. (image input)
    12. +
    13. (file input)
    14. +
    15. (textarea)
    16. +
    17. + +(select) +
    18. +
    19. (submit)
    20. +
    21. (button)
    22. + +
    + +
    + + + + + + diff --git a/formstyle.html b/formstyle.html new file mode 100644 index 0000000..8101316 --- /dev/null +++ b/formstyle.html @@ -0,0 +1 @@ + Style/Form Test

    INPUT elements with type="text"



    INPUT elements without type="text"



    \ No newline at end of file diff --git a/formstyle2.html b/formstyle2.html new file mode 100644 index 0000000..3fc8c93 --- /dev/null +++ b/formstyle2.html @@ -0,0 +1 @@ + Style/Form Test

    INPUT elements with type="text"



    INPUT elements without type="text"



    \ No newline at end of file diff --git a/gradient-radial-average.html b/gradient-radial-average.html new file mode 100644 index 0000000..1b316d4 --- /dev/null +++ b/gradient-radial-average.html @@ -0,0 +1,37 @@ + + + +Average Radial Gradients + + + + + + +

    +

    +

    +

    +

    +

    +

    +

    +

    +

    + + + diff --git a/gradient-radial-degenerate.html b/gradient-radial-degenerate.html new file mode 100644 index 0000000..f786de8 --- /dev/null +++ b/gradient-radial-degenerate.html @@ -0,0 +1,45 @@ + + + +Degenerate Radial Gradients + + + + + + +

    Degenerate radial gradients

    +

    (because it’s the best section title in the history of W3C specs, that’s why)

    + +
    + +

    +

    +

    +

    +

    +

    +

    +

    +

    +

    + +
    + + + diff --git a/gradient-radials.html b/gradient-radials.html new file mode 100644 index 0000000..7049a88 --- /dev/null +++ b/gradient-radials.html @@ -0,0 +1,25 @@ + + + +Radial Gradients + + + + + + +

    + + + diff --git a/gradient-repeat-2.html b/gradient-repeat-2.html new file mode 100644 index 0000000..ad960d6 --- /dev/null +++ b/gradient-repeat-2.html @@ -0,0 +1,188 @@ + + + +Repeating Linear Gradients + + + + + +

    Repeating linear gradients

    + +

    +WARNING: NOTHING IN THIS TEST SHOULD BE TAKEN SERIOUSLY. THE REPEATING-LINEAR-GRADIENT SYNTAX COULD BE ALL WRONG, LEADING TO USELESS RESULTS. PROCEED AT YOUR OWN RISK. CORRECTIONS ARE WELCOME. +

    + +

    +The ruler is a background-repeat-repeated GIF, included for measurement purposes. As you might expect. +

    +

    +Each blue pattern is a repeating-linear-gradient of the form…
    repeating-linear-gradient(left, rgba(0,0,255,0.5) 0px, rgba(0,0,255,0.5) 1px, transparent 1px, transparent 2px);
    …where the lengths are multiplied by the number of each test. Thus, for test 6, they are 6px, 12px, 12px, and 18px, respectively. +

    +

    +Each red pattern is a background-repeat-repeated PNG which alternates half-transparent red and full transparency. +

    + +
      +
    1. +
      O
      +
      O
      +
      O
      +
    2. +
    3. +
      O
      +
      O
      +
      O
      +
    4. +
    5. +
      O
      +
      O
      +
      O
      +
    6. +
    7. +
      O
      +
      O
      +
      O
      +
    8. +
    9. +
      O
      +
      O
      +
      O
      +
    10. +
    11. +
      O
      +
      O
      +
      O
      +
    12. +
    13. +
      O
      +
      O
      +
      O
      +
    14. +
    15. +
      O
      +
      O
      +
      O
      +
    16. +
    17. +
      O
      +
      O
      +
      O
      +
    18. +
    19. +
      O
      +
      O
      +
      O
      +
    20. +
    + + + diff --git a/gradient-repeat.html b/gradient-repeat.html new file mode 100644 index 0000000..d32ea21 --- /dev/null +++ b/gradient-repeat.html @@ -0,0 +1,279 @@ + + + +Repeating Linear Gradients + + + + + +

    Repeating linear gradients

    + +

    +The ruler is a background-repeat-repeated GIF, included for measurement purposes. As you might expect. +

    +

    +Each red pattern is a background-repeat-repeated PNG which alternates half-transparent red and full transparency. +

    +

    +Each initial blue pattern (lrg) is a repeating-linear-gradient of the form… +
    +repeating-linear-gradient(left, rgba(0,0,255,0.5) 0px, rgba(0,0,255,0.5) 1px, transparent 1px, transparent 2px); +
    +…where the lengths are multiplied by the number of each test. Thus, for test 6, they are 0px, 6px, 6px, and 12px, respectively. +

    +

    +Each second blue pattern (lrg2) is a repeating-linear-gradient of the form… +
    +repeating-linear-gradient(left, rgba(0,0,255,0.5) 1px, transparent 1px, transparent 2px, rgba(0,0,255,0.5) 2px, rgba(0,0,255,0.5) 3px); +
    +…where the lengths are multiplied by the number of each test. Thus, for test 6, they are 6px, 12px, 12px, and 18px, respectively. +

    + +
      +
    1. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    2. +
    3. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    4. +
    5. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    6. +
    7. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    8. +
    9. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    10. +
    11. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    12. +
    13. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    14. +
    15. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    16. +
    17. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    18. +
    19. +
       
      +
      lrg
      +
      red
      +
      lrg2
      +
    20. +
    + + + diff --git a/gradient-repeat/l1.gif b/gradient-repeat/l1.gif new file mode 100644 index 0000000..6013f7e Binary files /dev/null and b/gradient-repeat/l1.gif differ diff --git a/gradient-repeat/l1.png b/gradient-repeat/l1.png new file mode 100644 index 0000000..fecf734 Binary files /dev/null and b/gradient-repeat/l1.png differ diff --git a/gradient-repeat/l10.gif b/gradient-repeat/l10.gif new file mode 100644 index 0000000..2006809 Binary files /dev/null and b/gradient-repeat/l10.gif differ diff --git a/gradient-repeat/l10.png b/gradient-repeat/l10.png new file mode 100644 index 0000000..48fea7e Binary files /dev/null and b/gradient-repeat/l10.png differ diff --git a/gradient-repeat/l2.gif b/gradient-repeat/l2.gif new file mode 100644 index 0000000..1fc2691 Binary files /dev/null and b/gradient-repeat/l2.gif differ diff --git a/gradient-repeat/l2.png b/gradient-repeat/l2.png new file mode 100644 index 0000000..cbb0de1 Binary files /dev/null and b/gradient-repeat/l2.png differ diff --git a/gradient-repeat/l3.gif b/gradient-repeat/l3.gif new file mode 100644 index 0000000..f820a27 Binary files /dev/null and b/gradient-repeat/l3.gif differ diff --git a/gradient-repeat/l3.png b/gradient-repeat/l3.png new file mode 100644 index 0000000..bcd5e74 Binary files /dev/null and b/gradient-repeat/l3.png differ diff --git a/gradient-repeat/l4.gif b/gradient-repeat/l4.gif new file mode 100644 index 0000000..1bebe29 Binary files /dev/null and b/gradient-repeat/l4.gif differ diff --git a/gradient-repeat/l4.png b/gradient-repeat/l4.png new file mode 100644 index 0000000..e9f9168 Binary files /dev/null and b/gradient-repeat/l4.png differ diff --git a/gradient-repeat/l5.gif b/gradient-repeat/l5.gif new file mode 100644 index 0000000..88ca4e2 Binary files /dev/null and b/gradient-repeat/l5.gif differ diff --git a/gradient-repeat/l5.png b/gradient-repeat/l5.png new file mode 100644 index 0000000..8d3497b Binary files /dev/null and b/gradient-repeat/l5.png differ diff --git a/gradient-repeat/l6.gif b/gradient-repeat/l6.gif new file mode 100644 index 0000000..40e4080 Binary files /dev/null and b/gradient-repeat/l6.gif differ diff --git a/gradient-repeat/l6.png b/gradient-repeat/l6.png new file mode 100644 index 0000000..2f9724e Binary files /dev/null and b/gradient-repeat/l6.png differ diff --git a/gradient-repeat/l7.gif b/gradient-repeat/l7.gif new file mode 100644 index 0000000..46a53ff Binary files /dev/null and b/gradient-repeat/l7.gif differ diff --git a/gradient-repeat/l7.png b/gradient-repeat/l7.png new file mode 100644 index 0000000..24affbc Binary files /dev/null and b/gradient-repeat/l7.png differ diff --git a/gradient-repeat/l8.gif b/gradient-repeat/l8.gif new file mode 100644 index 0000000..c75fbdb Binary files /dev/null and b/gradient-repeat/l8.gif differ diff --git a/gradient-repeat/l8.png b/gradient-repeat/l8.png new file mode 100644 index 0000000..c1fe69c Binary files /dev/null and b/gradient-repeat/l8.png differ diff --git a/gradient-repeat/l9.gif b/gradient-repeat/l9.gif new file mode 100644 index 0000000..0ea1d70 Binary files /dev/null and b/gradient-repeat/l9.gif differ diff --git a/gradient-repeat/l9.png b/gradient-repeat/l9.png new file mode 100644 index 0000000..85ea911 Binary files /dev/null and b/gradient-repeat/l9.png differ diff --git a/grayscale.html b/grayscale.html new file mode 100644 index 0000000..1b3d34d --- /dev/null +++ b/grayscale.html @@ -0,0 +1 @@ + Untitled
    E0E0E0
    .
    .
    .
    .
    E5E5E5
    .
    .
    .
    .
    EAEAEA
    .
    .
    .
    .
    EFEFEF
    F0F0F0
    .
    .
    .
    .
    F5F5F5
    .
    .
    .
    .
    FAFAFA
    .
    .
    .
    .
    FFFFFF
    \ No newline at end of file diff --git a/hacktests.html b/hacktests.html new file mode 100644 index 0000000..b5acda3 --- /dev/null +++ b/hacktests.html @@ -0,0 +1 @@ + Untitled
    Any workable hack will result a box the same width as this one (400px) in all browsers. Any green-tinged hack validates; any red-tinged hack does not. Apologies to the red-green colorblind among us.
    "Box Model Hack" using voice-family (validates)
    "Simplified Box Model Hack" escaping one character (validates unless character in the range a-f is escaped)
    escape-encoding a character (validates)
    // comments (does not validate)
    simple redefining of value (validates)
    \ No newline at end of file diff --git a/handheld.html b/handheld.html new file mode 100644 index 0000000..7654069 --- /dev/null +++ b/handheld.html @@ -0,0 +1,17 @@ + + + +Handheld test + + + + +

    +This text should be white on black (and boldfaced) in a handheld-device browser. +

    + + + diff --git a/helvetial.html b/helvetial.html new file mode 100644 index 0000000..32657bd --- /dev/null +++ b/helvetial.html @@ -0,0 +1,39 @@ + + + + +Helvetial + + + + +
    + +
      +
    1. A list item with one GR span and another GR span inside.
    2. +
    3. A list item with one GR span and another GR span inside.
    4. +
    + +
    + + + diff --git a/hover-before.html b/hover-before.html new file mode 100644 index 0000000..bf48747 --- /dev/null +++ b/hover-before.html @@ -0,0 +1,29 @@ + + + +Hover-Before Test + + + + +

    +This is an anchor (although not a link). +

    +

    +This is an anchor (although not a link). +

    +

    +This is an anchor (although not a link). +

    +

    +This is an anchor (although not a link). +

    + + + diff --git a/hover-gc.html b/hover-gc.html new file mode 100644 index 0000000..35d3155 --- /dev/null +++ b/hover-gc.html @@ -0,0 +1,29 @@ + + + +Safari :hover/GC test + + + + +

    +[one] test link +

    +

    +[two] test link +

    +

    +[one] test link +

    +

    +[two] test link +

    + + + diff --git a/htmlid.html b/htmlid.html new file mode 100644 index 0000000..b3fcfb3 --- /dev/null +++ b/htmlid.html @@ -0,0 +1 @@ + Untitled

    If this element is green with a silver background, then the browser recognizes (and styles based on) id values on html elements.

    \ No newline at end of file diff --git a/i/bluegrid.gif b/i/bluegrid.gif new file mode 100755 index 0000000..1ba5e7d Binary files /dev/null and b/i/bluegrid.gif differ diff --git a/i/botleft.gif b/i/botleft.gif new file mode 100755 index 0000000..9fc5d8b Binary files /dev/null and b/i/botleft.gif differ diff --git a/i/botright.gif b/i/botright.gif new file mode 100755 index 0000000..9d80d97 Binary files /dev/null and b/i/botright.gif differ diff --git a/i/gradient-repeat-reference.png b/i/gradient-repeat-reference.png new file mode 100644 index 0000000..12b7c1e Binary files /dev/null and b/i/gradient-repeat-reference.png differ diff --git a/i/graygrid.gif b/i/graygrid.gif new file mode 100755 index 0000000..e476dfa Binary files /dev/null and b/i/graygrid.gif differ diff --git a/i/multiclass.gif b/i/multiclass.gif new file mode 100755 index 0000000..3429cd2 Binary files /dev/null and b/i/multiclass.gif differ diff --git a/i/redbox.gif b/i/redbox.gif new file mode 100755 index 0000000..e556268 Binary files /dev/null and b/i/redbox.gif differ diff --git a/i/redgrid.gif b/i/redgrid.gif new file mode 100755 index 0000000..8eb6d08 Binary files /dev/null and b/i/redgrid.gif differ diff --git a/i/ruler-h.gif b/i/ruler-h.gif new file mode 100644 index 0000000..98e7f0f Binary files /dev/null and b/i/ruler-h.gif differ diff --git a/i/ruler.png b/i/ruler.png new file mode 100644 index 0000000..3a46bfc Binary files /dev/null and b/i/ruler.png differ diff --git a/i/super.gif b/i/super.gif new file mode 100755 index 0000000..c642cda Binary files /dev/null and b/i/super.gif differ diff --git a/i/test.gif b/i/test.gif new file mode 100755 index 0000000..f7f7cfe Binary files /dev/null and b/i/test.gif differ diff --git a/i/test1.gif b/i/test1.gif new file mode 100755 index 0000000..df85d28 Binary files /dev/null and b/i/test1.gif differ diff --git a/i/tester-sm.jpg b/i/tester-sm.jpg new file mode 100755 index 0000000..07aa94a Binary files /dev/null and b/i/tester-sm.jpg differ diff --git a/i/tester.jpg b/i/tester.jpg new file mode 100755 index 0000000..e990e8c Binary files /dev/null and b/i/tester.jpg differ diff --git a/i/topleft.gif b/i/topleft.gif new file mode 100755 index 0000000..00e4205 Binary files /dev/null and b/i/topleft.gif differ diff --git a/i/topright.gif b/i/topright.gif new file mode 100755 index 0000000..91665f8 Binary files /dev/null and b/i/topright.gif differ diff --git a/i/vertalign-ie51mac.gif b/i/vertalign-ie51mac.gif new file mode 100755 index 0000000..3104ff5 Binary files /dev/null and b/i/vertalign-ie51mac.gif differ diff --git a/i/vertalign-ns621mac.gif b/i/vertalign-ns621mac.gif new file mode 100755 index 0000000..119ba23 Binary files /dev/null and b/i/vertalign-ns621mac.gif differ diff --git a/i/vertalign-rijk.jpg b/i/vertalign-rijk.jpg new file mode 100755 index 0000000..ba011c7 Binary files /dev/null and b/i/vertalign-rijk.jpg differ diff --git a/i/yinyang.png b/i/yinyang.png new file mode 100644 index 0000000..3e2355b Binary files /dev/null and b/i/yinyang.png differ diff --git a/ie-freeze.html b/ie-freeze.html new file mode 100644 index 0000000..77c82b4 --- /dev/null +++ b/ie-freeze.html @@ -0,0 +1,565 @@ + + + + +Internet Explorer Freezes -- BEWARE! + + + + + + + + + + + + + +
    + + + + + +
    +Warning: this page will freeze Internet Explorer for Windows! In the embedded style sheets, there are lines marked in a CSS comment with the string "[FREEZER]". Removing the indicated declaration from either one will avoid the freeze bug in IE/Win. Leaving them both in will cause it to freeze, requiring a force-quit of the application in order to get the computer back. This freezing has been observed under Windows 98, Windows 2000 Professional, and Windows XP. +
    + +
    + + +

    Ten Things To Do In Cleveland Before You’re Dead

    +
    Tuesday, 14 September 2004 :: 1154 EDT | Cleveland
    + +

    + +I quick-linked 10 Things to Do in Cleveland Before You Die, but the more I looked at the list, the less happy it made me. So I’ve decided to compile my own list. Note that this list doesn’t include restaurants. As much as I love to eat, I just don’t think that a single meal is worthy of a “things to do before you’re dead” list, no matter how amazing the meal. I might compile a separate “Ten Places to Eat In Cleveland” list, but that’s a subject for another day. + +

    + + + +
      + +
    1. + +Hear the Cleveland Orchestra. + +

      + +Not on CD, you goof—anyone can do that. Hear them perform live and in person at least once in your life. Odds are you’ll want to make it more than once, given that they’re one of the best orchestras in the world. Bonus points for seeing them at Blossom Music Center, followed by a fireworks display. + +

      + +
    2. + +
    3. + +Tour the cultural institutions of University Circle. + +

      + +That includes the Cleveland Museum of Art; the Cleveland Museum of Natural History, which includes the Shafran Planetarium; the Western Reserve Historical Society, which includes the Crawford Auto-Aviation Museum; and the Cleveland Botanical Gardens, all within a quarter-mile radius. Included in that grouping is Severance Hall, home of the Cleveland Orchestra. This one’s kind of a cheat, since if I mentioned them all separately that would make this a “Top 15 Things To Do” list, which for some reason doesn’t sound as interesting. + +

      + +
    4. + +
    5. + +Spend a day at the Cleveland Metroparks. + +

      + +Known as the “Emerald Necklace", the extensive park system (20,000 acres in 14 reservations) not only girds the city but also runs throughout the greater metropolitan area. There are hiking trails, picnic areas, educational events, and a whole lot more, including the Cleveland Metroparks Zoo. + +

      + +
    6. + +
    7. + +Tour the Rock and Roll Hall of Fame. + +

      + +The real joy is in the smaller cases, where you can find original lyrics sheets to landmark songs complete with scratched-out ideas and arrows marking rearrangements, bills for hotel-room damage, and other tidbits. The architecture of the building is fascinating as well. + +

      + +
    8. + +
    9. + +Visit the West Side Market. + +

      + +Besides the dozens of fruit and vegetable stalls in the outside promenade, the interior market space is filled with local butchers, bakers, and other amazing treats. Come early on Saturday morning for the best selection. + +

      + +
    10. + +
    11. + +Spend Labor Day weekend downtown. + +

      + +That’s where and when you’ll find the Taste of Cleveland, a great way to sample various cuisines, while the aerial displays of the Cleveland National Air Show, based not half a mile away, soar overhead. (Assuming the FAA relaxes its restrictions on such flights near sporting events, that is.) If you stick around until nightfall, you’ll have a perfect excuse to go party in the Flats, too. + +

      + +
    12. + +
    13. + +Hit one of the amusement parks. + +

      + +Technically these aren’t in Cleveland itself, but they’re close enough to warrant inclusion. About forty minutes southeast of downtown is Geauga Lake (formerly Six Flags Worlds of Adventure), a combination amusement park and water park. Just over an hour west of downtown, you’ll find Cedar Point, one of the nation’s premiere amusements parks and the roller coaster capital of the world. + +

      + +
    14. + +
    15. + +Go sailing on Lake Erie. + +

      + +Whether you take out a two-man boat or take a dinner cruise on the Good Time III, it’s worth seeing the city from the water. Even better, if you’re captain of your own boat, you can sail to one of the islands or head west along the shoreline to Cedar Point. + +

      + +
    16. + +
    17. + +See a game. + +

      + +With three major-league teams (the Indians, Browns, and Cavaliers) playing downtown, if you’re a sports fan, you’ll find a game to watch. There are a number of other teams in town as well, including the Barons (hockey) and the Force (soccer). + +

      + +
    18. + +
    19. + +Drop by Lakeview Cemetery. + +

      + +Do it while you’re still alive, okay? You’ll not only get great views of the city, but also see artistic, beautiful monuments to James A. Garfield, John D. Rockefeller, Eliot Ness, and others. The Wade Chapel, situated on the shores of a pond, features an interior designed by Louis Comfort Tiffany and full of the famous glasswork bearing his name. Who knows? Maybe you’ll find a place to rest after you’re dead. + +

      + +
    20. + +
    + +

    + +I have to be honest and admit that I haven’t even done everything on my own list. However, I suspect that as our kids grow up, we’ll do all of those things more than once. + +

    + + + +

    1 Response +» +

    + +
    +
      +
    • http://www.meyerweb.com/eric/thoughts/2004/09/14/ten-things-to-do-in-cleveland-before-youre-dead/trackback/
    • +
    • Comments RSS feed
    • +
    +
    + +
      +
    1. +

      You are from Cleveland??? +

      +

      Comment by Mark | Tuesday, 14 September 2004 :: 1258 EDT

      +
    2. + +
    + + +

    Leave a comment

    +
    +
    +

    + + + + +

    + +

    + + +

    + +

    + + +

    +
    +

    Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

    +
    +

    + +
    + +

    +

    + Remember to encode character entities if you're posting markup examples! Management reserves the right to edit or remove any comment—especially those that are abusive, irrelevant to the topic at hand, or made by anonymous posters—although honestly, most edits are a matter of fixing mangled markup. Thus the note about encoding your entities. If you're satisfied with what you're written, then go ahead... +

    +

    + +

    + +
    + + + +
    +
    + +
    +
    + + + +
    +

    Exploration

    +
    + + + + +(Powered by Google) +
    +
    + + + +
    +

    Feeds

    + +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    September 2004
    SMTWTFS
    August 
     1234
    567891011
    12131415161718
    19202122232425
    2627282930 
    + + +
    + + + + \ No newline at end of file diff --git a/image-box.html b/image-box.html new file mode 100644 index 0000000..d2c2d56 --- /dev/null +++ b/image-box.html @@ -0,0 +1 @@ + Image Padding?
    \ No newline at end of file diff --git a/img-table-test-2.html b/img-table-test-2.html new file mode 100644 index 0000000..2d09735 --- /dev/null +++ b/img-table-test-2.html @@ -0,0 +1 @@ + IMG-Table test
    \ No newline at end of file diff --git a/img-table-test.html b/img-table-test.html new file mode 100644 index 0000000..fc09bb9 --- /dev/null +++ b/img-table-test.html @@ -0,0 +1 @@ + IMG-Table test
    \ No newline at end of file diff --git a/img-table-zeldman-test.html b/img-table-zeldman-test.html new file mode 100644 index 0000000..899e747 --- /dev/null +++ b/img-table-zeldman-test.html @@ -0,0 +1 @@ + Jeffrey Zeldman Presents: The Daily Report
     
    MY GLAMOROUS LIFE: Tragicomic fodder from the life of Zeldman. A LIST APART: Design, code, content. For people who make websites. LES MISC: Articles, essays, and miscellanies. TAKING YOUR TALENT TO THE WEB: A Guide for the Transitioning Designer.
    DAILY REPORT: Web design news for your pleasure.
    STEAL THESE GRAPHICS: Free art for your desktop or personal site. FUN HOUSE: Entertainment for you. ASK DR WEB: Tips for web designers. Since 1995. 15 MINUTES: Interviews with movie stars and cyberstars, 1996-1999.
    Happy Cog.

    Current ALA: Time Management: The Pickle Jar Theory
    Current Relaunch: Happy Cog Studios
    Recent Glamour: Life During Wartime
    Recent Essentials (clickety-click)

    25–26 June 2002
    [10 am | 10 am]
    Porter Glendinning sent us this screen capture of webstandards.org as seen in his Palm Pilot. Worth noting: The Web Standards Project is built with XHTML 1.0 Strict. CSS is used for layout. There is no Palm version. There is no WAP version. Multiple versions are not needed. When you design and build with standards, one document serves all. Thanks, Porter.

    Similarly: Here’s how The WaSP’s site looks in Microsoft’s PocketPC. (Thanks, Anil.) Again, no special version was required or built.

    But wait, there’s more. Care of Grant Hutchinson, here’s the same site on a Newton, Apple’s long-discontinued predecessor to the Palm Pilot. “There’s nothing like viewing a modern site using a piece-meal browser on a vintage operating system.”

    The bad news: even the latest versions of certain off-brand browsers deliver incorrect and incomplete support for CSS, and no support at all for the W3C DOM. Folks who use these browsers will have inferior experiences on sites built with anything beyond HTML table layouts and 1997-era JavaScript. This may not bother you or your clients, but it will certainly distress these users.
            Take OmniWeb. Please. As screenshots prepared by Waferbaby show, the newly released OmniWeb 4.1 fares reasonably well with transitional layouts like the one used at zeldman.com. OmniWeb fudges some CSS layouts without impairing usability: Waferbaby’s navigation bar explodes on impact, and ALA’s leading and borders are missing, but both sites can still be read.
            The WaSP’s new site fares worse. Among other woes, its left-side navigation is almost entirely hidden. It may seem odd that a site so friendly to Palm users could prove so troublesome to a fancy-pants graphical browser like OmniWeb, but that’s how it is when browsers meet a web standard halfway. No CSS is better than incomplete and incorrect CSS. We can only hope that Omni Group will continue to improve its promising but problematic product.

    Likewise, here’s a snap of webstandards.org in iCab 2.8, a Mac-only browser that claims to offer standards support comparable to that in IE and Opera. (To be fair, iCab’s has always provided superb support for HTML. Which may not sound like much, but is. It’s those other standards iCab still needs to work on.) Thanks, Eric. :::

    23–24 June 2002
    In Issue 146 of A List Apart, For People Who Make Websites: Time management theories come and go, and we’re glad when most of them leave. But this one caught our fancy. No charts, no grids, no five syllable words — just a simple idea that can help you get more done with less stress. New ALA contributing writer Jeremy Wright uncorks the Pickle Jar Theory of Time Management.

    Monkey.

    Stilleye offers scripts you can download and use on your own sites. Includes expanding menus, a pixelated text generator, and a fix for MSIE’s automatic margin bug.

    Of late we’ve found ourselves bemusedly contemplating the abstract thoughts and equally abstract layouts of WebActivism.

    SDG, a newly launched web agency, has taken WaSP’s challenge to heart, and will offer its clients only standards-compliant work. The agency’s corporate site complies with XHTML 1.0 Transitional, CSS, and the Section 508 guidelines, and is not a bad looker.

    Recent essentials you may have missed: “Flash Player 6 & broken detection scripts” covers a problem on numerous Flash-based sites, where old browser detection scripts prevent visitors who’ve installed the Flash 6 player from viewing Flash content. “Dingbats instead of text” explores an MSIE problem in which text on web pages shows up as visual symbols instead of words. :::

    The author and his opinions.
    Over [counter] served!   Copyright © 1995–2002 Jeffrey Zeldman Presents.
    XHTML, CSS, 508.  Reset bookmarks to www.zeldman.com. Ahead Warp Speed.


    \ No newline at end of file diff --git a/imgborder.html b/imgborder.html new file mode 100644 index 0000000..e279107 --- /dev/null +++ b/imgborder.html @@ -0,0 +1 @@ + border-color tests \ No newline at end of file diff --git a/import-basic1.css b/import-basic1.css new file mode 100644 index 0000000..c5d39e8 --- /dev/null +++ b/import-basic1.css @@ -0,0 +1 @@ +h1 {color: green;} \ No newline at end of file diff --git a/import-basic2.css b/import-basic2.css new file mode 100644 index 0000000..d90d477 --- /dev/null +++ b/import-basic2.css @@ -0,0 +1 @@ +h2 {color: green;} \ No newline at end of file diff --git a/import-test.html b/import-test.html new file mode 100644 index 0000000..612eddb --- /dev/null +++ b/import-test.html @@ -0,0 +1 @@ + Untitled

    This is an h1

    This is an h2

    \ No newline at end of file diff --git a/important.html b/important.html new file mode 100644 index 0000000..da27fdc --- /dev/null +++ b/important.html @@ -0,0 +1,27 @@ + + + +Important Test + + + + +

    +[.c1] A paragraph. +

    +

    +[.c2] A paragraph. +

    +

    +[.c1] A paragraph with inline style. +

    +

    +[.c2] A paragraph with inline style. +

    + + + diff --git a/inlinespec.html b/inlinespec.html new file mode 100644 index 0000000..6428e5d --- /dev/null +++ b/inlinespec.html @@ -0,0 +1 @@ + Inline Specificity

    The specification says this paragraph should be green instead of red. If it is red, it has honored an inline style with lower specificity than an embedded style which applies to the same element.

    \ No newline at end of file diff --git a/jon_test_nn6.htm b/jon_test_nn6.htm new file mode 100755 index 0000000..4c56a65 --- /dev/null +++ b/jon_test_nn6.htm @@ -0,0 +1 @@ + Jon Test for NN4 - show/hide layers
    jon1 jon2 jon3 jon4 jon5

     

    1 Container Jon 1 ..........

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit a

    2 Container Jon 2..........

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit a

    3 Container Jon 3..........

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit a

    4 Container Jon 4..........

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit a

    5 Container Jon 5..........

    Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit a

    \ No newline at end of file diff --git a/line-height-strut.html b/line-height-strut.html new file mode 100644 index 0000000..6fd29ff --- /dev/null +++ b/line-height-strut.html @@ -0,0 +1,39 @@ + + + +Line-height struts(?) + + + + +
    + +
    + +
    + + +
    + +
    + + +
    + +
    +   + +
    + +
    + . + +
    + + + diff --git a/line-height/bigtext-spans.html b/line-height/bigtext-spans.html new file mode 100644 index 0000000..f82e0f2 --- /dev/null +++ b/line-height/bigtext-spans.html @@ -0,0 +1,59 @@ + + + +Line-height Testing + + + + +
    +
    +Super Big Text Is Testy Of Height +
    +
    + +
    +
    +Super Big Text Is Testy Of Height +
    +
    + +
    +
    +Super Big Text Is Testy Of Height +
    +
    + + + + diff --git a/line-height/inspect-multi.html b/line-height/inspect-multi.html new file mode 100644 index 0000000..ee62e4a --- /dev/null +++ b/line-height/inspect-multi.html @@ -0,0 +1,193 @@ + + + +Line-height Testing + + + + + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Font face + + + +
    Height of line boxnormal equivalent
    10px--
    25px--
    50px--
    100px--
    1000px--
    10000px--
    + +
    + + +
    +
    Oy!
    +
    Oy!
    +
    Oy!
    +
    Oy!
    +
    Oy!
    +
    Oy!
    +
    + + + + diff --git a/line-height/ruler.gif b/line-height/ruler.gif new file mode 100644 index 0000000..eef32af Binary files /dev/null and b/line-height/ruler.gif differ diff --git a/line-height/stripes.gif b/line-height/stripes.gif new file mode 100644 index 0000000..ddcf7c7 Binary files /dev/null and b/line-height/stripes.gif differ diff --git a/link-click.html b/link-click.html new file mode 100644 index 0000000..298e93e --- /dev/null +++ b/link-click.html @@ -0,0 +1,22 @@ + + + +Bare :empty + + + + + +

    +

    + + + diff --git a/list-indent-cases.html b/list-indent-cases.html new file mode 100644 index 0000000..4a84f70 --- /dev/null +++ b/list-indent-cases.html @@ -0,0 +1 @@ + List Indentation Cases
    • item 1
    • item 2
    • item 3
    • item 1
    • item 2
    • item 3
    • item 1
    • item 2
    • item 3
    • item 1
    • item 2
    • item 3
    • item 1
    • item 2
    • item 3
    • item 1
    • item 2
    • item 3
    \ No newline at end of file diff --git a/macie5/shifted-links.html b/macie5/shifted-links.html new file mode 100644 index 0000000..b6bdd65 --- /dev/null +++ b/macie5/shifted-links.html @@ -0,0 +1 @@ + Shifted Link Weirdness

    Shifted Link Weirdness

    If you're running IE5/Mac, run your mouse over the three links (which point to nothing) and notice the change in mouse pointer and, in some cases, the hover/rollover effects. Now move the mouse pointer over the left side of each table cell, and see the same thing happen. You can also watch the URLs appear in the status bar at the bottom of the browser window, assuming you didn't turn it off. If you click in that blank space at the left side of the table cell, the hyperlink will be selected. Try it, it's cool.

    This link is HTML-aligned to the right.
    This link is CSS-aligned to the right.
    \ No newline at end of file diff --git a/macie5/smallcap.html b/macie5/smallcap.html new file mode 100644 index 0000000..5f07fa9 --- /dev/null +++ b/macie5/smallcap.html @@ -0,0 +1 @@ + Untitled

    Now is the Time for All Good Men to Come to the Aid of their Country.

    Now is the Time for All Good Men to Come to the Aid of their Country.


    Now is the Time for All Good Men to Come to the Aid of their Country.

    Now is the Time for All Good Men to Come to the Aid of their Country.


    Now is the Time for All Good Men to Come to the Aid of their Country.

    Now is the Time for All Good Men to Come to the Aid of their Country.

    Now is the Time for All Good Men to Come to the Aid of their Country.

    \ No newline at end of file diff --git a/macie5/table-border.html b/macie5/table-border.html new file mode 100644 index 0000000..0762acc --- /dev/null +++ b/macie5/table-border.html @@ -0,0 +1 @@ + Border strangeness
    \ No newline at end of file diff --git a/macie5/vertical.html b/macie5/vertical.html new file mode 100644 index 0000000..14cedc5 --- /dev/null +++ b/macie5/vertical.html @@ -0,0 +1 @@ + Vertical Ascent

    Hey look, it's superscripted text. And how!

    \ No newline at end of file diff --git a/margin04.htm b/margin04.htm new file mode 100755 index 0000000..be03f26 --- /dev/null +++ b/margin04.htm @@ -0,0 +1 @@ + Untitled

    Opera 6.0

    If you define margins for paragraphs with CSS then float an image within a paragraph, the image breaks out of the paragraph block both top and bottom. If you use the system defaults for paragraphs, Opera behaves as expected. Also, try putting a border on the paragraph in CSS, see what happens.

    \ No newline at end of file diff --git a/margin04b.htm b/margin04b.htm new file mode 100755 index 0000000..25dc55e --- /dev/null +++ b/margin04b.htm @@ -0,0 +1 @@ + Untitled

    Opera 6.0

    If you define margins for paragraphs with CSS then float an image within a paragraph, the image breaks out of the paragraph block both top and bottom. If you use the system defaults for paragraphs, Opera behaves as expected. Also, try putting a border on the paragraph in CSS, see what happens.

    \ No newline at end of file diff --git a/medium-font.html b/medium-font.html new file mode 100644 index 0000000..1182a62 --- /dev/null +++ b/medium-font.html @@ -0,0 +1,39 @@ + + + + +Monospace Font Sizing + + + + + +show body size + + +
    A serif div.
    +
    A sans-serif div.
    +
    A monospace div.
    +
    A cursive div.
    +
    A fantasy div.
    + + + diff --git a/monospaced3.html b/monospaced3.html new file mode 100644 index 0000000..83ed98c --- /dev/null +++ b/monospaced3.html @@ -0,0 +1,56 @@ + + + + +Monospace Font Sizing + + + + +
    +

    (inline tests)

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +
    + +
    +

    (inline tests — alternate ordering, no 'serif' tests)

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +

    This a 'p' element with a 'span' element contained within.

    +
    + + + diff --git a/moz/w3css/banner-k.css b/moz/w3css/banner-k.css new file mode 100644 index 0000000..6558ad2 --- /dev/null +++ b/moz/w3css/banner-k.css @@ -0,0 +1 @@ +/* Like banner.css, but with different color. * Use for special pages. * * Author: Bert Bos * Created: 26 July 2000 * Version: $Id: banner-k.css,v 1.4 2001/08/31 13:39:05 bbos Exp $ */ @import "http://www.w3.org/Style/banner.css"; /* Override the colors */ div.banner p { background: url(semi8x8.gif) transparent; border-color: #025c7f } div.banner a, div.banner em { border-top-color: #025c7f } /* Hide from NS4 (there is a higher-specificity rule in banner.css) */ div.banner { display: none } div.banner a:hover { background: white; color: black } \ No newline at end of file diff --git a/moz/w3css/banner-k2.css b/moz/w3css/banner-k2.css new file mode 100644 index 0000000..c48fe85 --- /dev/null +++ b/moz/w3css/banner-k2.css @@ -0,0 +1 @@ +/* Like banner.css, but with different color. * Use for special pages. * * Author: Bert Bos * Created: 26 July 2000 * Version: $Id: banner-k.css,v 1.4 2001/08/31 13:39:05 bbos Exp $ */ @import "http://www.w3.org/Style/banner.css"; /* Override the colors */ div.banner p { background: url(semi2x2b.gif) transparent; border-color: #025c7f } div.banner a, div.banner em { border-top-color: #025c7f } /* Hide from NS4 (there is a higher-specificity rule in banner.css) */ div.banner { display: none } div.banner a:hover { background: white; color: black } \ No newline at end of file diff --git a/moz/w3css/banner-k3.css b/moz/w3css/banner-k3.css new file mode 100644 index 0000000..0c69338 --- /dev/null +++ b/moz/w3css/banner-k3.css @@ -0,0 +1 @@ +/* Like banner.css, but with different color. * Use for special pages. * * Author: Bert Bos * Created: 26 July 2000 * Version: $Id: banner-k.css,v 1.4 2001/08/31 13:39:05 bbos Exp $ */ @import "http://www.w3.org/Style/banner.css"; /* Override the colors */ div.banner p { background: url(semi8x8.png) transparent; border-color: #025c7f } div.banner a, div.banner em { border-top-color: #025c7f } /* Hide from NS4 (there is a higher-specificity rule in banner.css) */ div.banner { display: none } div.banner a:hover { background: white; color: black } \ No newline at end of file diff --git a/moz/w3css/main.css b/moz/w3css/main.css new file mode 100644 index 0000000..60be91a --- /dev/null +++ b/moz/w3css/main.css @@ -0,0 +1 @@ +@import "hints.css"; BODY { color: #000; /* background: #FBFBFF; */ background: #FFE; margin-left: 5%; margin-right: 8.5em; font-family: "Helvetica", sans-serif; /* line-height: 1.35; */ /* This would break MacIE 3 */ } TD, TH { /* ns workaround */ font-family: "Helvetica", sans-serif; line-height: 1.35; } H1 { margin-left: -5%; margin-bottom: 2em; font-size: large; } H1, H2 { font-weight: bold } H1, H2, H3 { color: #900; line-height: 1 } H1:first-line { color: #000 } .logo { float: left; } DIV.endmatter { /*margin-left: -5%;*/ margin-right: -6em } A:link { color: #009; /* border: none -- breaks NS 4.x */ } A:visited, A:active { color: #906; /* border: none -- breaks NS 4.x */ } A:link IMG, A:visited IMG { border-style: none } A IMG { color: white } /* The only way to hide the border in NS 4.x */ .hide { display: none; color: white; } SPAN.date { font-size: 0.8em } SPAN.attribution { font-weight: bold } BLOCKQUOTE { margin-left: 4em; margin-right: 4em; margin-top: 0.8em; margin-bottom: 0.8em; font-style: italic; /* color: #990; */ } ADDRESS { text-align: right; font-weight: bold; font-style: italic } BLOCKQUOTE P { /* Try to avoid space above the attribution */ margin-bottom: 0; } BLOCKQUOTE ADDRESS { margin: 0; } .motto, .motto A {font: italic 120%/1.3 Georgia, serif; color: #990} .emphasized { font-weight: bold } /* Why o why does this break Netscape 4.x? IMG { border: none } */ P.map-also { font-style: italic; margin-left: 15%; text-align: right } UL, OL, LI { /*margin-left: 0;*/ list-style: disc } P + P { text-indent: 1.5em; margin-top: 0 } P.hint + P, P.alt-hint + P { text-indent: 0; margin-top: 1em } P { margin-top: 1em; margin-bottom: 0 } UL, OL { margin-top: 0.5em } PRE { margin: 1em 0 1em 1.5em; color: #603 } P.remark {font-size: smaller} \ No newline at end of file diff --git a/moz/w3css/map-ns.css b/moz/w3css/map-ns.css new file mode 100644 index 0000000..043947f --- /dev/null +++ b/moz/w3css/map-ns.css @@ -0,0 +1 @@ +/* Author: Bert Bos (Adapted from work by Hkon Wium Lie) Created: 17 August 1999 Version: $Revision: 1.9 $ The following section creates a set of partially overlapping headlines in different colors and font families. Negative margin values must be set on block-level elements to have an effect - in this document P elements are used and the selectors are named '#p*'. The source will look like this:

    ...

    ...

    ...

    ...
    The following works more or less, but see map.css for a better way. */ /* DIV.map {margin: 140px -7% 4em 0; clear: both} */ DIV.map {margin: 2em -6em 4em 0; padding: 0; clear: both} #p1, #p2, #p3, #p4, #p5, #p6, #p7, #p8, #p9, #p10 {white-space: nowrap} #p1, #p2, #p3, #p4, #p5, #p6, #p7, #p8, #p9, #p10 {text-indent: 0} #p1 A, #p2 A, #p3 A, #p4 A, #p5 A, #p6 A, #p7 A, #p8 A, #p9 A, #p10 A {text-decoration: none} #p1, #p1 A {color: #DDD; font: 100px/20px "Impact", sans-serif} #p2, #p2 A {color: #000; font: italic 40px/20px "Georgia", serif} #p3, #p3 A {color: #080; font: 40px/20px "Verdana", sans-serif} #p4, #p4 A {color: #37F; font: bold 40px/20px "Courier New", "Courier", monospace} #p5, #p5 A {color: #F73; font: bold 100px/20px "Verdana", sans-serif} #p6, #p6 A {color: #22A; font: bold 25px/20px "Verdana", sans-serif} #p7, #p7 A {color: #088; font: italic 80px/20px "Verdana", sans-serif} #p8, #p8 A {color: #088; font: italic 20px/20px "Verdana", sans-serif} #p9, #p9 A {color: #088; font: italic 20px/20px "Verdana", sans-serif} #p10, #p10 A {color: #F73; font: bold 60px/20px "Verdana", sans-serif} #p1 {text-align: right; margin: 0 0 0 0} /* top right */ #p2 {text-align: left; margin: 50px 0 0 5%} /* top left */ #p3 {text-align: center; margin: 110px 0 0 0} /* center */ #p4 {text-align: right; margin: 35px 0 0 0} /* center right */ #p5 {text-align: left; margin: 120px 0 0 0} /* center left */ #p6 {text-align: center; margin: 100px 0 0 0} /* bottom center */ #p7 {text-align: right; margin: 60px 0 0 0} /* bottom right */ #p8 {text-align: left; margin: -10px 0 0 3%} /* bottom left */ #p9 {text-align: right; margin: 0px 0 0 0} /* bottom right */ #p10 {text-align: left; margin: 10px 0 0 0} /* center left */ \ No newline at end of file diff --git a/moz/w3css/map.css b/moz/w3css/map.css new file mode 100644 index 0000000..928a005 --- /dev/null +++ b/moz/w3css/map.css @@ -0,0 +1 @@ +/* Author: Bert Bos (Adapted from work by Hkon Wium Lie) Created: 17 August 1999 Version: $Revision: 1.10 $ The following section creates a set of partially overlapping headlines in different colors and font families. Negative margin values must be set on block-level elements to have an effect - in this document P elements are used and the selectors are named '#p*'. The source will look like this:

    ...

    ...

    ...

    ...
    This works by setting an offset from the bottom of the link area. The height of the line plus the bottom margin are equal to the top margin, so the line doesn't contribute to the height of its parent in any way. */ DIV.map { /* Reserve some room for the links */ padding-top: 190px; margin-left: -4%; margin-right: -6em; /* width: 100%; */ margin-bottom: 4em; margin-top: 5em; clear: both; text-shadow: 0.2em 0.2em /* 0.2em */ silver; } #p1, #p2, #p3, #p4, #p5, #p6, #p7, #p8, #p9, #p10 {white-space: nowrap} #p1, #p2, #p3, #p4, #p5, #p6, #p7, #p8, #p9, #p10 {text-indent: 0} #p1 A, #p2 A, #p3 A, #p4 A, #p5 A, #p6 A, #p7 A, #p8 A, #p9 A, #p10 A {text-decoration: none} #p1, #p1 A {color: #DDD; font: 100px/1 "Impact", "Helvetica Narrow", sans-serif} #p2, #p2 A {color: #000; font: italic 40px/1 "Georgia", serif} #p3, #p3 A {color: #080; font: 40px/1 "Verdana", sans-serif} #p4, #p4 A {color: #37F; font: bold 40px/1 "Courier New", "Courier", monospace} #p5, #p5 A {color: #F73; font: bold 100px/1 "Verdana", sans-serif} #p6, #p6 A {color: #22A; font: bold 25px/1 "Verdana", sans-serif} #p7, #p7 A {color: #088; font: italic 80px/1 "Verdana", sans-serif} #p8, #p8 A {color: #088; font: italic 20px/1 "Verdana", sans-serif} #p9, #p9 A {color: #088; font: italic 20px/1 "Verdana", sans-serif} #p10, #p10 A {color: #F73; font: bold 60px/1 "Verdana", sans-serif} #p1 {text-align: right; margin: -185px 0 85px 0} /* top right */ #p2 {text-align: left; margin: -190px 0 150px 5%} /* top left */ #p3 {text-align: right; margin: -87px 35% 47px 0} /* center */ #p4 {text-align: right; margin: -98px 0 58px 0} /* center right */ #p5 {text-align: left; margin: -130px 0 30px 0} /* center left */ #p6 {text-align: left; margin: -40px 0 15px 35%} /* bottom center */ #p7 {text-align: right; margin: -80px 0 0px 0} /* bottom right */ #p8 {text-align: left; margin: -40px 0 20px 3%} /* bottom left */ #p9 {text-align: right; margin: -25px 0 5px 0} /* bottom right */ #p10 {text-align: left; margin: -130px 0 70px 0} /* center left */ \ No newline at end of file diff --git a/moz/w3css/semi16x16.gif b/moz/w3css/semi16x16.gif new file mode 100755 index 0000000..514f80d Binary files /dev/null and b/moz/w3css/semi16x16.gif differ diff --git a/moz/w3css/semi2x2b.gif b/moz/w3css/semi2x2b.gif new file mode 100755 index 0000000..49de557 Binary files /dev/null and b/moz/w3css/semi2x2b.gif differ diff --git a/moz/w3css/semi2x2b.png b/moz/w3css/semi2x2b.png new file mode 100755 index 0000000..8fe0d97 Binary files /dev/null and b/moz/w3css/semi2x2b.png differ diff --git a/moz/w3css/semi8x8.gif b/moz/w3css/semi8x8.gif new file mode 100755 index 0000000..c55ebae Binary files /dev/null and b/moz/w3css/semi8x8.gif differ diff --git a/moz/w3css/shadows.css b/moz/w3css/shadows.css new file mode 100644 index 0000000..52342f3 --- /dev/null +++ b/moz/w3css/shadows.css @@ -0,0 +1 @@ +/* Style for sections with drop shadows * * Assumes that sections are marked-up like this: * *
    *
    *

    Heading

    * ... *
    *
    * * Default color is red (same as banner-o) * * Author: Bert Bos * Created: 24 Aug 2001 * Version: $Id: shadows.css,v 1.7 2001/08/31 13:46:20 bbos Exp $ */ div.back { clear: both; page-break-before: always; margin: 3em -0.75em 3em 1em; padding: 1.5em; } /* I'd like to use background: transparent url(semi4x4.png) but semi-transparent backgrounds seem to slow down the various browsers a lot... */ div.back {background: #567} div.section div.back {background: #777} /* border-radius is not a CSS property, but a proposal for CSS3. * Mozilla has implemented it in an experimental fashion, which is used * here to show the expected effect in the future. */ div.back, div.section { border-radius: 4em 2em; -moz-border-radius: 4em; } div.section { background: #FBFBFF; margin: -3em 0 0 -3em; padding: 1.5em; border: thin solid #999; } h1 { color: black; line-height: 1 } h1:first-line { color: #025c7f } h2 { color: black; text-shadow: 1px 1px black; text-align: right; font-variant: small-caps; font-weight: bold; margin-top: 0; font-size: 140% /*200%*/; } h3 { color: black; font-size: 100%; font-weight: normal; font-variant: small-caps; text-align: right; } body { line-height: 1.4; background: #9bd; font-size: medium; margin-right: 6.5em; } div.section a:link, div.section a:visited { color: inherit; font-style: italic; text-decoration: underline; } /* Should be a:visited:hover, a:link:hover but Opera Linux doesn't support that yet */ a:hover { background: #CF9; } \ No newline at end of file diff --git a/moz/w3css/style-css2.html b/moz/w3css/style-css2.html new file mode 100644 index 0000000..22a7e42 --- /dev/null +++ b/moz/w3css/style-css2.html @@ -0,0 +1 @@ + Cascading Style Sheets

    Cascading Style Sheets
    home page

    (This page uses CSS style sheets)

    Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g. fonts, colors, spacing) to Web documents. For background information on style sheets, see the Web style sheets resource page. Discussions about CSS are carried out on the (archived) www-style@w3.org mailing list and on comp.infosystems.www.authoring.stylesheets.

    What's new?

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010627 Westciv offers a 12-week, online CSS1 course, starting 25 June 2001. (Free if followed in real time.)
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 010613 WestCiv has released Layout Master, a program to design page layouts in HTML/CSS2 by drag & drop. (Mac, Windows forthcoming)
    • 010530 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows. Includes support for Netscape 6, IE 6 and Opera 5. (Shareware)
    • 010523 Westciv published version 3 of their online CSS guide, covering all of CSS2 as well as browser compatibility issues. (Free online, enhanced version for sale.)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market. Evaluation download available, registration required.
    • 010427A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010323 Westciv is offering online courses, which you can follow for free on their site or buy. HTML/XHTML starts now, CSS1 will follow in June.
    • 010220 The Browser upgrade initiative of the WaSP (Web Standards Project) aims to rid the world of old, non-standards compliant browsers that hold back progress.
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are beta versions for EPOC. Shareware.
    • 010130 W3Schools is a site with tutorials on many Web technologies, including CSS.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 010113 A page from the tutorial of the Morphon XML editor (see below) explains why CSS is a good choice for XML.
    • 001211 The Zvon site has published a complete CSS2 reference with examples. Also on that site: the CSS1 reference by Miloslav Nic is an index to the CSS1 spec by property name, enhanced with examples. There is also a tutorial on CSS for XML.
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)

    Something to add? Let me know!

    Learning CSS

    Tutorials

    For a quick introduction, try chapter 2 of Lie & Bos, or Dave Raggett's intro to CSS. Or see examples of styling XML and CSS tips & tricks.

    Books

    A selection of books on CSS:

    CSS online resources

    Some non-English resources:

    English resources:

    Secondary resources, i.e., resources that catalogue links to other resources. (Which makes this list a tertiary resource… )

    CSS Browsers

    The easiest way to start experimenting with style sheets is to download one of the browsers that support CSS1. Not all of the browsers below implement the full specification, but releases are coming out fast so this should soon change.

    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market.
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are betas of version 5 for EPOC. BeOS version is 3.62. Shareware.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 000815 NetClue Corp. released the Clue browser 3.0, a Java component with support for CSS1, DOM and Javascript.
    • 000327 Microsoft shipped Internet Explorer 5 for the Macintosh. It apparently supports full CSS1, the first browser to do so.
    • 991202 Closure is a Web browser written in Common Lisp; supports CSS1.
    • 991022 Hewlett Packard released their "embedded microbrowser" ChaiFarer, supporting CSS1. CSS2 will come later.
    • 990924 ICE Soft released v.5 of their two embeddable browsers: the "base" one is a viewer for HTML/XML+CSS2, the "pro" one adds networking and more. Both in Java. Does MathML, too.
    • 990412 Microsoft has released Internet Explorer 5.0 for Windows, Solaris and HP-UX
    • Silicon Graphics has an embeddable CSS-enhanced web browser that is used in a number of applications and their desktop
    • Amaya is W3C's Web client that is both a browser and an authoring tool. It has partial (but growing) support for CSS1.
    • Arena, previously W3C's testbed browser, is now being developed by Yggdrasil. It has a partial implementation of CSS1.
    • Emacs-w3, a.k.a. Gnuscape Navigator, supports some CSS1.

    These sources document the level of support in various browsers:

    CSS Authoring Tools

    Currently, most Web Authoring tools provide some sort of support for CSS style sheets. A ZDnet article described some of them. The list below is far from complete, but contains (in chronological order) all tools that have been reported to us.

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 001101 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)
    • 000928 Software602 has an office suite 602 Pro Suite for Windows that can edit HTML+CSS (freeware).
    • 000802 Lunatech Research has released beta version 7 of the Morphon XML editor, which includes a CSS editor. Written in Java.
    • 000704 AceHTML 4 by Visicom Media is an HTML/CSS editor for Windows. Both commercial and freeware versions are available.
    • 991217 Justsystem (also in English) has released their Java-based, multi-lingual wordprocessor ICHITARO Ark. It uses HTML/CSS as its native format (screenshot).
    • 991119 Bluefish is an OpenSource HTML editor for Unix with support for CSS1.
    • 991026 Amaya, W3C's Web client that is both a browser and an authoring tool, is in version 2.2.
    • 990807 Cascade and Cascade Light are CSS editors for the Mac.
    • 990804 En Vogue is a (non-WYSIWYG) editor running on the Atari ST. It supports CSS1 & 2.
    • 990529 SoftQuad's XMetaL authors & displays XML documents with CSS style sheets.
    • 990525 CorelDraw 9 exports HTML + CSS.
    • 980929 SoftQuad's HoTMetaL PRO 5.0 authors, as well as displays, CSS and HTML.
    • 980829 W3CSS is in a new release.
    • 980829 Prime Style has become a shareware product and versions 2.0 is now available.
    • 980826 StyleOne is an easy-to-use CSS editor to create Web pages.
    • 980312 CSS Mill by Patrick Corcoran is a visual tool for generating CSS styled HTML.
    • 980115 Lewis Gartenberg has released a shareware tool, W2CSS which converts MS Word documents into HTML and CSS.
    • 971216 EDF has released CSSize, a tool which helps you convert HTML documents into HTML+CSS documents.
    • 971216 Hexmac has released HexWeb CSS Edit as a plugin for BBEDit or as a stand-alone Macintosh version.
    • 971205: Cascade is a comprehensive Cascading Style Sheets editor for Mac. There is also a free version called Cascade Light.
    • 971204 A CSS mode for Alpha, a Mac programming editor, is available.
    • 971204 Anansi is reported to support CSS.
    • 971104 Coffeecup Software's StyleSheet Maker++ is a dedicated application for creating CSS style sheets.
    • 971024 mBED's Interactor 1.1 supports CSS Positioning which, when combined with a scriping language, allows you to create HTML-based animations.
    • 971006 Macromedia has released a preview release of DreamWeaver, an HTML authoring tool with rich support for CSS, including CSS Positioning.
    • 971006: Danere has released a new version of StyleMaker which supports CSS Positioning through a drag-and-drop interface.
    • 970912 Optima System's PageSpinner is a shareware HTML editor for MacOS with support for CSS.
    • 970908: Microsoft's beta version of FrontPage98 has some support for CSS.
    • 970710:Sheet Stylist is an application (actually an ActiveX control) for Windows 95 that allows you to create, edit and maintain CSS styles sheets.
    • 970623: Astrobyte has announced BeyondPress 3.0 which will convert QuarkXPress documents into HTML and CSS.
    • 970415: The Interaction dynamic site management system includes a comprehensive Macintosh CSS editor.
    • 970326: Sausage Software's HotDog editor now supports CSS.
    • 970326: Allaire's HomeSite editor (v. 2.5 and above) now supports CSS.
    • 960302: Harlequin has announced support for CSS in their Webmaker Frame-to-HTML application.
    • JoyHTML is a shareware Swedish HTML editor that supports CSS. It's not WYSIWYG, but rather source-code oriented. Nice if you would like to see the code without remembering the full CSS1 syntax. And you learn some Swedish as well (Download jh99sv.exe)
    • Adobe FrameMaker 5.5 can export HTML+CSS.

    Other software

    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010709 "xselect" is a C program that extracts all elements from an XML document that match a CSS selector. Part of the HTML-XML-utils package. (OpenSource)
    • 010427 A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 000420 Infinity Loop has released UpCast, an RTF to XML converter in Java that can generate structured XML or XHTML with an internal or external CSS1 style sheet.
    • 000217 Useful? Or not? Anyway, DeCSS is tiny (Perl) program by Mr. Bad to strip all CSS from an HTML file.
    • 991024 SAC (W3C's Simple API for CSS) is in beta. Bindings to C and Java are provided.
    • 991024 flute 1.0 is W3C's CSS parser in Java.
    • 990922 A beta-version of a Java-based CSS2 parser, with an API conforming to the July DOM2 draft, is available from SteadyState.

    CSS Specifications

    Cascading Style Sheets, level 1 (CSS1) became a W3C Recommendation in December 1996. It describes the CSS language as well as a simple visual formatting model. CSS2, which became a W3C Recommendation in May 1998, builds on CSS1 and adds support for media-specific style sheets (e.g. printers and aural devices), downloadable fonts, element positioning and tables.

    CSS3 is currently under development. You can follow its progress as new drafts are published.

    Translations into some languages are available from the CSS1 translations page and the CSS2 translations page. Errata are maintained separately for CSS1 and CSS2.

    The history of CSS is described in chapter 20 of the book Cascading Style Sheets, designing for the Web, by Hkon Wium Lie and Bert Bos (2nd ed., 1999, Addison Wesley, ISBN 0-201-59625-3)


    CSS Valid
CSS!Valid HTML 4.0!

    Bert Bos, CSS contact
    Last updated $Date: 2001/09/05 11:26:05 $ GMT
    \ No newline at end of file diff --git a/moz/w3css/style-css8.html b/moz/w3css/style-css8.html new file mode 100644 index 0000000..c58e978 --- /dev/null +++ b/moz/w3css/style-css8.html @@ -0,0 +1 @@ + Cascading Style Sheets

    Cascading Style Sheets
    home page

    (This page uses CSS style sheets)

    Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g. fonts, colors, spacing) to Web documents. For background information on style sheets, see the Web style sheets resource page. Discussions about CSS are carried out on the (archived) www-style@w3.org mailing list and on comp.infosystems.www.authoring.stylesheets.

    What's new?

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010627 Westciv offers a 12-week, online CSS1 course, starting 25 June 2001. (Free if followed in real time.)
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 010613 WestCiv has released Layout Master, a program to design page layouts in HTML/CSS2 by drag & drop. (Mac, Windows forthcoming)
    • 010530 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows. Includes support for Netscape 6, IE 6 and Opera 5. (Shareware)
    • 010523 Westciv published version 3 of their online CSS guide, covering all of CSS2 as well as browser compatibility issues. (Free online, enhanced version for sale.)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market. Evaluation download available, registration required.
    • 010427A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010323 Westciv is offering online courses, which you can follow for free on their site or buy. HTML/XHTML starts now, CSS1 will follow in June.
    • 010220 The Browser upgrade initiative of the WaSP (Web Standards Project) aims to rid the world of old, non-standards compliant browsers that hold back progress.
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are beta versions for EPOC. Shareware.
    • 010130 W3Schools is a site with tutorials on many Web technologies, including CSS.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 010113 A page from the tutorial of the Morphon XML editor (see below) explains why CSS is a good choice for XML.
    • 001211 The Zvon site has published a complete CSS2 reference with examples. Also on that site: the CSS1 reference by Miloslav Nic is an index to the CSS1 spec by property name, enhanced with examples. There is also a tutorial on CSS for XML.
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)

    Something to add? Let me know!

    Learning CSS

    Tutorials

    For a quick introduction, try chapter 2 of Lie & Bos, or Dave Raggett's intro to CSS. Or see examples of styling XML and CSS tips & tricks.

    Books

    A selection of books on CSS:

    CSS online resources

    Some non-English resources:

    English resources:

    Secondary resources, i.e., resources that catalogue links to other resources. (Which makes this list a tertiary resource… )

    CSS Browsers

    The easiest way to start experimenting with style sheets is to download one of the browsers that support CSS1. Not all of the browsers below implement the full specification, but releases are coming out fast so this should soon change.

    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market.
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are betas of version 5 for EPOC. BeOS version is 3.62. Shareware.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 000815 NetClue Corp. released the Clue browser 3.0, a Java component with support for CSS1, DOM and Javascript.
    • 000327 Microsoft shipped Internet Explorer 5 for the Macintosh. It apparently supports full CSS1, the first browser to do so.
    • 991202 Closure is a Web browser written in Common Lisp; supports CSS1.
    • 991022 Hewlett Packard released their "embedded microbrowser" ChaiFarer, supporting CSS1. CSS2 will come later.
    • 990924 ICE Soft released v.5 of their two embeddable browsers: the "base" one is a viewer for HTML/XML+CSS2, the "pro" one adds networking and more. Both in Java. Does MathML, too.
    • 990412 Microsoft has released Internet Explorer 5.0 for Windows, Solaris and HP-UX
    • Silicon Graphics has an embeddable CSS-enhanced web browser that is used in a number of applications and their desktop
    • Amaya is W3C's Web client that is both a browser and an authoring tool. It has partial (but growing) support for CSS1.
    • Arena, previously W3C's testbed browser, is now being developed by Yggdrasil. It has a partial implementation of CSS1.
    • Emacs-w3, a.k.a. Gnuscape Navigator, supports some CSS1.

    These sources document the level of support in various browsers:

    CSS Authoring Tools

    Currently, most Web Authoring tools provide some sort of support for CSS style sheets. A ZDnet article described some of them. The list below is far from complete, but contains (in chronological order) all tools that have been reported to us.

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 001101 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)
    • 000928 Software602 has an office suite 602 Pro Suite for Windows that can edit HTML+CSS (freeware).
    • 000802 Lunatech Research has released beta version 7 of the Morphon XML editor, which includes a CSS editor. Written in Java.
    • 000704 AceHTML 4 by Visicom Media is an HTML/CSS editor for Windows. Both commercial and freeware versions are available.
    • 991217 Justsystem (also in English) has released their Java-based, multi-lingual wordprocessor ICHITARO Ark. It uses HTML/CSS as its native format (screenshot).
    • 991119 Bluefish is an OpenSource HTML editor for Unix with support for CSS1.
    • 991026 Amaya, W3C's Web client that is both a browser and an authoring tool, is in version 2.2.
    • 990807 Cascade and Cascade Light are CSS editors for the Mac.
    • 990804 En Vogue is a (non-WYSIWYG) editor running on the Atari ST. It supports CSS1 & 2.
    • 990529 SoftQuad's XMetaL authors & displays XML documents with CSS style sheets.
    • 990525 CorelDraw 9 exports HTML + CSS.
    • 980929 SoftQuad's HoTMetaL PRO 5.0 authors, as well as displays, CSS and HTML.
    • 980829 W3CSS is in a new release.
    • 980829 Prime Style has become a shareware product and versions 2.0 is now available.
    • 980826 StyleOne is an easy-to-use CSS editor to create Web pages.
    • 980312 CSS Mill by Patrick Corcoran is a visual tool for generating CSS styled HTML.
    • 980115 Lewis Gartenberg has released a shareware tool, W2CSS which converts MS Word documents into HTML and CSS.
    • 971216 EDF has released CSSize, a tool which helps you convert HTML documents into HTML+CSS documents.
    • 971216 Hexmac has released HexWeb CSS Edit as a plugin for BBEDit or as a stand-alone Macintosh version.
    • 971205: Cascade is a comprehensive Cascading Style Sheets editor for Mac. There is also a free version called Cascade Light.
    • 971204 A CSS mode for Alpha, a Mac programming editor, is available.
    • 971204 Anansi is reported to support CSS.
    • 971104 Coffeecup Software's StyleSheet Maker++ is a dedicated application for creating CSS style sheets.
    • 971024 mBED's Interactor 1.1 supports CSS Positioning which, when combined with a scriping language, allows you to create HTML-based animations.
    • 971006 Macromedia has released a preview release of DreamWeaver, an HTML authoring tool with rich support for CSS, including CSS Positioning.
    • 971006: Danere has released a new version of StyleMaker which supports CSS Positioning through a drag-and-drop interface.
    • 970912 Optima System's PageSpinner is a shareware HTML editor for MacOS with support for CSS.
    • 970908: Microsoft's beta version of FrontPage98 has some support for CSS.
    • 970710:Sheet Stylist is an application (actually an ActiveX control) for Windows 95 that allows you to create, edit and maintain CSS styles sheets.
    • 970623: Astrobyte has announced BeyondPress 3.0 which will convert QuarkXPress documents into HTML and CSS.
    • 970415: The Interaction dynamic site management system includes a comprehensive Macintosh CSS editor.
    • 970326: Sausage Software's HotDog editor now supports CSS.
    • 970326: Allaire's HomeSite editor (v. 2.5 and above) now supports CSS.
    • 960302: Harlequin has announced support for CSS in their Webmaker Frame-to-HTML application.
    • JoyHTML is a shareware Swedish HTML editor that supports CSS. It's not WYSIWYG, but rather source-code oriented. Nice if you would like to see the code without remembering the full CSS1 syntax. And you learn some Swedish as well (Download jh99sv.exe)
    • Adobe FrameMaker 5.5 can export HTML+CSS.

    Other software

    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010709 "xselect" is a C program that extracts all elements from an XML document that match a CSS selector. Part of the HTML-XML-utils package. (OpenSource)
    • 010427 A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 000420 Infinity Loop has released UpCast, an RTF to XML converter in Java that can generate structured XML or XHTML with an internal or external CSS1 style sheet.
    • 000217 Useful? Or not? Anyway, DeCSS is tiny (Perl) program by Mr. Bad to strip all CSS from an HTML file.
    • 991024 SAC (W3C's Simple API for CSS) is in beta. Bindings to C and Java are provided.
    • 991024 flute 1.0 is W3C's CSS parser in Java.
    • 990922 A beta-version of a Java-based CSS2 parser, with an API conforming to the July DOM2 draft, is available from SteadyState.

    CSS Specifications

    Cascading Style Sheets, level 1 (CSS1) became a W3C Recommendation in December 1996. It describes the CSS language as well as a simple visual formatting model. CSS2, which became a W3C Recommendation in May 1998, builds on CSS1 and adds support for media-specific style sheets (e.g. printers and aural devices), downloadable fonts, element positioning and tables.

    CSS3 is currently under development. You can follow its progress as new drafts are published.

    Translations into some languages are available from the CSS1 translations page and the CSS2 translations page. Errata are maintained separately for CSS1 and CSS2.

    The history of CSS is described in chapter 20 of the book Cascading Style Sheets, designing for the Web, by Hkon Wium Lie and Bert Bos (2nd ed., 1999, Addison Wesley, ISBN 0-201-59625-3)


    CSS Valid
CSS!Valid HTML 4.0!

    Bert Bos, CSS contact
    Last updated $Date: 2001/09/05 11:26:05 $ GMT
    \ No newline at end of file diff --git a/moz/w3css/style-css8p.html b/moz/w3css/style-css8p.html new file mode 100644 index 0000000..a0343d2 --- /dev/null +++ b/moz/w3css/style-css8p.html @@ -0,0 +1 @@ + Cascading Style Sheets

    Cascading Style Sheets
    home page

    (This page uses CSS style sheets)

    Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g. fonts, colors, spacing) to Web documents. For background information on style sheets, see the Web style sheets resource page. Discussions about CSS are carried out on the (archived) www-style@w3.org mailing list and on comp.infosystems.www.authoring.stylesheets.

    What's new?

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010627 Westciv offers a 12-week, online CSS1 course, starting 25 June 2001. (Free if followed in real time.)
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 010613 WestCiv has released Layout Master, a program to design page layouts in HTML/CSS2 by drag & drop. (Mac, Windows forthcoming)
    • 010530 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows. Includes support for Netscape 6, IE 6 and Opera 5. (Shareware)
    • 010523 Westciv published version 3 of their online CSS guide, covering all of CSS2 as well as browser compatibility issues. (Free online, enhanced version for sale.)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market. Evaluation download available, registration required.
    • 010427A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010323 Westciv is offering online courses, which you can follow for free on their site or buy. HTML/XHTML starts now, CSS1 will follow in June.
    • 010220 The Browser upgrade initiative of the WaSP (Web Standards Project) aims to rid the world of old, non-standards compliant browsers that hold back progress.
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are beta versions for EPOC. Shareware.
    • 010130 W3Schools is a site with tutorials on many Web technologies, including CSS.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 010113 A page from the tutorial of the Morphon XML editor (see below) explains why CSS is a good choice for XML.
    • 001211 The Zvon site has published a complete CSS2 reference with examples. Also on that site: the CSS1 reference by Miloslav Nic is an index to the CSS1 spec by property name, enhanced with examples. There is also a tutorial on CSS for XML.
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)

    Something to add? Let me know!

    Learning CSS

    Tutorials

    For a quick introduction, try chapter 2 of Lie & Bos, or Dave Raggett's intro to CSS. Or see examples of styling XML and CSS tips & tricks.

    Books

    A selection of books on CSS:

    CSS online resources

    Some non-English resources:

    English resources:

    Secondary resources, i.e., resources that catalogue links to other resources. (Which makes this list a tertiary resource… )

    CSS Browsers

    The easiest way to start experimenting with style sheets is to download one of the browsers that support CSS1. Not all of the browsers below implement the full specification, but releases are coming out fast so this should soon change.

    • 010817 The KDE project released version 2.2, including the Konqueror browser and the KHTML library. A table outlines its (impressive) CSS2 support. (OpenSource, Unix)
    • 010517 Opera Software has released the Linux version of the Opera browser version 5.0.
    • 010515 Espial's Escape 4.7 browser implements CSS support for HTML, XML and XHTML. Written in Java for the embedded software market.
    • 010426 iCab, a browser for the Mac, is starting to support CSS. The preview release of version 2.5 reportedly supports most of CSS1. (Free)
    • 010326 Openwave's mobile browser implements XHTML and CSS and is expected to ship in cell phones 2nd half of 2001. Also see data sheet [PDF].
    • 010326 Nokia will start selling mobile phones that support XHTML and CSS during 2001. See demo [Flash], press release and white paper [PDF].
    • 010215 Version 5.02 of the Opera browser has been released for Windows. There are betas of version 5 for EPOC. BeOS version is 3.62. Shareware.
    • 010123 The Arachne WWW browser for DOS and Linux supports CSS1 since version 1.70 (free for non-commercial use).
    • 001115 Netscape has released Netscape 6, with one of the best CSS implementations to date.
    • 000815 NetClue Corp. released the Clue browser 3.0, a Java component with support for CSS1, DOM and Javascript.
    • 000327 Microsoft shipped Internet Explorer 5 for the Macintosh. It apparently supports full CSS1, the first browser to do so.
    • 991202 Closure is a Web browser written in Common Lisp; supports CSS1.
    • 991022 Hewlett Packard released their "embedded microbrowser" ChaiFarer, supporting CSS1. CSS2 will come later.
    • 990924 ICE Soft released v.5 of their two embeddable browsers: the "base" one is a viewer for HTML/XML+CSS2, the "pro" one adds networking and more. Both in Java. Does MathML, too.
    • 990412 Microsoft has released Internet Explorer 5.0 for Windows, Solaris and HP-UX
    • Silicon Graphics has an embeddable CSS-enhanced web browser that is used in a number of applications and their desktop
    • Amaya is W3C's Web client that is both a browser and an authoring tool. It has partial (but growing) support for CSS1.
    • Arena, previously W3C's testbed browser, is now being developed by Yggdrasil. It has a partial implementation of CSS1.
    • Emacs-w3, a.k.a. Gnuscape Navigator, supports some CSS1.

    These sources document the level of support in various browsers:

    CSS Authoring Tools

    Currently, most Web Authoring tools provide some sort of support for CSS style sheets. A ZDnet article described some of them. The list below is far from complete, but contains (in chronological order) all tools that have been reported to us.

    • 010905 WestCiv released version 2.0 of the CSS editor Style Master. Supports CSS2 and includes a browser-compatibility guide. (Mac & Windows)
    • 010803 XMLmind has released a beta version of XMLmind Editor (XXE), an XML 1.0 editor, that also features a WYSIWYG editing mode using CSS2.
    • 010711 Morphon Technologies released a beta of the Morphon Standalone CSS Editor, supporting CSS2 (Java, free trial)
    • 010704 Visicom Mdia released version 4.30.0 of WebExpert 2000, an HTML editor with support for CSS2, in French.
    • 010622 Maxro Software has released CSS-Styler 3.0, a CSS editor for Windows (free trial version)
    • 010621 JustStyle CSS Editor (version 1.1) is an editor for CSS1 style sheets. (30-day free trial, Java)
    • 001101 Bradbury Software has released version 2.10 of TopStyle, a CSS editor for Windows.
    • 001102 Thomas Meinike has released StyleAssistant (German page), a menu-driven program for writing CSS1 style sheets. (Freeware, Windows)
    • 001014 Quanta is an HTML editor for the KDE desktop. CSS 1 & 2 support is in the beta for KDE2 (Unix, OpenSource)
    • 000928 Software602 has an office suite 602 Pro Suite for Windows that can edit HTML+CSS (freeware).
    • 000802 Lunatech Research has released beta version 7 of the Morphon XML editor, which includes a CSS editor. Written in Java.
    • 000704 AceHTML 4 by Visicom Media is an HTML/CSS editor for Windows. Both commercial and freeware versions are available.
    • 991217 Justsystem (also in English) has released their Java-based, multi-lingual wordprocessor ICHITARO Ark. It uses HTML/CSS as its native format (screenshot).
    • 991119 Bluefish is an OpenSource HTML editor for Unix with support for CSS1.
    • 991026 Amaya, W3C's Web client that is both a browser and an authoring tool, is in version 2.2.
    • 990807 Cascade and Cascade Light are CSS editors for the Mac.
    • 990804 En Vogue is a (non-WYSIWYG) editor running on the Atari ST. It supports CSS1 & 2.
    • 990529 SoftQuad's XMetaL authors & displays XML documents with CSS style sheets.
    • 990525 CorelDraw 9 exports HTML + CSS.
    • 980929 SoftQuad's HoTMetaL PRO 5.0 authors, as well as displays, CSS and HTML.
    • 980829 W3CSS is in a new release.
    • 980829 Prime Style has become a shareware product and versions 2.0 is now available.
    • 980826 StyleOne is an easy-to-use CSS editor to create Web pages.
    • 980312 CSS Mill by Patrick Corcoran is a visual tool for generating CSS styled HTML.
    • 980115 Lewis Gartenberg has released a shareware tool, W2CSS which converts MS Word documents into HTML and CSS.
    • 971216 EDF has released CSSize, a tool which helps you convert HTML documents into HTML+CSS documents.
    • 971216 Hexmac has released HexWeb CSS Edit as a plugin for BBEDit or as a stand-alone Macintosh version.
    • 971205: Cascade is a comprehensive Cascading Style Sheets editor for Mac. There is also a free version called Cascade Light.
    • 971204 A CSS mode for Alpha, a Mac programming editor, is available.
    • 971204 Anansi is reported to support CSS.
    • 971104 Coffeecup Software's StyleSheet Maker++ is a dedicated application for creating CSS style sheets.
    • 971024 mBED's Interactor 1.1 supports CSS Positioning which, when combined with a scriping language, allows you to create HTML-based animations.
    • 971006 Macromedia has released a preview release of DreamWeaver, an HTML authoring tool with rich support for CSS, including CSS Positioning.
    • 971006: Danere has released a new version of StyleMaker which supports CSS Positioning through a drag-and-drop interface.
    • 970912 Optima System's PageSpinner is a shareware HTML editor for MacOS with support for CSS.
    • 970908: Microsoft's beta version of FrontPage98 has some support for CSS.
    • 970710:Sheet Stylist is an application (actually an ActiveX control) for Windows 95 that allows you to create, edit and maintain CSS styles sheets.
    • 970623: Astrobyte has announced BeyondPress 3.0 which will convert QuarkXPress documents into HTML and CSS.
    • 970415: The Interaction dynamic site management system includes a comprehensive Macintosh CSS editor.
    • 970326: Sausage Software's HotDog editor now supports CSS.
    • 970326: Allaire's HomeSite editor (v. 2.5 and above) now supports CSS.
    • 960302: Harlequin has announced support for CSS in their Webmaker Frame-to-HTML application.
    • JoyHTML is a shareware Swedish HTML editor that supports CSS. It's not WYSIWYG, but rather source-code oriented. Nice if you would like to see the code without remembering the full CSS1 syntax. And you learn some Swedish as well (Download jh99sv.exe)
    • Adobe FrameMaker 5.5 can export HTML+CSS.

    Other software

    • 010806 A Perl CSS project has been started on SourceForge, to develop CSS-DOM and SAC libraries for Perl.
    • 010709 "xselect" is a C program that extracts all elements from an XML document that match a CSS selector. Part of the HTML-XML-utils package. (OpenSource)
    • 010427 A Perl module that implements SAC, called CSS::SAC, has been written by Robin Berjon. (OpenSource.)
    • 001208 Aurelia Systems offers Aureleon, a printer driver for Windows 95/98/NT/2000 that converts anything you can print to HTML + CSS.
    • 000420 Infinity Loop has released UpCast, an RTF to XML converter in Java that can generate structured XML or XHTML with an internal or external CSS1 style sheet.
    • 000217 Useful? Or not? Anyway, DeCSS is tiny (Perl) program by Mr. Bad to strip all CSS from an HTML file.
    • 991024 SAC (W3C's Simple API for CSS) is in beta. Bindings to C and Java are provided.
    • 991024 flute 1.0 is W3C's CSS parser in Java.
    • 990922 A beta-version of a Java-based CSS2 parser, with an API conforming to the July DOM2 draft, is available from SteadyState.

    CSS Specifications

    Cascading Style Sheets, level 1 (CSS1) became a W3C Recommendation in December 1996. It describes the CSS language as well as a simple visual formatting model. CSS2, which became a W3C Recommendation in May 1998, builds on CSS1 and adds support for media-specific style sheets (e.g. printers and aural devices), downloadable fonts, element positioning and tables.

    CSS3 is currently under development. You can follow its progress as new drafts are published.

    Translations into some languages are available from the CSS1 translations page and the CSS2 translations page. Errata are maintained separately for CSS1 and CSS2.

    The history of CSS is described in chapter 20 of the book Cascading Style Sheets, designing for the Web, by Hkon Wium Lie and Bert Bos (2nd ed., 1999, Addison Wesley, ISBN 0-201-59625-3)


    CSS Valid
CSS!Valid HTML 4.0!

    Bert Bos, CSS contact
    Last updated $Date: 2001/09/05 11:26:05 $ GMT
    \ No newline at end of file diff --git a/mozKill.html b/mozKill.html new file mode 100644 index 0000000..f854f95 --- /dev/null +++ b/mozKill.html @@ -0,0 +1 @@ + Mozilla Killa

    Mozilla chrome go bye-bye... or not.

    \ No newline at end of file diff --git a/mq-valueless.html b/mq-valueless.html new file mode 100644 index 0000000..81b1b5c --- /dev/null +++ b/mq-valueless.html @@ -0,0 +1,60 @@ + + + +Valueless Media Queries + + + + + +
      +
    1. (width)
    2. +
    3. (height)
    4. +
    5. (device-width)
    6. +
    7. (device-height)
    8. +
    9. (orientation) [span1] [span2]
    10. +
    11. (aspect-ratio)
    12. +
    13. (device-aspect-ratio)
    14. +
    15. (color)
    16. +
    17. (color-index)
    18. +
    19. (monochrome)
    20. +
    21. (resolution) [span1 >100dpi] [span2 326dpi] [span3 <1000dpi]
    22. +
    23. (scan)
    24. +
    25. (grid)
    26. +
    + + + diff --git a/multiatribute.html b/multiatribute.html new file mode 100644 index 0000000..a9ded2b --- /dev/null +++ b/multiatribute.html @@ -0,0 +1,26 @@ + + + +Multiattribute + + + + +

    +A. +

    + + +

    +B. +

    + + + diff --git a/multibg.html b/multibg.html new file mode 100644 index 0000000..068187c --- /dev/null +++ b/multibg.html @@ -0,0 +1 @@ + MultiClass Test

    Document styles:

    body {background: white; color: black;}
    #test {background:
    	url(i/topleft.gif) 0 0 no-repeat,
    	url(i/topright.gif) 100% 0 no-repeat,
    	url(i/botleft.gif) 0 100% no-repeat,
    	url(i/botright.gif) 100% 100% no-repeat;
    	padding: 25px; background-color: #008000;}
    
    Let's add four images to a single background! I mean, why not?
    \ No newline at end of file diff --git a/multiclass.html b/multiclass.html new file mode 100644 index 0000000..9963bad --- /dev/null +++ b/multiclass.html @@ -0,0 +1 @@ + MultiClass Test

    Document styles:

    li {margin: 0.33em;}
    .one {font-style: italic;}
    .one.one {font-weight: bold;}  /* check this one! */
    .one.two.three.four {color: red;}
    .four {border: 1px dotted gray;}
    .oh {text-decoration: underline;}
    .five-oh {background: #CCE;}
    .oh.three.five.six.seven.eight.nine {background: yellow;}
    

    Styled elements (text replicates class values):

    • one two
    • one three
    • four one one
    • four
    • hawaii five-oh
    • eight six seven five three oh nine

    The content above should appear basically the same as the graphic below-- not counting the size and family of the text itself, the width of the element boxes, or the bullet styles.

    reference rendering
    \ No newline at end of file diff --git a/nth-of-type-not.html b/nth-of-type-not.html new file mode 100644 index 0000000..9ddfc6f --- /dev/null +++ b/nth-of-type-not.html @@ -0,0 +1,52 @@ + + + + +:nth-of-type() and :not() + + + + + +
      +
    1. List item
    2. +
    3. List item
    4. +
    5. List item
    6. + +
    7. List item
    8. +
    9. List item
    10. +
    11. List item
    12. +
    13. List item
    14. +
    15. List item
    16. +
    17. List item
    18. +
    19. List item
    20. +
    21. List item
    22. + +
    23. List item
    24. +
    25. List item
    26. +
    27. List item
    28. +
    29. List item
    30. +
    31. List item
    32. +
    33. List item
    34. +
    35. List item
    36. +
    + +

    +Note that you must hover over the ordered list to reveal its fullness. (Yes, I’m sorry if you’re on a mobie device. This is a simple testcase.) +

    +

    +The :nth-of-type() portion refers only to that element type within the document structure; in this case, li. It does not take the class negation into account when counting. Thus only the odd-numbered li elements (within the set of elements of that type) can be selected, regardless of whether they are displayed or not. Structural selectors care about document structure, not rendering. Otherwise, list items 6, 8, 10, and 12 (in the hovered state; 5, 7, 9, and 11 unhovered) would be red-on-silver. +

    +

    +Furthermore, only those odd-numbered li elements without a class containing skip are selected. Thus, the “skipped” list items do not get red italic text or silver backgrounds, even when they are odd-numbered members of the li type set. +

    + + + diff --git a/parsebugs.html b/parsebugs.html new file mode 100644 index 0000000..41bb604 --- /dev/null +++ b/parsebugs.html @@ -0,0 +1,75 @@ + + + +Parsing bug testing + + + + +

    +Italic green passes (correctly fails to match), bold red-on-yellow fails (matches when it should not). +

    + +
      + +
    1. +Testing * html #id01 +
    2. + +
    3. +Testing *html #id02 +
    4. + +
    5. +Testing html* #id03 +
    6. + +
    7. +Testing * + html #id04 +
    8. + +
    9. +Testing *+html #id05 +
    10. + +
    11. +Testing html > /**/body #id06 +
    12. + +
    13. +Testing html>/**/body #id07 +
    14. + +
    15. +Testing li/* comment */#id08 +
    16. + +
    17. +Testing li/**/#id09 +
    18. + +
    + +

    +Any failures point to potential CSS hacks that will target a browser, and any passes indicate hacks that will not work. +

    + + + diff --git a/propspace.html b/propspace.html new file mode 100644 index 0000000..493c95f --- /dev/null +++ b/propspace.html @@ -0,0 +1 @@ + Property-space

    If this paragraph is red, the browser got confused by whitespace in one of the rules that applies to it. If it's green, then it handled the whitespace as the CSS grammar requires.

    Here are the styles that were used:
    p {color: red;}
    p#one {color  :  green;}
    
    \ No newline at end of file diff --git a/pseudo-link-test.html b/pseudo-link-test.html new file mode 100644 index 0000000..eb9fc13 --- /dev/null +++ b/pseudo-link-test.html @@ -0,0 +1 @@ + Untitled

    If the user agent handles the :link and :visited pseudo-classes (and the cascade) correctly, then unvisited links on this page should be normal weight and green, while visited links should be boldfaced and purple.

    CSS Stuff

    \ No newline at end of file diff --git a/pseudo-link-test2.html b/pseudo-link-test2.html new file mode 100644 index 0000000..678037c --- /dev/null +++ b/pseudo-link-test2.html @@ -0,0 +1 @@ + a:link test

    My woram.com website.

    My galapagos.to website.

    \ No newline at end of file diff --git a/pseudos-inspector-test.html b/pseudos-inspector-test.html new file mode 100644 index 0000000..6f2291c --- /dev/null +++ b/pseudos-inspector-test.html @@ -0,0 +1,41 @@ + + + +Pseudo-Class and -Element Inspector Tests + + + + +

    +A proactive team gets up to speed on horizontal markets. Red flags become solutions. A major stretch goal for this fiscal quarter is new-generation challenges. A transition phase fiscally gives rise to enabling get-it-done attitudes. Value-added strategy agrees to disagree and in view of the fact that each of you will ramp up progress on a zero-defect-generation schedule we clearly can conclude that a best-of-class goal blows them away. Leading indicators would seem to suggest that synergies close the loop on the issue of the enabling guesstimates. Can we indeed say that major players agree to disagree on a reality check? We will efficiently take over the enterprise market for soup-to-nuts headcount readjustment. A first-class horizontal market knocks your socks off, however opportunity has mind-blowing 90% solutions. So, legacy dialogue takes the initiative. +

    +

    +(courtesy http://lurkertech.com/corpspeak/) +

    + +
      +
    • This has a span within.
    • +
    • This also has a span within.
    • +
    + + + diff --git a/pseudospec.html b/pseudospec.html new file mode 100644 index 0000000..eef05ea --- /dev/null +++ b/pseudospec.html @@ -0,0 +1 @@ + Pseudo-Element Specificity

    Styles applied to this page:

    p.test1:first-letter {color: green; font-size: 200%;}
    p.test1 {color: gray; font-size: 1em;}
    p.test2 {color: gray; font-size: 1em;}
    p.test2:first-letter {color: green; font-size: 200%;}
    

    This paragraph has a class of test1, and its text should be gray. This should apply to the first letter, whose rule has a specificity equal to the p.test rule.

    This paragraph has a class of test2, and its text should be gray. This should apply not to the first letter, whose rule has a specificity equal to the p.test rule, and which comes later in the stylesheet.

    \ No newline at end of file diff --git a/quote-suppress.html b/quote-suppress.html new file mode 100644 index 0000000..a6d9212 --- /dev/null +++ b/quote-suppress.html @@ -0,0 +1,138 @@ + + + +Suppressing Marks on Quotes and Blockquotes + + + + +
    +

    Baseline: no alterations to quotation styles.

    + +

    +Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + +
    +

    #g1 {quotes: none;}

    + +

    +Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + +
    +

    #g2 {quotes: '' '';}

    + +

    +Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + +
    +

    q:before, q:after {content: none;}

    + +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element.

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + +
    +

    q:before, q:after {content: normal;}

    + +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element.

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + +
    +

    q:before, q:after {content: '';}

    + +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element.

    + +
    +

    +And then there's this blockquote.

    +

    Here there is quoted text without quotation characters in the content.

    +

    Here there is "quoted text" with quotation characters outside the q element.

    +

    Here there is "quoted text" with quotation characters inside the q element. +

    +
    + +
    + + + diff --git a/quoted-colors.html b/quoted-colors.html new file mode 100644 index 0000000..3bae107 --- /dev/null +++ b/quoted-colors.html @@ -0,0 +1 @@ + Quoted color values

    CSS does not permit color values to be quoted. However, lazy browsers permit it, and some legacy pages were authored using the quotes. In browsers that ignore the quotation marks on color values, the text of all six following paragraphs will be a shade of purple. In those that do not, only the first and fourth following paragraphs will have text in a shade of purple.

    Paragraph one. Lorem ipsum blah blah blah.

    Paragraph two. Lorem ipsum blah blah blah.

    Paragraph three. Lorem ipsum blah blah blah.

    Paragraph four. Lorem ipsum blah blah blah.

    Paragraph five. Lorem ipsum blah blah blah.

    Paragraph six. Lorem ipsum blah blah blah.

    \ No newline at end of file diff --git a/rotate3d-explore.html b/rotate3d-explore.html new file mode 100644 index 0000000..c29aa9a --- /dev/null +++ b/rotate3d-explore.html @@ -0,0 +1,67 @@ + + + + +rotate3d() vs. rotateX() etc. + + + + +

    editable CSS

    + +
    + +
    ABC
    +
    ABC
    +
    ABC
    +
    ABC
    +
    ABC
    + +
    + +
    + +
    ABC
    +
    ABC
    +
    ABC
    +
    ABC
    +
    ABC
    + +
    + + +

    +Both boxes show the top-right-bottom-left views of the transform in the middle. Each view is rotated 80 degrees away from face-on, not 90 degrees. If you change the selectors in the editable CSS, things will break. Don’t say I didn’t warn you. +

    + + + diff --git a/safari/transform-jump.html b/safari/transform-jump.html new file mode 100644 index 0000000..b1c6e87 --- /dev/null +++ b/safari/transform-jump.html @@ -0,0 +1,41 @@ + + + +Skynet + + + + +
    +This is an absolutely positioned element. It containing block defaults to the root element but switches to the body when it is transformed by hovering. +
    + +
    +This is a normal-flow element. It has a top margin which collapses with the body element's top element (which is zero). Hover the mouse pointer over the body (the bluish box surrounding this one) to see the absolutely positioned element shift. +
    + + + diff --git a/sec17-06-02.htm b/sec17-06-02.htm new file mode 100755 index 0000000..517cd64 --- /dev/null +++ b/sec17-06-02.htm @@ -0,0 +1 @@ + sec17-06-02.htm
    1 2 3
    4 5 6
    7 8 9
    10 11 12
    13 14 15
    \ No newline at end of file diff --git a/selectoracle-example.html b/selectoracle-example.html new file mode 100644 index 0000000..844c032 --- /dev/null +++ b/selectoracle-example.html @@ -0,0 +1 @@ + CSS2 Selector Test

    Setup: please follow this link so that you have visited the W3C's main page. This will set up the necessary conditions for the following test.


    A paragraph which starts off the DIV.

    This is an H1 element

    (this is anonymous text)

    This is a paragraph with an id of text. It contains three hyperlinks, only one of which should become boldfaced white on black. It isn't this hyperlink, which won't be visited no matter where you've been; therefore it doesn't get the specified hover styles. The hyperlink in this sentence, however, points to the W3C's main page; however it has no title attribute and so should not take the styles. This hyperlink here also points to the W3C's main page, but also has the needed value for the title attribute.


    A paragraph which starts off the DIV.

    This is an H1 element

    This is a paragraph with no id. It contains three hyperlinks, none of which should become boldfaced white on black. It won't be this hyperlink, or this one which points to the W3C's main page, or even this hyperlink here, because the selector can't match any of the hyperlinks in this paragraph.

    \ No newline at end of file diff --git a/specificity-test.html b/specificity-test.html new file mode 100644 index 0000000..a34a5e0 --- /dev/null +++ b/specificity-test.html @@ -0,0 +1 @@ +

    This paragraph should be green.

    This paragraph should be green. If it is red, the inline style has overridden the rule in the embedded stylesheet-- incorrectly so, in this case.

    \ No newline at end of file diff --git a/string-unicode.html b/string-unicode.html new file mode 100644 index 0000000..35d968c --- /dev/null +++ b/string-unicode.html @@ -0,0 +1,23 @@ + + + + +Unicode quotes in strings + + + + + +

    p01

    +

    p02

    +

    p03

    +

    p04

    + + + diff --git a/suite-format-xml.txt b/suite-format-xml.txt new file mode 100644 index 0000000..2bc02bc --- /dev/null +++ b/suite-format-xml.txt @@ -0,0 +1 @@ + ..... ..... p.one {background: url(star.png);} p.two {background: cyan;}

    This paragraph should have a star pattern tiled in the background.

    This paragraph should have a cyan background.

    \ No newline at end of file diff --git a/super.html b/super.html new file mode 100644 index 0000000..5d646a8 --- /dev/null +++ b/super.html @@ -0,0 +1 @@ + Superscript Testing

    This paragraph will contain superscripted text at random points, and it will hopefully not influence the separation between succesive baselines when it occurs. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.


    This paragraph will contain superscripted text at random points, but since the line-height style doesn't apply here, they will likely increase the separation between succesive baselines when it occurs. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

    \ No newline at end of file diff --git a/table-back.html b/table-back.html new file mode 100644 index 0000000..5b8a733 --- /dev/null +++ b/table-back.html @@ -0,0 +1 @@ + Table background?
    r1c1 r1c2 r1c3 r1c4
    r2c1 r2c2 r2c3 r2c4
    r3c1 r3c2 r3c3 r3c4
    r4c1 r4c2 r4c3 r4c4
    \ No newline at end of file diff --git a/table-collapse.html b/table-collapse.html new file mode 100644 index 0000000..d69a81d --- /dev/null +++ b/table-collapse.html @@ -0,0 +1 @@ + Collapsing Border Model

    Collapsing Border Model

    12
    24
    \ No newline at end of file diff --git a/table-fixed.html b/table-fixed.html new file mode 100644 index 0000000..663c9c3 --- /dev/null +++ b/table-fixed.html @@ -0,0 +1 @@ + Fixed Layout

    Fixed Layout

    12
    244444
    \ No newline at end of file diff --git a/test590.html b/test590.html new file mode 100644 index 0000000..53724fb --- /dev/null +++ b/test590.html @@ -0,0 +1 @@ + 590 Text

    some text

    \ No newline at end of file diff --git a/text-shadow.html b/text-shadow.html new file mode 100644 index 0000000..6a1ba64 --- /dev/null +++ b/text-shadow.html @@ -0,0 +1 @@ + text-shadow test

    This should have a gray shadow

    This should have a purple "glow"

    This should have a wild set of shadows

    \ No newline at end of file diff --git a/trans-border.html b/trans-border.html new file mode 100644 index 0000000..c8b35b5 --- /dev/null +++ b/trans-border.html @@ -0,0 +1,27 @@ + + + +Transparent Borders + + + + +
    +
    +These divs should have ten-pixel transparent borders. This will have an effect similar to margins, which the divs do not have. +
    +
    +Thus, there should be 10 pixels of white space around the divs, and 20 pixels between them. There should be no red, gray, or black space at all except for the one-pixel solid black border surrounding the two divs. +
    +
    + + + diff --git a/try_like_tables.html b/try_like_tables.html new file mode 100644 index 0000000..409f566 --- /dev/null +++ b/try_like_tables.html @@ -0,0 +1,96 @@ + + + + + +try 4 + + + + + + + +
    + +
    + +
    blah
    + +
    blah
    + +
    +
    through a top-down, proactive approach we can remain + customer focused and goal-directed, innovate and be an inside-out organization + which facilitates sticky web-readiness transforming turnkey eyeballs to + brand 24/365 paradigms with benchmark turnkey channels implementing viral + e-services and dot-com action-items while we take that action item off-line + and raise a red flag and remember touch base as you think about the red + tape outside of the box and seize B2B e-tailers and re-envisioneer innovat
    +
    through a top-down, proactive approach we can + remain customer focused and goal-directed, innovate and be an inside-out + organization which facilitates sticky web-readiness transforming turnkey + eyeballs to brand 24/365 paradigms with benchmark turnkey channels implementing + viral e-services and dot-com action-items while we take that action item + off-line and raise a red flag and remember touch base as you think about + the red tape outside of the box and seize B2B e-tailers and re-envisioneer + innovatthrough a top-down, proactive approach we can remain customer focused + and goal-directed, innovate and be an inside-out organization which facilitates + sticky web-readiness transforming turnkey eyeballs to brand 24/365 paradigms + with benchmark turnkey channels implementing viral e-services and dot-com + action-items while we take that action item off-line and raise a red flag + and remember touch base as you think about the red tape outside of the + box and seize B2B e-tailers and re-envisioneer innovative partnerships + that evolve dot-com initiatives delivering synergistic earballs to incentivize + B2B2C deliverables that leverage magnetic solutions to synergize clicks-and-mortar + earballs while facilitating one-to-one action-items with revolutionary + relationships that deliver viral markets and grow e-business supply-chains + that expedite seamless relationships and transform back-end relationships + withthrough a top-down, proactive approach we can remain customer focused + and goal-directed, innovate and be an inside-out organization which facilitates + sticky web-readiness transforming turnkey eyeballs to brand 24/365 paradigms + with benchmark turnkey channels implementing viral e-services and dot-com + action-items while we take that action item off-line and raise a red flag + and remember touch base as you think about the red tape outside of the + box and seize B2B e-tailers and re-envisioneer innovative partnerships + that evolve dot-com initiatives delivering synergistic earballs to incentivize + B2B2C deliverables that leverage magnetic solutions to synergize clicks-and-mortar + earballs while facilitating one-to-one action-items with revolutionary + relationships that deliver viral markets and grow e-business supply-chains + that expedite seamless relationships and transform back-end relationships + withthrough a top-down, proactive approach we can remain customer focused + and goal-directed, innovate and be an inside-out organization which facilitates + sticky web-readiness transforming turnkey
    +
    +
    +
    blah
    +
    + + + diff --git a/underscore-test.html b/underscore-test.html new file mode 100644 index 0000000..6d749e3 --- /dev/null +++ b/underscore-test.html @@ -0,0 +1 @@ + Underscore testing

    This paragraph has a class of test_one. It should only be styled in browsers released in mid-2001 or later.

    This paragraph has a class of test_two. It should be styled by any CSS1-supporting browser.

    This paragraph has a class of test\_three. I'm not so sure about this one.

    \ No newline at end of file diff --git a/universal-onem.html b/universal-onem.html new file mode 100644 index 0000000..68166bd --- /dev/null +++ b/universal-onem.html @@ -0,0 +1,58 @@ + + + +Universal One-em + + + + +

    If this page is unreadable, set text size to 'medium'!

    +
    +

    +All right, assuming you can read this, here's how to trigger the problem this page demonstrates: +

    +
      +
    1. Fire up IE6/Win.
    2. +
    3. Open up the "View" menu.
    4. +
    5. Go to the "Text Size" menu entry.
    6. +
    7. Set the text size to "Medium."
    8. +
    9. Load up this page.
    10. +
    11. Using the same basic process as before, set the text size to "Smaller."
    12. +
    13. Wince.
    14. +
    +
    +

    +For extra fun, try the other non-"Medium" text size values. The degree to which the text size is modified for each is truly impressive. +

    +

    +The triggering rule for this bug is, of all things, the following: +

    +
    +* {font-size: 1em;}
    +
    +

    +If the rule is modified to use the value 100%, the bug isn't tripped. In other words, the flagship browser of Microsoft's primary platform still can't handle simple font sizing. +

    +

    +Thanks to Felix Miata for pointing out the solution of using 100%. +

    +

    +Following is some filler text just to make the page longer. +

    +

    +Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. +

    +

    +Lorem ipsum, dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. +

    + + + + diff --git a/val-casetest.html b/val-casetest.html new file mode 100644 index 0000000..ed9f3d5 --- /dev/null +++ b/val-casetest.html @@ -0,0 +1 @@ + Test of case-sensitivity

    This document should validate as HTML 4.0 at a minimum.

    This paragraph has a class of class1. It should have normal text and a yellow background.

    This paragraph has a class of CLASS1. It should have italic text and a transparent background.

    This paragraph has an ID of id1. It should have normal text and a cyan background.

    This paragraph has an ID of ID1. It should have boldface text and a transparent background.

    \ No newline at end of file diff --git a/vertalign-cases.html b/vertalign-cases.html new file mode 100644 index 0000000..11870a6 --- /dev/null +++ b/vertalign-cases.html @@ -0,0 +1 @@ + Vertical alignment cases
    x x
    x x
    x x
    x x
    x x
    x x
    x x
    x x
    x x
    \ No newline at end of file diff --git a/visited-styles.html b/visited-styles.html new file mode 100644 index 0000000..042611a --- /dev/null +++ b/visited-styles.html @@ -0,0 +1,30 @@ + + + + +Visited styles + + + + + +
      +
    1. This link will not have been visited
      (and please don’t try)
    2. +
    3. This link should show as visited
      (but if not, click it)
    4. +
    + + + diff --git a/white-space.html b/white-space.html new file mode 100644 index 0000000..9c6c8a5 --- /dev/null +++ b/white-space.html @@ -0,0 +1,48 @@ + + + +white-space: pre-line and pre-wrap + + + + +

    +[cl1] This paragraph should show extra space where there would ordinarily not be any. + There should also be preservation of returns +as this sentence + very clearly demonstrates. +

    + +

    +[cl2] This paragraph should not word-wrap, no matter how long the paragraph might be or over how many lines it would ordinarily wrap, as it has been set to white-space: nowrap and that should have the obvious effect. +

    + +

    +[cl1] This paragraph should show extra space, [cl3] except in the second half. +

    + +

    +[cl4] This paragraph should show extra space where there would ordinarily not be any. It should also wrap lines in any situation where they exceed the width of the containing element, such as with this sentence. + + There should also be preservation of returns +as this sentence + very clearly demonstrates. +

    + +

    +[cl5] This paragraph should not show extra spaces where there would ordinarily not be any; in other words, whitespace is collapsed. It should also wrap lines in any situation where they exceed the width of the containing element, such as with this sentence. + + However, there should be preservation of returns +as this sentence + very clearly demonstrates. +

    + + + diff --git a/width-pad.html b/width-pad.html new file mode 100644 index 0000000..d4199a3 --- /dev/null +++ b/width-pad.html @@ -0,0 +1 @@ +
    The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog.
    The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog.
    The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog.
    \ No newline at end of file diff --git a/width-test.html b/width-test.html new file mode 100644 index 0000000..d4dd16b --- /dev/null +++ b/width-test.html @@ -0,0 +1,21 @@ + + + +Width Expansion? + + + + +
    +
    +
    +
    + + + diff --git a/winie/table-double/13.html b/winie/table-double/13.html new file mode 100644 index 0000000..977aaa6 --- /dev/null +++ b/winie/table-double/13.html @@ -0,0 +1,121 @@ + + + + +Corporate Versus Freelance: Details + + + + + + +
    + +Findings from the survey for people who make websites, 2008 +
    + +
    + +
    + + +

    Fig. 13.9 Profit versus non-profit

    + + + + + + + + + + + + + + + + + + + + + + + + +
    Partner in a large company or organization

    91.7%

    8.3%

    Partner in a small business

    98.2%

    1.8%

    Employee of a company, university, library, +museum, nonprofit, or other organization

    79.1%

    20.9%

    Overall

    81.6%

    18.4%

    For-profitNon-profit
    + + +

    Fig. 13.9 Profit versus non-profit

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Partner in a large company or organization

    91.7%

    8.3%

    Partner in a small business

    98.2%

    1.8%

    Employee of a company, university, library, +museum, nonprofit, or other organization

    79.1%

    20.9%

    Overall

    81.6%

    18.4%

    For-profitNon-profit
    + +

    Fig. 13.9 Profit versus non-profit

    + + + + + + + + + + + + + + + + + + + + + + + + +
    Partner in a large company or organization

    91.7%

    8.3%

    Partner in a small business

    98.2%

    1.8%

    Employee of a company, university, library, +museum, nonprofit, or other organization

    79.1%

    20.9%

    Overall

    81.6%

    18.4%

    For-profitNon-profit
    + + +
    + + + +
    + + + diff --git a/winie/table-double/c/base.css b/winie/table-double/c/base.css new file mode 100644 index 0000000..5e70f6d --- /dev/null +++ b/winie/table-double/c/base.css @@ -0,0 +1,72 @@ +@import url(reset.css); + +html {border-top: 5px solid #1E769B;} +body {font: 90%/1.67 Georgia, Palatino, "Palatino Linotype", Times, "Times New Roman", serif; + color: #333; background: #FFF; + counter-reset: subhead; + border-top: 68px solid #FBFAF4;} +h1, h2, h3, h4, table {font: 1em Arial, "Helvetica Neue", Helvetica, sans-serif;} +h1, h2, h3, h4 {font-weight: bold;} +a:link {color: #1E769B;} +a:visited {color: #666;} + +.ludacris {width: 968px; margin: 0 auto; + position: relative;} + +.header {position: absolute; top: -65px; left: 0; width: 100%;} +.header .logo {position: absolute; top: 5px; left: 17px;} +.header .tag {position: absolute; top: 18px; left: 270px;} + +.main h1 {font-size: 280%; margin-bottom: 0.2em;} +.main h2 {font-size: 210%; font-weight: normal; color: #666; + margin-top: 1.25em; margin-bottom: 0.33em;} +.main p.tagline {margin: -0.25em 0 0.75em; + font-size: 125%; + color: #7B7960;} +.main h3 {margin: 2.25em 0 0.25em; font-size: 125%;} +.main h3 b {font-size: 75%; text-transform: uppercase; + color: #666; padding-right: 0.25em;} +.main h4 {margin: 2.5em 0 0.75em; + text-transform: uppercase; font-size: 125%; + color: #928F59;} + +.main p {margin: 0 0 1em;} +.main ul, .main ol {padding-left: 1.75em; margin: 1em 0;} +.main ul li, .main ol li {list-style: disc; margin: 0.5em 0;} +.main ol li {list-style: decimal;} + +.main {margin: 0 10px 0 270px; padding-top: 2.5em;} +.nav {positIon: absolute; top: 3em; left: 15px; width: 15em; + margin: 0 0.75em 2.5em 0; + border-bottom: 1px solid #CCC;} +.nav li a {display: block; padding: 0.3em 0; + font-size: 90%; text-decoration: none; + color: #7B7960; + border-top: 1px solid #CCC;} +.nav li a b {font-weight: normal;} +.nav li.current a, .nav li a:hover {color: #000;} +.nav li.current ol {background: #FBFAF4; border-top: 1px solid #000;} +.nav li.current li {padding-left: 0.75em; + font: 93% Arial, "Helvetica Neue", Helvetica, sans-serif;} +.nav li.current ol li:first-child a {border-top: 0;} +.nav li.current li a {padding: 0.45em 1em 0.45em 1.75em; text-indent: -2em; + color: #1E769B;} +.nav li.current li a:hover {color: #B00;} +.nav li.current li a b {padding-right: 0.25em; text-transform: uppercase; + color: #7B7960;} + +.jump {margin: 2em 0 2em 19em; overflow: auto;} +.jump li {border: 1px solid #D7D7D8; + background: #FDFCF8 no-repeat;} +.jump li a {display: block; padding: 23px 0.75em 0.5em; + font: bold 115% Arial, "Helvetica Neue", Helvetica, sans-serif; + text-decoration: none; + color: #1E769B;} +.jump li a:hover {color: #000;} +.jump .prev {float: left; background-image: url(prev.gif); background-position: 0.75em 9px;} +.jump .next {float: right; background-image: url(next.gif); background-position: 95% 9px;} + +.footer {margin: 0 0 3em 19em; padding: 0.75em; + border-top: 1px solid #CCC; + clear: both;} +.footer p {font-size: smaller;} diff --git a/winie/table-double/c/charts.css b/winie/table-double/c/charts.css new file mode 100644 index 0000000..5d58fe8 --- /dev/null +++ b/winie/table-double/c/charts.css @@ -0,0 +1,115 @@ +table {padding: 0.5em; margin: 0.25em 0 1em; + border-top: 3px solid #CECAA1; border-bottom: 2px solid #DDDABE; + font-size: 90%; + overflow: hidden; + border-separate: separate; border-spacing: 0;} +table th, table td {padding: 0.25em 0.4em; + vertical-align: middle;} +.main table p {margin: 0;} +p.note {font-style: italic; font-size: 92.5%; margin: -0.75em 0 0.75em;} + +/* data tables */ + +table.data th, table.data td {border: 1px solid #CCC; border-width: 0 1px 1px 0; + padding: 0.6em 0.33em 0.4em; + text-align: right;} +table.data th {background: #E0EFF5;} +table.data thead th {vertical-align: bottom; border-top: 1px solid #CCC;} +table.data thead th:empty {border-top: none; background: none;} +table.data tbody th, table.data tfoot th {text-align: left; border-left: 1px solid #CCC;} + +table.data tbody td {width: 4em;} +table.data tbody td.zero {color: #666;} +table.data tbody td.hilt {background: #EEE;} +table.data thead th.total, table.data tbody td.total { + border-left: 2px solid #CCC; color: gray;} +table.data tfoot {color: gray;} +table.data tfoot th, table.data thead th.total { + text-align: right; background: none; padding: 0.6em 0.33em 0.4em;} +table.data tfoot th, table.data tfoot td {border-top: 2px solid #CCC;} + +/* bar charts */ + +table.chart {padding-left: 0.25em; width: 100%;} +table.chart tbody th {text-align: right;} + +table.chart.bar {padding-right: 4em;} +table.chart.bar tbody td {width: 30em;} +table.chart.bar tbody td p {position: relative; top: 0; + padding: 3px 0 1px 1px; height: 1em; + text-align: right; + background-color: #5CB9DC;} +table.chart.bar tbody td p span {position: absolute; top: 0.25em; left: 100%; + margin-left: 0.33em; font-size: 93%;} + +table.chart.bar.t10 tbody td div {width: 1000%;} +table.chart.bar.t20 tbody td div {width: 500%;} +table.chart.bar.t25 tbody td div {width: 400%;} +table.chart.bar.t30 tbody td div {width: 333.3%;} +table.chart.bar.t40 tbody td div {width: 250%;} +table.chart.bar.t50 tbody td div {width: 200%;} +table.chart.bar.t60 tbody td div {width: 166.7%;} +table.chart.bar.t70 tbody td div {width: 142.8%;} +table.chart.bar.t75 tbody td div {width: 133.3%;} +table.chart.bar.t80 tbody td div {width: 125%;} +table.chart.bar.t90 tbody td div {width: 111%;} +table.chart.bar.t100 tbody td div {width: 100%;} + + +/* combo bar charts */ + +table.chart.combo tbody th, table.chart.combo tbody td {padding: 0.15em 0.25em;} +table.chart.combo tbody th {white-space: pre;} +table.chart.combo tbody td p {padding: 0.33em 0;} +table.chart.combo tbody td p span {font-size: 93%; padding: 0 0.5em;} +table.chart.combo tfoot th {padding-top: 1em;} + +/* duos */ + +table.chart.combo.double tbody td {width: 50%;} +table.chart.combo.double tbody td div {background: #5CB9DC;} +table.chart.combo.double tbody td.p1 div {width: 200%;} +table.chart.combo.double tbody td.p1 p {text-align: left; + background-color: #B2D43A; position: relative; z-index: 1;} + +table.chart.combo.double tbody td.p2 {text-align: right;} +table.chart.combo.double tbody td.p2 p {width: auto !important; position: relative; z-index: 2;} + +table.chart.combo.double tfoot th span {padding-left: 0.5em; border-left: 1.2em solid;} +table.chart.combo.double tfoot th.p1 span {border-left-color: #B2D43A;} +table.chart.combo.double tfoot th.p2 span {border-left-color: #5CB9DC;} + +/* treys */ + +table.chart.combo.triple tbody td {width: 33%;} +table.chart.combo.triple tbody td div {width: 300%; position: relative;} + +table.chart.combo.triple tbody td.p1 div {background: #FEA318;} +table.chart.combo.triple tbody td.p1 p {text-align: left; + background-color: #B2D43A;} + +table.chart.combo.triple tbody td.p2 {text-align: center; vertical-align: top;} +table.chart.combo.triple tbody td.p2 div {margin-left: -100%; + position: relative; z-index: 100; background: none;} +table.chart.combo.triple tbody td.p2 p {position: absolute; + padding: 0.33em 0;} + +table.chart.combo.triple tbody td.p3 div {margin-left: -200%;} +table.chart.combo.triple tbody td.p3 {text-align: right;} +table.chart.combo.triple tbody td.p3 p {margin-left: auto; + background: #5CB9DC;} + +table.chart.combo.triple tfoot th span {padding-left: 0.5em; border-left: 1.2em solid;} +table.chart.combo.triple tfoot th.p1 span {border-left-color: #B2D43A;} +table.chart.combo.triple tfoot th.p2 span {border-left-color: #FEA318;} +table.chart.combo.triple tfoot th.p3 span {border-left-color: #5CB9DC;} + +/* IE7 hack to fix middle bars on treys */ + +* html table.chart.combo.triple tbody td.p2 div {margin-left: -105%; margin-right: -106%;} +*+html table.chart.combo.triple tbody td.p2 div {margin-left: -105%; margin-right: -106%;} + +/* to prevent bar growth */ + +* html table.chart.combo tbody th, +*+html table.chart.combo tbody th {white-space: nowrap;} diff --git a/winie/table-double/c/header-logo-filled.gif b/winie/table-double/c/header-logo-filled.gif new file mode 100644 index 0000000..5eb7f0a Binary files /dev/null and b/winie/table-double/c/header-logo-filled.gif differ diff --git a/winie/table-double/c/header-logo.gif b/winie/table-double/c/header-logo.gif new file mode 100644 index 0000000..b4e7128 Binary files /dev/null and b/winie/table-double/c/header-logo.gif differ diff --git a/winie/table-double/c/header-tag-filled.gif b/winie/table-double/c/header-tag-filled.gif new file mode 100644 index 0000000..8e7ddac Binary files /dev/null and b/winie/table-double/c/header-tag-filled.gif differ diff --git a/winie/table-double/c/header-tag.gif b/winie/table-double/c/header-tag.gif new file mode 100644 index 0000000..343fe15 Binary files /dev/null and b/winie/table-double/c/header-tag.gif differ diff --git a/winie/table-double/c/next.gif b/winie/table-double/c/next.gif new file mode 100644 index 0000000..f4f008c Binary files /dev/null and b/winie/table-double/c/next.gif differ diff --git a/winie/table-double/c/prev.gif b/winie/table-double/c/prev.gif new file mode 100644 index 0000000..1dd4c9a Binary files /dev/null and b/winie/table-double/c/prev.gif differ diff --git a/winie/table-double/c/reset.css b/winie/table-double/c/reset.css new file mode 100644 index 0000000..14a193b --- /dev/null +++ b/winie/table-double/c/reset.css @@ -0,0 +1,32 @@ +html, body, div, span, applet, object, iframe, +h1, h2, h3, h4, h5, h6, p, blockquote, pre, +a, abbr, acronym, address, big, cite, code, +del, dfn, em, font, img, ins, kbd, q, s, samp, +small, strike, strong, sub, sup, tt, var, +b, u, i, center, +dl, dt, dd, ol, ul, li, +fieldset, form, label, legend, +table, caption, tbody, tfoot, thead, tr, th, td { + margin: 0; + padding: 0; + border: 0; + outline: 0; + font-size: 100%; + vertical-align: baseline; +} +ol, ul { + list-style: none; +} +blockquote, q { + quotes: none; +} +blockquote:before, blockquote:after, +q:before, q:after { + content: ''; + content: none; +} + +table { + border-collapse: separate; + border-spacing: 0; +} diff --git a/winie/table-double/testcase.html b/winie/table-double/testcase.html new file mode 100644 index 0000000..1d9098b --- /dev/null +++ b/winie/table-double/testcase.html @@ -0,0 +1,115 @@ + + + +Test case + + + + + + + + + + + + + + + + + + + + + + + + + +
    A heading

    75%

    2nd

    A heading
    with a line break

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    + + + + + + + + + + + + + + + + + + + + + + +
    A heading

    75%

    2nd

    A heading
    with a line break

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    + + + + + + + + + + + + + + + + + + + + + + +
    A heading

    75%

    2nd

    A heading
    with a line break

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    A heading +with a CR and pre

    75%

    2nd

    + + + diff --git a/winie5/ie55-pflbug.html b/winie5/ie55-pflbug.html new file mode 100644 index 0000000..96b494f --- /dev/null +++ b/winie5/ie55-pflbug.html @@ -0,0 +1 @@ + IE5.5: Bug mit P:first-letter? .......

    Testtext

    erschienen in 2001

    Anschrift

    \ No newline at end of file diff --git a/winie7/attr-gif-jpg.html b/winie7/attr-gif-jpg.html new file mode 100644 index 0000000..41c623a --- /dev/null +++ b/winie7/attr-gif-jpg.html @@ -0,0 +1,199 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/attr-id.html b/winie7/attr-id.html new file mode 100644 index 0000000..734afbc --- /dev/null +++ b/winie7/attr-id.html @@ -0,0 +1,196 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/attr-noalt.html b/winie7/attr-noalt.html new file mode 100644 index 0000000..e10c135 --- /dev/null +++ b/winie7/attr-noalt.html @@ -0,0 +1,199 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/attr-scope.html b/winie7/attr-scope.html new file mode 100644 index 0000000..816498a --- /dev/null +++ b/winie7/attr-scope.html @@ -0,0 +1,406 @@ + + + +An Event Apart Boston 2007 + + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + + +

    BOSTON — March 26–27, 2007

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26-27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + + + +
    + +

    The Schedule

    +

    +An Event Apart Boston runs from 9:00 am–5:30 pm, with an opening night party starting at 6:30 pm. We have a lot to cover, so the event will start promptly. Arrive early to get a good seat! Doors open at 8:00 am; for best results, plan to show up between 8:00 am and 8:30 am. +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
     Day 1Day 2
    9:00 am +

    Secrets of the CSS Jedi

    +

    Eric Meyer

    +

    +How much time do you spend either desperately fighting or blindly accepting browser defaults? More than you might think. Truly understanding both sides of this struggle is critical for anyone who wants to be a CSS Master. This will be an in-depth exploration of how CSS really works, and how this knowledge can make your work easier. +

    +
    +

    Good vs. Great Design

    +

    Cameron Moll

    +

    +It’s easy to poke fun at bad design, but it’s far more challenging—and rewarding—to discern differences between good design and great design. This session will teach you practical design techniques for tipping the scales of greatness in your favor, using a blend of graphic design theory, human computing principles, and a communication-centric approach. +

    +
    10:00 am +

    BREAK

    +
    +  +
    10:15 am +

    Writing the User Interface

    +

    Jeffrey Zeldman

    +

    +Drop-shadows don’t fill shopping carts. Aside from a few buttons and arrows, nearly all of the work of a user interface is performed by words. Yet most designers don’t question the text their clients dump on them, and most budgets don’t cover editing and writing. Learn how word choice can drastically improve design, branding, and usability—and how to edit web content effectively, even if you’re not a writer. +

    +
    +

    Web Standards Stole My Truck

    +

    Ethan Marcotte

    +

    +CSS have you singing a country tune? Feel like XHTML or the DOM ran off with your dog, your girlfriend, or—even worse—your design? We’ll discuss what it really means to design with standards, and learn how to get the keys to your trailer back. +

    +
    11:15 am +

    BREAK

    +
    +  +
    11:30 am +

    Redesigning Your Way Out of a Paper Bag

    +

    Jason Santa Maria

    +

    +Ninety percent of web design is redesign. Every redesign should serve a purpose beyond mere freshening. Rethinking an existing brand can be a designer’s most exciting (and most perilous) challenge. Happy Cog’s Jason Santa Maria should know, having recently redesigned beloved and respected brands including AIGA and A List Apart. Learn how color, typography, and visual metaphors can change the way people experience even the most familiar sites. +

    +
    +

    Building Better Browsers

    +

    Molly E. Holzschlag

    +

    +The bane of the web developer’s existence, browsers can be our greatest love +or our worst enemy. Learn about the history, development, evolution and +promise of browsers for the web and beyond, and find out how you can better +understand browsers and participate in the way the software we work hard to +tame evolves. +

    +
    12:30 pm +

    Lunch

    +

    Partially Sponsored by Adobe

    +
    +  +
    2:00 pm +

    The Web Usability Diet

    +

    Steve Krug

    +

    +Usability is a bit like eating sensibly: we all know it’s good for us (and our websites), but that doesn’t necessarily mean we’re going to do it. In the last year, Steve Krug has found himself paring down his simple message even more, so everyone can find time for it. Come hear his latest thinking on what you really need to do about usability—and why it’s less than you think. +

    +
    +

    The State of CSS in an IE7 World

    +

    Eric Meyer

    +

    +After five quiet (and increasingly frustrating) years, the 800-pound gorilla is awake once more. We know that Internet Explorer 7 fixed a lot of bugs and added new support, but with IE6 still hanging around like an annoying party crasher, has anything really changed? We’ll take a look at where we are and where we’re going in an IE7 world. +

    +
    3:00 pm +

    BREAK

    +
    +  +
    3:15 pm +

    Beyond Basic Access

    +

    Andrew Kirkpatrick (Adobe)

    +

    +Designers already know about the basics of accessibility for people with disabilities. This session addresses the more complex issues that must be mastered when developing interactive experiences with XHTML, CSS, and JavaScript, and will show how to quickly determine what users with different abilities need to provide meaningful accessible experiences. +

    +
    +

    Selling Design

    +

    Jeffrey Zeldman

    +

    +It takes talent, knowledge, and experience to design great websites. But what’s the use if your client (or boss) consistently kills your best work? Great design requires great clients, and they are made, not born. Learn to identify receptive clients and bosses and develop an inclusive, collaborative process that builds the level of trust needed to sell great work. +

    +
    4:15 pm +

    BREAK

    +
    +  +
    4:30 pm +

    Interface Design Juggling

    +

    Dan Cederholm

    +

    +Keeping all the right pieces in play when designing for the web can be a balancing act. This session will focus on being an independent interface designer in a complex world of endless choices. Learn how streamlined process and smart approaches can make for compelling, adaptable designs with XHTML and CSS. You’ll soon be juggling microformats, typography and flexible design with ease. +

    +
    +

    Critiques

    +

    Eric Meyer, Jason Santa Maria, Jeffrey Zeldman and Guests

    +

    +A rip-snortin’ romp through the design, code, usability, branding and content of sites created by some of the smartest people in the world—namely, the attendees of An Event Apart Boston. +

    +
    6:30 pm–??? +

    Opening Night Party

    +

    Sponsored by (mt) Media Temple

    +

    Restaurant 33
    +33 Stanhope Street
    +Boston, MA 02116 (Map)
    Open Bar | Munchies | Grooves

    +

    +Free food! Free drinks! Network, network, network! Dance to the mellow grooves. Eat, drink, and make contacts.

    + + + +
    +  +
    + +

    Great hotel, special savings

    +

    +The Boston Marriott Copley Place has arranged special room rates for Event Apart attendees, starting at $215. To get these savings, book your room online or call 1-617-236-5800 and say you need the “special Event Apart room rate.” +

    + +

    Located in beautiful and historic Back Bay, just off the Massachusetts Turnpike, four miles from Logan Airport and five minutes from the Back Bay Amtrak station, the hotel provides in-room, high-speed internet access; laptop safes and coolers; 27-inch color TV with cable movies, in-room pay movies, Web TV and Gameboy; luxurious bedding and linens, and more. Best of all, it’s the site of the conference. You can walk out of your room and into the show!

    + + +
    + +
    + + + +
    + + + + + diff --git a/winie7/attr-selflinks.html b/winie7/attr-selflinks.html new file mode 100644 index 0000000..1125348 --- /dev/null +++ b/winie7/attr-selflinks.html @@ -0,0 +1,197 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/children.html b/winie7/children.html new file mode 100644 index 0000000..c946971 --- /dev/null +++ b/winie7/children.html @@ -0,0 +1,199 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/fixed-footer.html b/winie7/fixed-footer.html new file mode 100644 index 0000000..961351d --- /dev/null +++ b/winie7/fixed-footer.html @@ -0,0 +1,205 @@ + + + +An Event Apart + + + + + + + + + + +
    +An Event Apart: For People Who Make Websites +
    +
    + + +
    + +
    + +

    +Join Eric Meyer, Jeffrey Zeldman, and special guests +to gain a deeper understanding of web standards and emerging best practices. Be inspired by fresh ideas and new directions. Join the greatest minds and hottest talents in web design today. +

    + +
    + +
    +BOSTON +SOLD OUT +
      +
    • March 26–27, 2007
    • +
    • Boston Marriott Copley
    • +
    • SOLD OUT | SCHEDULE
    • +
    +
    + +

    Featured Speakers for An Event Apart Boston

    + + + +

    +All that, and we critique your websites! Hey, you might even win a prize... +

    + +
    + +
    + +
    + +

    Upcoming Events

    +
      +
    • SEATTLE +

      Registration opens March 15!

      +
    • +
    + +
    + +
    +

    An Event Apart News

    + + +

    + An Event Apart RSS feed (what's this?) +

    + +
    + +
    + +
    + + + +
    + + + + + diff --git a/winie7/ie7talk.txt b/winie7/ie7talk.txt new file mode 100644 index 0000000..c871f94 --- /dev/null +++ b/winie7/ie7talk.txt @@ -0,0 +1,208 @@ +Added things + +Fixed positioning +min-width, max-width +min-height, max-height +Attribute selectors +Child selector +Adjacent sibling selector +:first-child +Chained classes and pseudo-classes +Arbitrary-element :hover +Full background-attachment: fixed +Alpha channel in PNG images +ABBR tag + + +-- + +They fixed fixed! + +div#footer { + position: fixed; + bottom: 0; + left: 0; right: 0; + padding: 0.5em 1em; + background: white; + border-top: 1px solid gray; +} +body { + padding-bottom: 5em; +} + +-- + +body > div { + border: 1px solid red; +} +body > div > div { + border: 1px dotted red; +} + +-- + +#ericmeyer > *:first-child { + cuteness: 100; +} + +#ericmeyer:first-child { + pedantics: xx-large; +} + +td:first-child { + background: yellow; +} + +-- + +Attribute selectors + +CSS2.1 + +[attr] +[attr="val"] +[attr~="val"] +[attr|="val"] + +CSS3 + +[attr*="val"] +[attr^="val"] +[attr$="val"] + +-- + +img[src$=".gif"] { + border: 3px solid red; +} +img[src$=".jpg"] { + border: 3px solid lime; +} + + +div[id] { + border: 1px dotted red; + margin: 1px; +} + + +img { + border: 5px solid red; +} +img[alt] { + border-style: none !important; +} + + +-- + +a[href$=".pdf"] { + padding-right: 18px; + background: url(/pix/pdf-icon.gif) + 100% 50% no-repeat; +} + +a[title*="(PDF"] { + padding-right: 18px; + background: url(/pix/pdf-icon.gif) + 100% 50% no-repeat; +} + +*[href*="aneventapart.com"] { + font-weight: bold; + color: maroon; + background: #AEA571; +} + +th[scope="col"] { + border-top: 1px solid black; + border-bottom: 1px solid black; +} +th[scope="row"] { + border-right: 1px solid black; +} +th[scope="row"] + td { + padding-left: 0.75em; +} + + +-- + +What about Number 6? + +Dean Edwards has your fix + +-- + +Dead bugs + +Peekaboo bug +Guillotine bug +Duplicate character bug +Duplicate indent +3-pixel text jog +Creeping text bug +Double float margin bug +Bottom margin bug on hover +IE/Win line-height bug +Quirky percentages in IE +List item whitespace bug +Moving viewport scrollbar outside HTML borders +Border chaos +Text highlighting under a top border +No Scroll bug +Disappearing list background +width:auto +Dotted border style +XML prolog triggering quirks mode + +-- + +Dead parsing bugs + +* html +html>body +head+body +_height +overriding !important + +-- + +New and surviving parsing bugs! + +*+html +html* +html>/**/body +@import media + +-- + +What the Hack...? + +Conditional comments are reliable and reduce the kabbalistic quotient in your CSS + +* html #example {height: 0;} +*+html #example {min-height: 0;} + + + +div#footer { + position: fixed; + bottom: 0; + left: 0; right: 0; + padding: 0.5em 1em; + background: white; + border-top: 1px solid gray; +} +* html div#footer { + position: absolute; +} +body { + padding-bottom: 5em; + position: relative; +} + +-- + +Layout-wise, it's pretty much like any other current browser (FF, Safari, Opera, etc.) with the inevitable weird quirks here and there + diff --git a/winie8/linktest.html b/winie8/linktest.html new file mode 100644 index 0000000..94dd5ef --- /dev/null +++ b/winie8/linktest.html @@ -0,0 +1,36 @@ + + + +Linktest + + + + +
    + +
    + + + +
    +

    Here's some content.

    +
    + + +