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