ladybird/.prettierignore

Tests/LibJS/AST/
Tests/LibJS/Bytecode/
Tests/LibJS/Runtime/invalid-lhs-in-assignment.js
Tests/LibJS/Runtime/unicode-identifier-escape.js
Tests/LibJS/Runtime/modules/failing.mjs

Tests/LibWeb/Crash/wpt-import/
Tests/LibWeb/Ref/input/wpt-import
Tests/LibWeb/Text/input/wpt-import
Tests: Exclude JS AST and bytecode tests from prettier checks 2026-02-18 09:52:14 -03:00			`Tests/LibJS/AST/`
			`Tests/LibJS/Bytecode/`
LibJS: Move tests to `/Tests/LibJS` 2026-01-22 07:58:59 -03:00			`Tests/LibJS/Runtime/invalid-lhs-in-assignment.js`
			`Tests/LibJS/Runtime/unicode-identifier-escape.js`
			`Tests/LibJS/Runtime/modules/failing.mjs`
LibJS: Add using declaration support, RAII like operation in js In this patch only top level and not the more complicated for loop using statements are supported. Also, as noted in the latest meeting of tc39 async parts of the spec are not stage 3 thus not included. 2022-12-20 18:09:57 -03:00
Meta: Don't lint imported WPT crash tests with prettier 2025-06-21 11:53:21 -03:00			`Tests/LibWeb/Crash/wpt-import/`
Meta: Add imported WPT ref tests to .prettierignore 2024-11-06 13:51:53 -03:00			`Tests/LibWeb/Ref/input/wpt-import`
LibWeb: Implement HTMLElement.innerText closer to spec And here's the wild part: instead of cloning WPT tests, import the relevant WPT tests that this fixes into our own test suite. This works by adding a small Ladybird-specific callback in resources/testharnessreport.js (which is what that file is meant for!) Note that these run as text tests, and so they must signal the runner when they are done. Tests using the "usual" WPT harness should just work, but tests that do something more freestyle will need manual signaling if they are to be imported. I've also increased the test timeout here from 30 to 60 seconds, to accommodate the larger WPT-style tests. 2024-10-24 14:21:55 -03:00			`Tests/LibWeb/Text/input/wpt-import`