Skip to content

Conversation

@dbkr
Copy link
Member

@dbkr dbkr commented Sep 5, 2025

I'll leave the comment to do the explaining on the change itself.

This also adds axe testing to every compound web component... except the ones that have been excluded because they have errors. As per other comment, a lot of these are just that the stories don't put the components in their proper context. The tag excludes them until we have time to fix them all.

I've added a test for ReleaseAnnoucement when put on a div to assert that this axe failure goes away.

I'll leave the comment to do the explaining
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Sep 5, 2025

Deploying compound-web with  Cloudflare Pages  Cloudflare Pages

Latest commit: 19ad3bf
Status: ✅  Deploy successful!
Preview URL: https://563b31c6.compound-web.pages.dev
Branch Preview URL: https://dbkr-release-announcement-re.compound-web.pages.dev

View logs

dbkr added 2 commits September 5, 2025 16:12
With an axe-exclude tags for stories that don't pass (which is a
slightly frightening number...)
@dbkr dbkr marked this pull request as ready for review September 5, 2025 15:21
@dbkr dbkr requested a review from a team as a code owner September 5, 2025 15:21
@dbkr dbkr requested review from robintown and t3chguy and removed request for a team September 5, 2025 15:21
Copy link
Member

Choose a reason for hiding this comment

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

This looks unexpected

Copy link
Member Author

Choose a reason for hiding this comment

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

The reasoning here is that rather than having the anchor element control the visibility of the popup, we make it something else, that way the anchor element doesn't have to be a button, which I needed so I can add a test for when it's a div. I included the extra button so you could open and close the popup, although only because the functionality was there before: we could just have a prop to control whether it's open?

Copy link
Member

Choose a reason for hiding this comment

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

Can we hide it from the screenshot via mask or css? We shouldn't be asserting browser styles for unstyled buttons in our tests

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure - hidden in screenshots now.

Copy link
Member

Choose a reason for hiding this comment

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

Ditto

Copy link
Member

Choose a reason for hiding this comment

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

Ditto

Copy link
Member

Choose a reason for hiding this comment

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

Ditto

Copy link
Member

Choose a reason for hiding this comment

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

I wouldn't expect an unstyled Close button here

@dbkr dbkr requested a review from t3chguy September 5, 2025 16:37
Copy link
Member

@t3chguy t3chguy left a comment

Choose a reason for hiding this comment

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

It looks like my latest comment was not acknowledged or responded to.

@dbkr
Copy link
Member Author

dbkr commented Sep 8, 2025

Sorry, not sure what happened there: maybe github not updating, also possibly Friday afternoon brain syndrome.

@dbkr dbkr requested a review from t3chguy September 8, 2025 15:48
@dbkr dbkr merged commit 773acbd into main Sep 8, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants