257853 2023-06-08 08:59:41 -0700 [WPT export friction] Run WPT lint as part of WebKit development via check-webkit-style 2026-05-04 10:56:38 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 1 annevk gsnedders gsnedders jbedard simon.fraser webkit-bug-importer youennf oldest_to_newest 1960559 0 annevk 2023-06-08 08:59:41 -0700 We should run WPT lint as part of our own listing infrastructure to ensure exports to WPT don't run into issues that would have been easily addressed ahead-of-time. 1961819 1 webkit-bug-importer 2023-06-15 09:00:22 -0700 <rdar://problem/110843279> 1963047 2 jbedard 2023-06-22 08:03:53 -0700 Naively, it seems like check-webkit-style would be the right place for this. 2036483 3 gsnedders 2024-05-20 13:15:45 -0700 We currently are meant to blanket ignore everything in LayoutTests (but see Bug 274407), so this also implies changing the current ignore rule to run a specific lint on a bunch of LayoutTests. 2054743 4 gsnedders 2024-08-22 10:53:13 -0700 *** Bug 278503 has been marked as a duplicate of this bug. *** 2054771 5 simon.fraser 2024-08-22 12:59:05 -0700 The use-experience here is that if the WPT linter finds an issue when you are exporting a WPT, you have no recourse to fix it and continue the export. 2058256 6 simon.fraser 2024-09-06 12:13:41 -0700 To run the WPT linter manually, you can pass it full paths to new files: ./LayoutTests/imported/w3c/web-platform-tests/wpt lint <list of absolute paths> 2201693 7 simon.fraser 2026-04-17 16:27:06 -0700 Pull request: https://github.com/WebKit/WebKit/pull/63010 2206698 8 gsnedders 2026-05-01 15:23:08 -0700 Pull request: https://github.com/WebKit/WebKit/pull/64073 2207259 9 ews-feeder 2026-05-04 10:56:36 -0700 Committed 312533@main (1c2ce5ed31e5): <https://commits.webkit.org/312533@main> Reviewed commits have been landed. Closing PR #64073 and removing active labels.