Fri, 16 Jan 2015 18:13:44 +0100
Integrate suggestion from review to improve consistency with existing code.
1 This directory contains various XUL document (mozilla/content/xul/document) testcases for reftest.
3 test001: Checks that stylesheets referenced from an overlay via an
4 xml-stylesheet PI are applied to the master document appropriately.
6 test002: Same as #1, but there's additional overlay between the master doc and
7 the overlay with the stylesheet.
9 test003: Checks that dynamically removing the stylesheet PI from an inline
10 script has expected effect.
12 test004: Same as test003, but removing the stylesheet PI happens from a "load"
13 event handler.
15 test005: Same as test003, but removing the stylesheet PI happens from a top-level
16 script in an external JS file.
18 test006: Simple <?xml-stylesheet ?> instruction in the prolog has an effect and exists
19 in the DOM.
21 test007: Same as #006 for xul-overlay PI.
23 test008: Handle stylesheet PIs pointing to nonexistent resources gracefully.
25 test009: Same as #008 for xul-overlay PIs
27 test010: PIs in the master document, outside the prolog, don't have any effect but get
28 added to the DOM.
30 test011: (bug 363406) Relative URIs in overlay's <?xml-stylesheet ?> PI are
31 resolved against overlay's URI, not the document URI.
33 test012: Tests that sheets references from <?xml-stylesheet ?> PIs are added to the
34 document in the same order as the PIs themselves are in - the simple case.
36 test013: Tests the same thing as #012, but for the case when the first sheet contains
37 an @import statement, which makes it -finish- loading earlier than the
38 second sheet.
40 test014: (bug 363406) Relative URIs in overlay's <?xul-overlay ?> PI are resolved
41 against overlay's URI, not the document URI.
43 test015: Relative URIs in overlay's <xul:script> are resolved against overlay's
44 URI, not the document URI.
46 test016: Non-XUL elements work in overlays.
48 test017: (bug 359959) <?xul-overlay ?> used as a direct child of <overlay>
49 should be inserted into the DOM, but not cause the overlay to be
50 applied.
52 test018: <?xul-overlay ?> used deep inside another overlay (i.e. as a child of
53 a 'hookup' node) should be inserted into the DOM, but not cause the
54 overlay to be applied.
56 test019: Same as #017 for <?xml-stylesheet ?>
58 test020: Same as #018 for <?xml-stylesheet ?>
60 test021: (bug 363419) Non-XUL elements directly underneath <overlay> should
61 be merged correctly into the base document.
63 test022: (bug 369828) <html:style> works in XUL documents