chore: lock playwright version [swc-829]#5414
Conversation
|
Branch previewReview the following VRT differencesWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
If the changes are expected, update the |
05d38b3 to
d1f97c0
Compare
Tachometer resultsCurrently, no packages are changed by this PR... |
16ac9a1 to
f28b5e9
Compare
| import { sendKeys } from '@web/test-runner-commands'; | ||
|
|
||
| describe('NumberField - inputs', () => { | ||
| before(async () => { |
There was a problem hiding this comment.
CanIUse indicates that the international number field has been available in our supported evergreen - 2 so we can remove the polyfills now
| private host: ReactiveElement; | ||
| language = document.documentElement.lang || navigator.language; | ||
| get language(): string { | ||
| return document.documentElement.lang || navigator.language; |
There was a problem hiding this comment.
This is fetching the root-level language but shouldn't we also be honoring if the language attribute is set on a container too?
There was a problem hiding this comment.
this change is what is causing a majority of the number field failing tests, I would like to revert it since its out of scope for this specifically and capture this idea somehow for when we refactor number field.
There was a problem hiding this comment.
Those tests were failing before as well - I added this change to resolve the first round of issues I saw. You can see the details outlined in the Jira ticket.
The first error I identified was on NumberField which threw an error that locale was invalid on every instance. I fixed this according to similar debugging advice I found online by converting any manually provided locales with underscores to dashes.
There was a problem hiding this comment.
thats odd, when i reverted it the tests passed. I'm going to do a fresh clone again to make sure it wasn't something weird on my local. thank you for this context and apologies I missed that from the ticket.
e41803d to
cf33dd2
Compare
1d4606b to
95f97c1
Compare
95f97c1 to
74fbb10
Compare
74fbb10 to
71b894f
Compare
| ] | ||
| } | ||
| }, | ||
| "extends": [ |
There was a problem hiding this comment.
🚫 [eslint] <no-dupe-keys> reported by reviewdog 🐶
Duplicate key 'extends'.
| "plugin:lit-a11y/recommended", | ||
| "plugin:require-extensions/recommended" | ||
| ], | ||
| "overrides": [ |
There was a problem hiding this comment.
🚫 [eslint] <no-dupe-keys> reported by reviewdog 🐶
Duplicate key 'overrides'.
| @@ -19,7 +19,7 @@ import prettier from 'prettier'; | |||
| import Case from 'case'; | |||
There was a problem hiding this comment.
🚫 [eslint] <import/no-extraneous-dependencies> reported by reviewdog 🐶
'case' should be listed in the project's dependencies, not devDependencies.
71b894f to
4ce24bf
Compare
4ce24bf to
a5f2232
Compare
There was a problem hiding this comment.
🚫 [eslint] <notice/notice> reported by reviewdog 🐶
Missing notice header
There was a problem hiding this comment.
🚫 [eslint] <notice/notice> reported by reviewdog 🐶
Missing notice header
There was a problem hiding this comment.
🚫 [eslint] <notice/notice> reported by reviewdog 🐶
Missing notice header
Description
Related issue(s)
Motivation and context
How has this been tested?
Test case 1
Test case 2
Did it pass in Desktop?
Did it pass in Mobile?
Did it pass in iPad?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main.