From 49be86d7885ddf9f3532cc3b48c4b5c0cd931d73 Mon Sep 17 00:00:00 2001 From: web-padawan Date: Thu, 9 Jan 2025 16:05:12 +0200 Subject: [PATCH] chore: document testing Tab with Playwright WebKit on Mac OS --- DEVELOPMENT.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index c32323316f..8b3881dccb 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -16,6 +16,7 @@ of steps to perform when creating a new major or minor version branch of the mon - [Generating icons](#generating-icons) - [Using a local clone of the repo](#using-a-local-clone-of-the-repo) - [Fixing npm dist-tag](#fixing-npm-dist-tag) + - [Testing Tab on WebKit](#testing-tab-on-webkit) ## Getting started @@ -291,7 +292,7 @@ Re-generate SVG icon sets and icon fonts from individual SVG files for the packa yarn icons ``` -## Using a local clone of the repo +### Using a local clone of the repo When using a Vaadin app, you can modify the frontend build tool config to resolve the web components modules from your local clone, instead of the versions downloaded from npm registry. @@ -369,7 +370,7 @@ This will symlink the individual component packages into the `node_modules` fold After that you can start / restart your application and it should use the source code from the monorepo. -## Fixing npm dist-tag +### Fixing npm dist-tag When maintaining two stable majors (e.g. 22.0.x and 23.0.x), it is important to maintain `latest` npm tag. For example, we release 22.0.7 after 23.0.1 but we still want to keep `latest` pointing to 23.0.1. @@ -379,3 +380,7 @@ Use the following script on `main` branch to run `npm dist-tag` for all packages ```sh ./scripts/fixDistTag.sh ``` + +### Testing Tab on WebKit + +When running tests in Playwright WebKit on Mac OS, some tests using `sendKeys({ press: 'Tab' })` might fail for components using native `