-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PeoplePicker - Korean Characters issue in IE11 #10432
Conversation
@yumikohey @Adjective-Object not sure why I can't add reviewers, please take a look |
Asset size changes
Over Tolerance (1024 B) Over Baseline Below Baseline New Removed 1 kB = 1000 B Baseline commit: 3682e4b101a264192d36d2a7ceb59ad877661e6f (build) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joschect please review
packages/office-ui-fabric-react/src/components/Autofill/Autofill.tsx
Outdated
Show resolved
Hide resolved
@KevinTCoughlin yep, I'm taking a look at it now. It's taken me a sec to get my windows machine setup to test. |
@amyngu awesome job! Thanks for doing that. |
@amyngu it looks like snapshots need to be updated for CI to pass. |
Hello @KevinTCoughlin! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
…ll.tsx Co-Authored-By: Kevin Coughlin <706967+KevinTCoughlin@users.noreply.github.com>
Looks like another case of But no snapshot files churn when running the command local to the ~\Work\office-ui-fabric-react\packages\experiments [keco/autoFillKoreanIE11]> yarn update-snapshots yarn run v1.17.3
$ just-scripts jest -u
[2:56:05 PM] ■ started 'jest'
[2:56:05 PM] ■ Running Jest
[2:56:05 PM] ■ C:\Program Files\nodejs\node.exe "C:\Users\keco.REDMOND\Work\office-ui-fabric-react\node_modules\jest\bin\jest.js" --config "C:\Users\keco.REDMOND\Work\office-ui-fabric-react\packages\experiments\jest.config.js" --passWithNoTests --colors --forceExit --updateSnapshot
PASS src/components/Slider/Slider.test.tsx (12.599s)
PASS src/components/Sidebar/Sidebar.test.tsx (14.988s)
PASS src/components/PersonaCoin/PersonaCoin.test.tsx (15.172s)
PASS src/components/Button/Button.test.tsx (15.322s)
PASS src/components/Toggle/Toggle.state.test.tsx (15.66s)
PASS src/components/Button/ButtonVariants/ButtonVariants.test.tsx (15.986s)
PASS src/components/Button/SplitButton/SplitButton.test.tsx (16.307s)
PASS src/components/Button/MenuButton/MenuButton.test.tsx
PASS src/components/Chiclet/Chiclet.test.tsx
PASS src/components/Toggle/Toggle.view.test.tsx
PASS src/components/Persona/Vertical/VerticalPersona.test.tsx
PASS src/components/SelectedItemsList/SelectedItemsList.test.tsx
PASS src/components/Pagination/Pagination.test.tsx
Force exiting Jest
Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?
[2:56:28 PM] ■ finished 'jest' in 23.59s
Done in 24.93s. |
Figured out what's required to resolve CI. @amyngu you'll need to do a full build via |
Component Perf AnalysisNo significant results to display. All results
|
🎉 Handy links: |
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
Focus areas to test
Autofill & People Pickers
Microsoft Reviewers: Open in CodeFlow