<\/p>\n
This is a test paragraph.<\/p>\n
This is a test paragraph.<\/p>\n
This is a test paragraph.<\/p>\n
This is a test paragraph.<\/p>\n
This is a test paragraph.<\/p>\n
This is a normal paragraph ( This is another paragraph. I think it needs to be added that This is a block quotation containing a single The following contains address information about the author, in an This is a paragraph before an unnumbered<\/strong> list ( <\/p>\n The following is a <\/p>\n This is a paragraph before a definition<\/strong> list ( Some of the elements tested above are typically displayed in a monospace This is a text paragraph that contains somep<\/code> element).
\nTo add some length to it, let us mention that this page was
\nprimarily written for testing the effect of user style sheets<\/strong>.
\nYou can use it for various other purposes as well, like just checking how
\nyour browser displays various HTML elements by default.
\nIt can also be useful when testing conversions from HTML
\nformat to other formats, since some elements can go wrong then.<\/p>\n
\nthe set of elements tested is not exhaustive in any sense. I have selected
\nthose elements for which it can make sense to write user style sheet rules,
\nin my opionion.<\/p>\ndiv<\/code> element. Authors may use such elements instead
\nof paragraph markup for various reasons. (End of div<\/code>.)<\/div>\n
\nparagraph. Well, not quite, since this is not really<\/em>
\nquoted text, but I hope you understand the point. After all, this
\npage does not use HTML markup very normally anyway.<\/p><\/blockquote>\naddress<\/code>
\nelement.<\/p>\nJukka Korpela<\/a>,
\njkorpela@cs.tut.fi<\/a>
\nP\u00e4iv\u00e4ns\u00e4teenkuja 4 A, Espoo, Finland<\/address>\nLists<\/h2>\n
ul<\/code>). Note that
\nthe spacing between a paragraph and a list before or after that is hard
\nto tune in a user style sheet. You can’t guess which paragraphs are
\nlogically related to a list, e.g. as a „list header“.<\/p>\n\n
\nfor short items lists look better if they are compactly presented,
\nwhereas for long items, it would be better to have more vertical spacing between items.<\/li>\n
\nLet us terminate the list now without making any more fuss about it.<\/li>\n<\/ul>\ndir<\/code> list:<\/p>\n\n
\nprobably wrap to the next line in rendering.
\nThis is a paragraph before a numbered<\/strong> list (ol<\/code>). Note that
\nthe spacing between a paragraph and a list before or after that is hard
\nto tune in a user style sheet. You can’t guess which paragraphs are
\nlogically related to a list, e.g. as a „list header“.<\/p>\n\n
\nitems are short, lists look better if they are compactly presented,
\nwhereas for long items, it would be better to have more vertical spacing between items.<\/li>\n
\nLet us terminate the list now without making any more fuss about it.<\/li>\n<\/ol>\ndl<\/code>).
\nIn principle, such a list should consist of terms<\/em> and associated
\ndefinitions.
\nBut many authors use dl<\/code> elements for fancy „layout“ things. Usually the
\neffect is not too<\/em> bad, if you design user style sheet rules for dl<\/code>
\nwhich are suitable
\nfor real definition lists.<\/p>\nText-level markup<\/h2>\n
\n
\nabbr<\/code> markup used)<\/li>\nacronym<\/code> markup used)<\/li>\nb<\/code> markup used – just bolding with unspecified
\nsemantics)<\/li>\nbig<\/code> markup used)<\/li>\nfont size=6<\/code> markup used)<\/li>\nfont face=Courier<\/code> markup used)<\/li>\nfont color=red<\/code> markup used)<\/li>\n
\ncite<\/code> markup used)<\/li>\na[i] = b[i] + c[i);<\/code> (computer code; code<\/code> markup used)<\/li>\ndeleted<\/del> text (del<\/code> markup used)<\/li>\n
\n(dfn<\/code> markup used for the term being defined)<\/li>\nem<\/code> markup used for emphasizing
\na word)<\/li>\ni<\/code> markup used)<\/li>\nins<\/code> markup used)<\/li>\nkbd<\/code> markup
\nused for text indicating keyboard input)<\/li>\nHello!<\/q> (
q<\/code> markup used for quotation)<\/li>\nShe said
Hello!<\/q><\/q> (a quotation inside a quotation)<\/li>\n
\n(samp<\/code> markup used for sample output)<\/li>\nsmall<\/code> markup used)<\/li>\nstrike<\/code> markup used; note:
\ns<\/code> is a nonstandard synonym for strike<\/code>)<\/li>\nstrong<\/code>
\nmarkup used)<\/li>\nsub<\/code> and
\nsup<\/code> markup) work inside running text, we need some
\ndummy text around constructs like x1<\/sub> and H2<\/sub>O
\n(where subscripts occur). So here is some fill so that
\nyou will (hopefully) see whether and how badly the subscripts
\nand superscripts mess up vertical spacing between lines.
\nNow superscripts: Mlle<\/sup>, 1st<\/sup>, and then some
\nmathematical notations: ex<\/sup>, sin2<\/sup> x<\/i>,
\nand some nested superscripts (exponents) too:
\nex2<\/sup><\/sup> and f(x)g(x)a+b+c<\/sup><\/sup>
\n(where 2 and a+b+c should appear as exponents of exponents).<\/li>\ntt<\/code> markup used)<\/li>\nu<\/code> markup used)<\/li>\ncat<\/code> filename<\/var> displays the
\nfile specified by the filename<\/var> (var<\/code> markup
\nused to indicate a word as a variable).<\/li>\n<\/ul>\n
\nfont, often using the same<\/em> presentation for all of them. This
\ntests whether that is the case on your browser:<\/p>\n\n
This is sample text inside code markup<\/code><\/li>\nLinks<\/h2>\n
\n
\ninline links. Generally, inline links (as opposite to e.g. links
\nlists) are problematic
\nfrom the
\nusability<\/a> perspective,
\nbut they may have use as
\n\u201cincidental\u201d, less relevant links. See the document
\nLinks Want To Be Links<\/a><\/cite>.<\/p>\nForms<\/h2>\n