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
Fix Callout example targets and simplify styling #15941
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 28ba25e:
|
38ca10f
to
413ed98
Compare
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: ca4ec134424fbd53ecc726b965d6dbff1fc12bf6 (build) |
|
Handy links: |


Pull request checklist
$ yarn changeDescription of changes
While investigating Callout screener issues, we noticed that the examples on the doc site were not targeting the correct element due to an overly general selector. Fix that issue and simplify some of the styling of the example callout contents.
I also started looking at the Callout docs while trying to understand some things about the examples and fixed a couple minor issues there, as well as adding an explicit interface for
onRestoreFocus's parameters since the signature is reused several places.One other issue I noticed and fixed (while seeing if I could use ThemeProvider in an example) was a missing bracket in a code example in the
react-theme-providerreadme.