Netscape 6.1 applies an underline effect to this element along
16 | with a special mouse cursor when hovering (an arrow with a question mark.) Later
17 | versions apply only a dotted underline effect.
18 |
Opera 7+ applies a dotted underline effect to this element;
19 | in previous versions no special extra formatting was applied.
11 |
12 |
13 | filler text 1234 Nowhere St. Anywhere, State 00001-9999 filler text
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/a/ahref-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | A HREF: Browser peculiarity - TITLE used as label for IE FAVORITES
6 |
9 |
10 |
11 |
12 |
13 | Assertions:
14 |
IE4+ uses the TITLE attribute as the Favorites label for a URL
15 | when placed via the right-mouseclick context menu.
16 |
17 |
18 | Hyperlink to a document, no TITLE attribute.
19 | Right click...Add to favorites to see the Name label used
20 |
21 | filler text http://www.yahoo.com/ filler text
22 |
23 |
24 |
25 | Hyperlink to a document, TITLE="this is a title" present.
26 | Right click...Add to favorites to see the Name label used
27 |
28 | filler text http://www.yahoo.com/ filler text
29 |
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/a/applet-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | APPLET: Browser peculiarity - mouse events and select/highlighting an applet
6 |
9 |
10 |
11 |
12 |
13 | Assertions:
14 |
A bad bug exists in the Netscape 6 betas where selecting text
15 | that included an applet would crash the browser if a mouse event handler was
16 | attached to the applet. This was fixed by 6.0 final.
17 |
18 |
19 |
20 | Test: Use the mouse to select the "filler text" on both sides of the applet
21 |
22 | filler text
23 |
27 | filler text
28 |
29 |
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/a/arealocaltest.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | AREA: Default destination
6 |
7 |
8 |
9 |
10 |
Netscape and Opera both ignore improperly terminated URLs used
16 | as the BASE HREF value. eg: relative URLs in a document that used "http://www.blooberry.com"
17 | as the HREF would resolve to "http://[relative URL]", and "http://www.blooberry.com/indexdot"
18 | would resolve to "http://www.blooberry.com/[relative URL]". To prevent this problem, use
19 | a trailing "/" character to properly terminate the URL. Internet Explorer, by the way, accepts both URL forms.
20 |
21 |
22 | BASE element refers to "http://www.blooberry.com/indexdot/", hyperlink refers to "index.html"
23 | (Should successfully link to the Indexdot main page):
24 |
25 | filler text
26 | Link to "index.html"
27 | filler text
28 |
29 |
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/base-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BASE: Browser Peculiarities: Handling improperly terminated URLs
6 |
7 |
10 |
11 |
12 |
13 |
14 | Assertion:
15 |
Netscape and Opera both ignore improperly terminated URLs used
16 | as the BASE HREF value. eg: relative URLs in a document that used "http://www.blooberry.com"
17 | as the HREF would resolve to "http://[relative URL]", and "http://www.blooberry.com/indexdot"
18 | would resolve to "http://www.blooberry.com/[relative URL]". To prevent this problem, use
19 | a trailing "/" character to properly terminate the URL. Internet Explorer, by the way, accepts both URL forms.
20 |
21 |
22 | BASE element refers to "http://www.blooberry.com/indexdot", hyperlink refers to "index.html"
23 | (Should link to the blooberry.com site main page instead of the Indexdot main page like you might expect):
24 |
25 | filler text
26 | Link to "index.html"
27 | filler text
28 |
29 |
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/basefont-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BASEFONT: Browser peculiarity - application on heading levels
6 |
9 |
10 |
11 |
12 |
13 | Assertions:
14 |
Neither Internet Explorer or Netscape 1.0-4.x apply the BASEFONT
15 | SIZE attribute value to heading levels. Internet Explorer does apply the FACE and
16 | COLOR values to headings though.
The CITE attribute is exposed in Netscape 6.1+ by invoking a
15 | context menu on the element (PC: right clicking) and choosing "properties."
16 | The value of CITE for the test element below is: "http://www.example.com/bqcitation.htm"
If the background image fails to download for any reason and
17 | no BGColor is specified it is common practice for browsers not to apply the other
18 | coloring attributes (this ensures readability with the default browser color schemes.)
19 |
20 |
21 | This document contains a valid background URL reference, text=#0000cc (blue),
22 | link=yellow, vlink=#ff0000. BGColor is specified: #808080.
23 |
24 | filler text
25 | Link text
26 | VLink text
27 | filler text
28 |
29 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/body-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BODY: Browser peculiarity/tip - BODY attributes with invalid BACKGROUND and
6 | no BGCOLOR
7 |
10 |
11 |
12 |
14 |
15 | Assertion:
16 |
If the background image fails to download for any reason and
17 | no BGColor is specified it is common practice for browsers not to apply the other
18 | coloring attributes (this ensures readability with the default browser color schemes.)
19 |
20 |
21 | This document contains a valid background URL reference, text=#0000cc (blue),
22 | link=yellow, vlink=#ff0000. No BGColor is specified.
23 |
24 | filler text
25 | Link text
26 | VLink text
27 | filler text
28 |
29 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/body-bp4.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BODY: Browser peculiarity/tip - BODY attributes with invalid BACKGROUND and
6 | no BGCOLOR
7 |
10 |
11 |
12 |
14 |
15 | Assertion:
16 |
If the background image fails to download for any reason and
17 | no BGColor is specified it is common practice for browsers not to apply the other
18 | coloring attributes (this ensures readability with the default browser color schemes.)
19 |
20 |
21 | This document contains an invalid background URL reference, text=#0000cc (blue),
22 | link=yellow, vlink=#ff0000. BGColor is specified: #808080.
23 |
24 | filler text
25 | Link text
26 | VLink text
27 | filler text
28 |
29 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/body-bp5.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BODY: Browser peculiarity/tip - BODY attributes with invalid BACKGROUND and
6 | no BGCOLOR
7 |
10 |
11 |
12 |
14 |
15 | Assertion:
16 |
If the background image fails to download for any reason and
17 | no BGColor is specified it is common practice for browsers not to apply the other
18 | coloring attributes (this ensures readability with the default browser color schemes.)
19 |
20 |
21 | This document contains an invalid background URL reference, text=#0000cc (blue),
22 | link=yellow, vlink=#ff0000. No BGColor is specified.
23 |
24 | filler text
25 | Link text
26 | VLink text
27 | filler text
28 |
29 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/b/br-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | BR: Browser Peculiarities: absorbed linefeeds
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
If you use a BR at the end of a block structuring element (ex: BLOCKQUOTE)
15 | or block structuring sub element (ex: LI), you may need to use two consecutive line
16 | breaks to produce a visual space in a document. This is because there is already
17 | an implied line break at the end of block structures.
Netscape 6: If the DISABLED attribute is used, it grays out the
17 | content, but I noticed that it did not gray out content inside tables that are used
18 | in the BUTTON.
The CITE/DATETIME attributes are exposed in Netscape 6.1+ by
15 | invoking a context menu on the element (PC: right clicking) and choosing "properties."
16 | The value of CITE for the test element below is: "#jan25-2001" and DATETIME is
17 | "2001-01-25T18:00:00PST"
18 |
19 |
20 |
21 | filler text del text filler text
22 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/d/del-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: DEL element
6 |
7 |
8 |
9 |
10 |
Despite the caveat to not have multiple consecutive DD
15 | elements, most browsers have no problem with it.
16 |
17 |
18 | Test with first DT having 4 consecutive DD elements following, followed by a DT
19 | element with no DD elements following:
20 |
21 | filler text
22 |
11 |
12 |
13 | filler text emphasized text filler text
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/e/embedtest.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Embedded document test
6 |
7 |
8 |
9 |
10 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
11 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
12 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
13 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
14 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
15 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
16 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
17 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
18 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
19 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
20 |
21 |
22 |
23 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/e/embedtest.txt:
--------------------------------------------------------------------------------
1 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
2 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
3 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
4 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
5 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
6 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
7 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/fieldset-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FIELDSET: Browser Peculiarities: DIR=rtl rendering
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
Netscape 6 Beta 1 interprets the DIR=RTL attribute slightly
15 | different than later Netscape betas and Internet Explorer.
11 |
12 | Font SIZE relative (+2):
13 | filler text font text filler text
14 |
15 |
16 | Font SIZE absolute (6):
17 | filler text font text filler text
18 |
19 |
20 | Font POINT-SIZE (20):
21 | filler text font text filler text
22 |
23 |
24 | Font COLOR (#00ff00):
25 | filler text font text filler text
26 |
27 |
28 | Font FACE (Arial,'Times New Roman',System):
29 | filler text font text filler text
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frame-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: Browser Peculiarities: "some Internet Explorer versions where the
6 | BODY BACKGROUND attribute in the NOFRAMES section is applied to the frame borders.
7 | This behavior is an odd artifact and probably a bug."
8 |
9 |
10 |
14 |
15 |
16 |
17 |
18 | whatever
19 |
20 |
21 |
22 |
23 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frame-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: In all versions of Netscape, if no SRC attribute is initially specified,
6 | the frame area is no longer addressable as a target (even if a NAME is specified)
7 | for document links, etc. Internet Explorer and Opera handle the case of an
8 | initial blank SRC just fine.
9 |
10 |
11 |
18 |
19 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frame-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: Browser peculiarity - ROWS and COLS in same FRAMESET definition
6 |
9 |
10 |
11 |
12 |
13 | Assertions:
14 |
Authors can also choose to specify ROWS and COLS in the same
15 | FRAMESET element. If this is done, the nested FRAME references will be assigned
16 | sequentially to the ROWS and COLS layout specifications as follows: left to right,
17 | top to bottom (eg: COLS, then ROWS.)
18 |
19 |
20 |
21 |
22 | Frameset definition: rows="*,*,*" cols="*,*", Frames in order: A, B, C, D, E, F
23 |
24 |
25 |
26 |
27 | Frameset definition: cols="*,*" rows="*,*,*", Frames in order: A, B, C, D, E, F
28 |
29 |
30 |
31 |
32 | Frameset definition: cols="*,*,*" rows="*,*", Frames in order: A, B, C, D, E, F
33 |
34 |
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frame-bp4.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | A frameset consists of two identical rows, referencing the same document,
6 | that contains only a single image horizontally centered on the page.
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/framea.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME A
6 |
7 |
8 |
9 |
It is easy to abuse any of the methods of specifying frame sizes
15 | to allow dimensions that are not equal to the parent frame size (while this can be
16 | harmless, it could cause display problems.)
Internet Explorer: If the FRAMESPACING attribute is given a
15 | value of zero, it effectively sets the NORESIZE attribute of the sub-frames as well.
16 | It almost seems as if IE frames need a positive FRAMESPACING value for the user
17 | to "grab on to" or move.
18 |
19 |
20 |
21 | Frameset definition: 2 columns, frameset has no FRAMESPACING attribute
22 |
23 |
24 |
25 |
26 | Frameset definition: 2 columns, frameset has FRAMESPACING=0
27 |
28 |
29 |
30 |
31 | Frameset definition: 2 columns, frameset has FRAMESPACING=5
32 |
33 |
34 |
35 |
36 |
37 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest-recursivecols.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 | Frameset Page
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest-recursivecombo1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 | Frameset Page
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest-recursivecombo2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 | Frameset Page
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest-recursiverows.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 | Frameset Page
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Frameset document
6 |
7 |
8 |
9 |
10 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
11 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
12 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
13 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
14 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
15 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
16 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
17 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
18 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
19 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
20 |
21 |
22 |
23 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest10.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: rows="800,1200"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest11.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: rows="150,*,100"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest12.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: rows="800,*,1200"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest13.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Basic 2 column frameset
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest14.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Frameset with no FRAMESPACING attribute
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest15.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Frameset with FRAMESPACING=0
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest16.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Frameset with FRAMESPACING=5
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: Browser peculiarity - Empty SRC and frame targeting
6 |
9 |
10 |
11 |
12 |
13 | Assertions:
14 |
In all versions of Netscape, if no SRC attribute is initially
15 | specified, the frame area is no longer addressable as a target (even if a NAME is specified)
16 | for document links, etc. Internet Explorer and Opera handle the case of an initial
17 | blank SRC just fine.
11 |
12 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
13 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
14 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
15 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
16 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
17 | Filler text Filler text Filler text Filler text Filler text Filler text Filler text
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest4.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: basic document
6 |
9 |
10 |
11 |
12 |
13 | New framed document
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest5.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: rows="*,*,*" cols="*,*"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest6.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: cols="*,*" rows="*,*,*"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest8.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: two rows, with document containing only a horizontally centered image
6 |
7 |
8 |
9 |
10 |
11 |
12 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/f/frametest9.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | FRAME: rows="150,100"
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/h/head-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Assertion:
7 | Although it is not required to have this element in HTML documents
8 | (XHTML DOES require it), it is still a basic top level element in the HTML document
9 | structure and it is considered bad style to omit it. Having it present more clearly
10 | defines the boundaries between HEAD and BODY elements for a parser or person reading the HTML code.
11 |
12 |
13 | This document has no HEAD element
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/h/heading-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Hx: Browser Peculiarities: H7 support in Mosaic
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
Mosaic has always supported another heading size, H7, which
15 | has a lower importance than H6 and is rendered smaller.
16 |
17 |
18 | Normal Heading levels 1-6, with the final being the proprietary H7
19 |
20 | filler text
21 |
The DTD for HTML 4 says that heading elements are not nestable.
15 | In practice though, you'll find that authors have often historically done this,
16 | and browsers have no problems rendering this sort of thing either.
The ALIGN attribute is meaningless unless the WIDTH attribute is also specified.
15 |
16 |
17 | Successive HR elements with no WIDTH attribute. First with no align, second with align=left, third with align=center
18 | and fourth with align=right
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Successive HR elements with WIDTH=100 attribute. First with no align, second with align=left, third with align=center
30 | and fourth with align=right
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/h/html-bp1.htm:
--------------------------------------------------------------------------------
1 | Assertion:
2 | The HTML element was not a required element in the HTML specifications
3 | (but it is required under XHTML), and most popular browsers will not react oddly
4 | to its absence. Still, this is a basic top level element in the HTML/XHTML
5 | document structure and it is recommended to use it.
6 |
7 |
8 | This document has no HTML, HEAD or BODY elements
9 |
10 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/h/html-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | HTML: Browser peculiarity - Applying CSS to the HTML element in Mozilla
6 |
7 |
8 |
9 |
10 | Assertion:
11 |
Netscape 6, Beta 1 did not support CSS attached via the HTML element.
12 | This was fixed in N6B2 and above.
13 |
14 |
15 | This document has CSS applied to the HTML element (style="background-color: green; color: yellow;").
16 | If the background is green the test passes.
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/i/i-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: I element
6 |
7 |
8 |
9 |
10 |
11 | Filler text Filler text Filler text Filler text Filler text Filler text
12 | Filler text Filler text Filler text Filler text Filler text Filler text
13 | Filler text Filler text Filler text Filler text Filler text Filler text
14 | Filler text Filler text Filler text Filler text Filler text Filler text
15 | Filler text Filler text Filler text Filler text Filler text Filler text
16 | Filler text Filler text Filler text Filler text Filler text Filler text
17 |
Netscape does not seem to adjust the dimensions of an image
15 | if a LOWSRC attribute is also supplied, ie: The dimensions of the LOWSRC image
16 | are used to render the SRC image if no other HEIGHT and WIDTH properties have been set.
17 |
18 |
19 | Reference Image (zenpattern.gif), default size:
20 |
21 | filler text
22 |
23 | filler text
24 |
25 |
26 |
27 | Reference Image (right.gif), default size:
28 |
29 | filler text
30 |
31 | filler text
32 |
33 |
34 |
35 | Test case with right.gif as the LOWSRC, and zenpattern.gif as the SRC.
36 | Dimensions of the image are different:
37 |
38 | Click to see test case
39 |
40 |
41 |
42 |
43 |
44 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/i/img-helper-lowsrc1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | IMG LOWSRC test case
6 |
7 |
8 |
9 |
10 | Assertion:
11 |
Netscape does not seem to adjust the dimensions of an image
12 | if a LOWSRC attribute is also supplied, ie: The dimensions of the LOWSRC image
13 | are used to render the SRC image if no other HEIGHT and WIDTH properties have been set.
Using a READONLY attribute in IE4 and IE5 on this element still
15 | allows a user to invoke the file...open dialog (from the "Browse..." button), although
16 | the text field is not directly editable. In IE5.5 plus, both the text field AND the
17 | file...open dialog are not usable.
The CITE/DATETIME attributes are exposed in Netscape 6.1+ by
15 | invoking a context menu on the element (PC: right clicking) and choosing "properties."
16 | The value of CITE for the test element below is: "#jan25-2001" and DATETIME is
17 | "2001-01-25T18:00:00PST"
18 |
19 |
20 |
21 | filler text ins text filler text
22 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/i/ins-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: INS element
6 |
7 |
8 |
9 |
10 |
Opera 4.x: Assigning event handlers to this element will only
15 | trigger on the isindex surrounding area, NOT the ISINDEX text input field -
16 | this seems like incorrect behavior to me.
In Netscape 1.0-4.x, when data is sent via POST, it is sent
15 | as a name/value pair (exactly like it is done with normal forms.)
16 | The data is sent as: The ISINDEX value is what is entered by the user, and the
17 | variable name it is assigned to is "isindex." If the GET method is used, the
18 | value is the only data that is sent.
19 |
20 |
21 | Clicking on the link will generate the ISINDEX test case. Click on the link,
22 | type some text in the isindex box and hit the enter key.
23 |
24 | Generate
25 | ISINDEX with METHOD=post
26 |
27 |
28 |
29 |
30 |
31 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/i/isindex-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | ISINDEX: Browser Peculiarities: Default METHOD of sending data
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
The default method for sending ISINDEX data is via the GET method
15 | (the data is appended to a URL as an argument.)
16 |
17 |
18 | Clicking on the link will generate the ISINDEX test case. Click on the link,
19 | type some text in the isindex box and hit the enter key.
20 |
21 | Generate
22 | plain ISINDEX case
23 |
24 |
25 |
26 |
27 |
28 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/k/kbd-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: KBD element
6 |
7 |
8 |
9 |
10 |
Code example: KBD element
11 |
12 |
13 | filler text text entered from the keyboard filler text
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/l/legend-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | LEGEND: Browser Peculiarities: Rendering in early Mozilla builds
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
In Netscape 6 Beta 1, a black bordered box was automatically
15 | placed around the LEGEND content (equivalent of using <legend STYLE="border: 2px solid black">).
16 | In later versions, no border box is applied.
17 |
18 | If the behavior is as described, both cases should look alike.
19 |
Use of the ACCESSKEY attribute for this element in IE 4.0 puts
15 | focus on the first form field within the parent FIELDSET.
16 |
17 | To activate ACCESSKEY:
18 |
19 |
IE/Moz: ALT + accesskey character
20 |
Opera: SHIFT-ESC + accesskey character
21 |
22 |
23 |
24 |
25 | LEGEND element with accesskey="r". The third field has an accesskey "s" by comparison:
26 |
27 | filler text
28 |
36 | filler text
37 |
38 |
39 |
40 |
41 |
42 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/l/li-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | LI: Browser Peculiarities: Use of a list structure without LI sub-elements
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
Internet Explorer, Mosaic and Netscape all produce the
15 | indenting behavior for the case of having no LI elements in a list context.
16 | No list markers are generated.
17 |
18 |
19 | Indentation of UL element content with no LI sub-element:
20 |
21 | filler text
22 |
23 | UL list content UL list content UL list content UL list content UL list content UL list content
24 |
25 | filler text
26 |
27 |
28 |
29 |
30 | Indentation of OL element content with no LI sub-element:
31 |
32 | filler text
33 |
34 | OL list content OL list content OL list content OL list content OL list content OL list content
35 |
36 | filler text
37 |
38 |
39 |
40 |
41 |
42 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/l/li-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | LI: Browser Peculiarities: Treatment of "0" and negative values for VALUE attribute
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
VALUE attribute behavior for "0" and negative values:
15 |
16 |
IE: (all) Value ignored
17 |
Netscape/Mozilla: (all) Both value types treated as "1" (default)
18 |
Opera 2.1-6.x: Value Ignored
19 |
Opera 7.x+: "0" honored; negative values cause no marker to be rendered on that LI or any thereafter.
20 |
21 |
22 |
23 | OL list with 2nd LI VALUE="5":
24 |
25 | filler text
LI item 1
LI item 2
LI item 3
filler text
26 |
27 |
28 |
29 | OL list with 2nd LI VALUE="0":
30 |
31 | filler text
LI item 1
LI item 2
LI item 3
filler text
32 |
33 |
34 |
35 | OL list with 2nd LI VALUE="-5":
36 |
37 | filler text
IE 3.0 only allowed for a single LINK or STYLE block.
17 | Only the last one specified in the document is used.
18 | IE 4.0 and above, Netscape and Opera merge/cascade multiple STYLE elements.
19 |
20 |
21 | Simple DIV element with id="test1". First external CSS specifies "color: green" for this element.
22 |
23 | filler text
24 |
This is a div
25 | filler text
26 |
27 |
28 |
29 | Simple DIV element with id="test2". Second external CSS specifies "color: green" for this element.
30 |
31 | filler text
32 |
This is a div
33 | filler text
34 |
35 |
36 |
37 |
38 |
39 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/l/link-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | LINK: Browser Peculiarities: LINK elements with ID ignored in Netscape 4.x
6 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Assertion:
16 |
Netscape 4.x ignores a LINKed stylesheet if the LINK element has an ID attribute.
17 |
18 |
19 | Simple DIV element with id="test1". First external CSS specifies
20 | "background-color: green; text-transform: uppercase;" for this element.
21 | LINK element does not have ID attribute
22 |
23 | filler text
24 |
This is a div
25 | filler text
26 |
27 |
28 |
29 | Simple DIV element with id="test2". Second external CSS specifies
30 | "background-color: green; text-transform: uppercase;" for this element.
31 | LINK element has an ID attribute
32 |
33 | filler text
34 |
If no WIDTH attribute is set for a MARQUEE element, it behaves like a
15 | block-level element (linebreak before and after) and occupies 100% of the containing
16 | element/window width. If a width is set, it behaves like an in-line element.
Nested MARQUEE elements do not behave well in Internet Explorer.
15 | Don't try it.
16 |
17 |
18 | Basic nested MARQUEE elements, no widths on each. Green background on outer, yellow on inner:
19 |
20 | filler text
21 |
22 | filler text
23 |
24 |
25 |
26 | Basic nested MARQUEE elements, width=500 on each. Green background on outer, yellow on inner:
27 |
28 | filler text
29 | outerMarquee
30 | innerMarquee outerMarquee
31 | filler text
32 |
33 |
34 |
35 |
36 |
37 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/m/marquee-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | MARQUEE: Browser Peculiarities: Block structures in Marquee
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
The use of block structures in MARQUEEs (such as BLOCKQUOTE)
15 | will be ignored in IE versions 3.0x and below, while in IE 4.0 and above it makes
16 | the marquee appear as a multi-line field.
Scenario: MARQUEE is the only content of a table cell and
15 | WIDTH attribute is not set for EITHER the table cell or MARQUEE element:
16 | Internet Explorer 4.0 and above - cell width defaults to 1 pixel.
17 | Internet Explorer 2.0/3.0 - cell width defaults to the width of the MARQUEE content.
18 |
19 |
20 | Basic MARQUEE element ("Marquee text") in cell 1, no width.:
21 |
22 | filler text
23 |
24 |
Marquee text
cell 2
25 |
26 | filler text
27 |
28 |
29 |
30 | Basic MARQUEE element ("Marquee text") in cell 1, width=200.:
31 |
32 | filler text
33 |
Netscape 7.0+: For the BEHAVIOR attribute, the ALTERNATE value
15 | is rendered differently than IE - In IE, the marquee starts at one side of the
16 | marquee box, already onscreen. It then proceeds to the opposite side of the marquee
17 | box, until its leading content edge reaches the marquee box edge, and then returns
18 | back the way it came. In Mozilla, the marquee content starts offscreen, comes
19 | onscreen at one side, travels to the opposite side, then goes offscreen before travelling
20 | back the way it came.
Netscape 6 Beta 1 had a bug with MENU lists: Unless LI elements
15 | in the menu list were explicitly closed (they should be optional), the menu
16 | indentation level was maintained for the rest of the document. This behavior was fixed in 6.0 Beta 2.
17 |
18 |
19 | Basic MENU list with closing LI elements:
20 |
21 | filler text
22 |
27 | filler text
28 |
29 |
30 |
31 | Basic MENU list with no closing LI elements:
32 |
33 | filler text
34 |
39 | filler text
40 |
41 |
42 |
43 |
44 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/n/nobr-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: NOBR element
6 |
7 |
8 |
9 |
10 |
Code example: NOBR element
11 |
12 |
13 | filler text This is a run of nobreak text to be used as an example This is a run of nobreak text to be used as an example
14 | This is a run of nobreak text to be used as an example This is a run of nobreak text to be used as an example
15 | This is a run of nobreak text to be used as an example This is a run of nobreak text to be used as an example filler text
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/o/ol-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | OL: Browser Peculiarities: Treatment of "0" and negative values for START attribute
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
START attribute behavior for "0" and negative values:
15 |
16 |
IE: (all) Both value types honored
17 |
Netscape/Mozilla: (all) Ignored
18 |
Opera 2.1-6.x: Ignored
19 |
Opera 7.x+: "0" honored; negative values cause list markers to go away
20 |
21 |
22 |
23 | OL list with START="5":
24 |
25 | filler text
LI item 1
LI item 2
LI item 3
filler text
26 |
27 |
28 |
29 | OL list with START="0":
30 |
31 | filler text
LI item 1
LI item 2
LI item 3
filler text
32 |
33 |
34 |
35 | OL list with START="-5":
36 |
37 | filler text
All Opera versions, IE4+, and Netscape up to version 6.0 support the original
17 | PLAINTEXT specification which did not accept a closing tag.
18 |
Internet Explorer up to version 3, Netscape 6.1+ and all Mosaic versions
19 | provide for a closing tag. A closing tag would allow placement in regions
20 | other than the end of a HTML document.
21 |
22 |
23 |
24 |
25 | Plain PLAINTEXT element, with nested B element (It should be fairly evident if parsing stops beyond the end tag):
26 |
27 | filler text
28 | plaintext NESTED BOLD ELEMENT, character entity: & plaintext
29 | filler text
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/q/q-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Q: Browser peculiarity - rendering effects in Mozilla
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
The CITE attribute is exposed in Netscape 6.1+ by invoking a
15 | context menu on the element (PC: right clicking) and choosing "properties."
16 | The value of CITE for the test element below is: "http://www.example.com/qcitation.htm"
IE 4+ supports this element, but only via its recognition.
17 | Common attributes will be applied to content, but nothing is done with the CITE
18 | attribute by the browser unless scripting is used to take action on its value.
19 |
20 |
21 | Test 1:
22 | filler text
23 | Plain Q element, no attributes
24 | filler text
25 |
26 |
27 | Test 2:
28 | filler text
29 | Q
30 | element, with class="test" (Gray color), id="test1" (green background),
31 | style ("word-spacing: 20px"), and title ("this is a title" on hover) attributes
32 | filler text
33 |
34 |
35 |
36 |
37 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/r/rt-bp2.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | RT: Browser Peculiarities: Placement of RT within RUBY element
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
IE: If RT content exists before the RB element, the RT content
15 | is rendered small, but inline before the RB content.
IE 5+: While Block elements can exist within a Ruby element,
15 | some interesting behaviors are apparent. Images render fine also, but not form widgets.
IE 5+: While Block elements can exist within a Ruby element,
15 | some interesting behaviors are apparent. Images render fine also, but not form widgets.
While the author CAN legally omit using the HTML comment to
16 | encapsulate the Style information, most older browsers will display the style
17 | information in these cases as document content. Authors are strongly encouraged
18 | to use the HTML Comment for the Style element to prevent this from happening.
19 |
20 |
21 | Simple DIV element with class="test".
22 | Style element is NOT nested in a comment, and contains: ".test { background-color: green; color: yellow }":
23 |
24 | filler text
25 |
While the author CAN legally omit using the HTML comment to
18 | encapsulate the Style information, most older browsers will display the style
19 | information in these cases as document content. Authors are strongly encouraged
20 | to use the HTML Comment for the Style element to prevent this from happening.
21 |
22 |
23 | Simple DIV element with class="test".
24 | Style element IS nested in a comment, and contains: ".test { background-color: green; color: yellow }":
25 |
26 | filler text
27 |
IE 3.0 only allowed for a single LINK or STYLE block.
19 | Only the last one specified in the document is used.
20 | IE 4.0 and above, Netscape and Opera merge/cascade multiple STYLE elements.
21 |
22 |
23 | Simple DIV element with class="test".
24 | First STYLE block contains ".test { color: green }". Second STYLE block contains
25 | ".test { background-color: yellow }".
26 | Both should be cascaded together on the one
27 | test DIV to produce a div with background-color=yellow and color=green.
28 |
29 | filler text
30 |
Some browsers may react badly to titles of null length or greater than 256 characters.
15 |
16 |
17 | The title element of this document is empty
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/t/title-bp3.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
8 |
9 |
10 |
11 |
12 | Assertion:
13 |
Although it is a required element in the specification, most
14 | popular browsers will not react oddly to its absence.
15 |
16 |
17 | This document has no title element.
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/t/tt-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: TT element
6 |
7 |
8 |
9 |
10 |
Code example: TT element
11 |
12 |
13 | filler text Fixed-width text filler text
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/u/u-bp1.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | U: Tips/Tricks: Underline element possible confusion with hyperlink appearance
6 |
9 |
10 |
11 |
12 |
13 | Assertion:
14 |
Use of the U element can possibly generate confusion with
15 | hyperlinks which generally carry a characteristic underlining effect.
16 |
17 |
18 | Using U element alone:
19 |
20 | filler text Link to Yahoo.com filler text
21 |
22 |
23 |
24 | Using U element with FONT COLOR element (with typical browser unvisited link color):
25 |
26 | filler text Link to Yahoo.com filler text
27 |
28 |
29 |
30 | Using A HREF element linking to yahoo.com :
31 |
32 | filler text Link to Yahoo.com filler text
33 |
34 |
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/u/u-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: U element
6 |
7 |
8 |
9 |
10 |
Code example: U element
11 |
12 |
13 | filler text Underlined text filler text
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/docs/misc/html-element-index/testing/html/tags/v/var-example.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Code example: VAR element
6 |
7 |
8 |
9 |
10 |