Skip to content
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

Feature/cms 1266 error summary in slideouts #14436

Merged
merged 20 commits into from
Feb 26, 2024

Conversation

i-just
Copy link
Contributor

@i-just i-just commented Feb 21, 2024

Description

Adds the error summary to slideouts.

Unlike the full-page approach, where there’s one error summary area that shows above the tabs, in slideouts, we have an error summary per tab, and each of those only shows the errors in a given tab.

Related issues

cms-1266

Copy link

linear bot commented Feb 21, 2024

@brianjhanson
Copy link
Contributor

@gcamacho079 another one that impacts the front-end.

CleanShot 2024-02-21 at 11 30 03

@i-just i-just requested a review from brandonkelly February 22, 2024 16:47
@i-just i-just marked this pull request as ready for review February 22, 2024 16:50
@gcamacho079
Copy link
Contributor

gcamacho079 commented Feb 22, 2024

@i-just @brianjhanson I tested this on JAWS/Chrome and NVDA/Firefox, and based on how these read the content (i.e. JAWS doesn’t read automatically, while NVDA does) I think there could be the potential that the visually-hidden text is missed unless we move it to the end of the heading. For example: "Found 3 errors in this tab; 5 errors in 2 tabs" where the italicized text would be visually-hidden.

I was also able to trigger the "Found 0 errors" message again by correcting an error in the current tab, while leaving one in another tab (screenshot attached). Also, it still shows an error icon for the current tab.

An error message says 'Found 0 errors' for the current tab, but the tab button shows an error icon and there's an error in another tab.

Based on those two things, I’m still wondering if we should just make the full message visible for everyone, as it makes it crystal clear from that single error box that the other tabs are the issue.

@i-just i-just marked this pull request as draft February 23, 2024 10:02
@i-just
Copy link
Contributor Author

i-just commented Feb 23, 2024

Thanks @gcamacho079!

I changed the heading to: <h2>Found 1 error in this tab.<span class="visually-hidden">3 errors found in 3 tabs.</span></h2>.
I don’t have a strong preference on whether that second part should be visible to all or just hidden, so if you think it should all be visible, please LMK and I can easily change it.

This morning, I was able to reliably replicate that “0 errors” message (It was happening when you fix an error and then save immediately before autosave kicks in). Long story short, I have made a change to ensure we have the draft before attempting to do a full save, and that fixes this issue (and some other quirks).

If you have a sec, give it a quick test and LMK if you think any further changes are needed.

@i-just i-just requested a review from gcamacho079 February 23, 2024 16:07
@i-just i-just marked this pull request as ready for review February 23, 2024 16:07
@i-just i-just marked this pull request as draft February 23, 2024 16:37
@i-just i-just marked this pull request as ready for review February 23, 2024 18:21
# Conflicts:
#	src/web/assets/cp/dist/cp.js
#	src/web/assets/cp/dist/cp.js.map
@brandonkelly brandonkelly merged commit a18a4cb into 5.0 Feb 26, 2024
5 checks passed
@brandonkelly brandonkelly deleted the feature/cms-1266-error-summary-in-slideouts branch February 26, 2024 06:45
@brandonkelly
Copy link
Member

Works and looks great!!

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.

4 participants