testaro 77.0.4 → 77.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/procs/catalog.js +12 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "testaro",
3
- "version": "77.0.4",
3
+ "version": "77.1.0",
4
4
  "description": "Run 1300 web accessibility tests from 10 tools and get a standardized report",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/procs/catalog.js CHANGED
@@ -44,6 +44,18 @@ exports.getCatalog = async report => {
44
44
  });
45
45
  // If the launch and navigation succeeded:
46
46
  if (page) {
47
+ // Expand closed details elements before the page image and the box measurements, so
48
+ // both see the same fully disclosed state. Chromium lays out the content of a closed
49
+ // details element (content-visibility: hidden) without painting it and without
50
+ // shifting the content after it, so getBoundingClientRect returns coordinates that
51
+ // overlap unrelated visible elements, making box IDs disagree with the page image.
52
+ await page.evaluate(() => {
53
+ document.querySelectorAll('details:not([open])').forEach(details => {
54
+ details.setAttribute('open', '');
55
+ });
56
+ }).catch(error => {
57
+ console.log(`ERROR: Expanding details elements failed (${error.message})`);
58
+ });
47
59
  // If a page image is required:
48
60
  if ([0, 2, 4, 6].includes(report.imageColor)) {
49
61
  // Create one and add it to the report.