Skip to content

chore(Progress): updated placement and verbiage for status examples - #7777

Merged
thatblindgeye merged 3 commits into
patternfly:mainfrom
thatblindgeye:iss7288_progressHelpText
Sep 4, 2025
Merged

thatblindgeye merged 3 commits into
patternfly:mainfrom
thatblindgeye:iss7288_progressHelpText

Conversation

@thatblindgeye

Copy link
Copy Markdown
Contributor

Closes #7288

@patternfly-build

patternfly-build commented Sep 2, 2025 •

Copy link
Copy Markdown
Collaborator

@kaylachumley kaylachumley left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good! didn't see anything too crazy - not sure we want erin to review the copy? up to you!

@edonehoo edonehoo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some small nits (mostly making each point a sentence)!

Comment on lines +203 to +207
When conveying status, you should ensure:
- there is visible helper text that explains the status,
- the helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text#basic), and
- the helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When conveying status, you should ensure:
- there is visible helper text that explains the status,
- the helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text#basic), and
- the helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).
When conveying status, you should ensure the following:
- There is visible helper text that explains the status.
- The helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text#basic).
- The helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).


When conveying status, you should ensure:
- There is visible helper text that explains the status.
- The helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text/html#basic).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive! Anticipating the change from #static to #basic. But generally if I link to another component in the docs, I link to the default/react tab. That link won't work if you're just looking at core docs (like in this PR), but it works on org. Curious what you and @edonehoo think.

Suggested change
- The helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text/html#basic).
- The helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text#basic).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case this should be fine - I think my one caveat would be do we want to link to a React example if someone is browsing the HTML docs? The link not working correctly on staging/local builds is a fair point, but I guess that depends if we should worry as much about that or the final experience on org?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree! didn't catch that, but I also link to the react tab unless we're referencing a core-specific example

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops my page didn't refresh with Eric's comment before my reply. I didn't realize that the progress doc is an html page since I'm usually in react land, but hm that's a fair point. If it's safe to assume that consumers generally stick with html/css implementation consistently (rather than mingling html & react implementations for something like this) then maybe it is better to link to the html helper text here?

@mcoker mcoker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple small comments

When conveying status, you should ensure:
- There is visible helper text that explains the status.
- The helper text includes the status icon, as seen in our [basic helper text example](/components/helper-text/html#basic).
- The helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you a quotation mark

Suggested change
- The helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).
- The helper text is linked to the `.pf-v6-c-progress__bar[role="progressbar"]` element via an `aria-describedby` attribute, as seen in the [progress helper text example](#helper-text).

@mcoker mcoker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@thatblindgeye
thatblindgeye merged commit a5be52c into patternfly:main Sep 4, 2025
4 checks passed
@patternfly-build

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 6.3.0-prerelease.56 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Progress - examples with status should be reordered and verbiage applied

5 participants