-
Notifications
You must be signed in to change notification settings - Fork 229
docs(progress-bar): documentation updates #5553
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: a4f9388 The changes in this PR will be included in the next version bump. This PR includes changesets to release 84 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Tachometer resultsChromeprogress-bar permalinkbasic-test
Firefoxprogress-bar permalinkbasic-test
|
b03e21f
to
d3066d2
Compare
80b25dc
to
67bd793
Compare
6aab6d6
to
cf28e9b
Compare
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.
We already have a system in place to show deprecation notice like below. In package.json you can add deprecationNotice: " < your notice here> ".
I have pushed this commit for you to verify.

Excellent, thank you! Do we need to address this? 03c57d2#r2161351158 Are all of the CSS changes expected in the diff as well? |
4a7e837
to
02018da
Compare
Mostly all are linting whitespace. Only change is
@cdransf Yes we need to add the changes from this commit to maintain parity of UI on the deprecation notice. Let's not create another format here! |
03c57d2
to
b17b435
Compare
Got it! I rebased main back in to resolve the conflicts when you have the time to take another look. ✨ |
Can you add back inline-alert.css changes too. I think it is missing. |
Just restored those. ✨ |
📚 Branch Preview🔍 Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
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.
A few changes to some headings and wording but overall a welcome improvement to our docs.
ef5cb05
to
cbef3bc
Compare
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.
Looks good to me! Please re-run the pipeline to clear out the VRT noise. If everything passes, this should be good to merge.
cbef3bc
to
d5ed278
Compare
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.
Lost gold treasure map (LGTM)
d5ed278
to
b22d679
Compare
e9d1468
to
09e1e20
Compare
Co-authored-by: Rajdeep Chandra <rajrock38@gmail.com>
09e1e20
to
a4f9388
Compare
Description
Improving the accessibility documentation of components.
Related issue(s)
SWC-398
Author's checklist
Reviewer's checklist
patch
,minor
, ormajor
featuresDevice review