You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The header and typeIcon grid areas were still defined, seemingly without reason, which caused the issue with title wrapping. We’ve added a temporary override to remove these areas from the grid until CSS fixes this on its side.
We’re also addressing the error attribute, which should have already been in deprecated status (when we remove it, the typeIcon grid area becomes unnecessary). The alternative is to move towards using Alert Dialog with variant="error" for error cases.
If my change required a change to the documentation, I have updated the documentation in this pull request.
I have read the CONTRIBUTING document.
I have added tests to cover my changes.
All new and existing tests passed.
I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against main.
rubencarvalho
changed the title
fix(dialog): update grid-template-areas to use heading instead of uns…
fix(dialog): update grid to span heading area
Oct 10, 2024
rubencarvalho
changed the title
fix(dialog): update grid to span heading area
fix(dialog): update grid to fully span heading area
Oct 10, 2024
rubencarvalho
changed the title
fix(dialog): update grid to fully span heading area
fix(dialog-wrapper): update grid to fully span heading area
Oct 10, 2024
Lighthouse scores comparing the documentation site built from the PR ("Branch") to that of the production documentation site ("Latest") and the build currently on main ("Main"). Higher scores are better, but note that the SEO scores on Netlify URLs are artifically constrained to 0.92.
Transfer Size
Category
Latest
Main
Branch
Total
228.267 kB
217.259 kB
217.209 kB 🏆
Scripts
57.684 kB
52.602 kB
52.502 kB 🏆
Stylesheet
34.514 kB
30.175 kB 🏆
30.278 kB
Document
6.223 kB
5.465 kB
5.456 kB 🏆
Font
126.952 kB
126.642 kB
126.623 kB 🏆
Request Count
Category
Latest
Main
Branch
Total
52
52
52
Scripts
41
41
41
Stylesheet
5
5
5
Document
1
1
1
Font
2
2
2
rubencarvalho
changed the title
fix(dialog-wrapper): update grid to fully span heading area
fix(dialog-wrapper): update heading to fully span grid area
Oct 10, 2024
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
header
andtypeIcon
grid areas were still defined, seemingly without reason, which caused the issue with title wrapping. We’ve added a temporary override to remove these areas from the grid until CSS fixes this on its side.We’re also addressing the
error
attribute, which should have already been in deprecated status (when we remove it, thetypeIcon
grid area becomes unnecessary). The alternative is to move towards usingAlert Dialog
withvariant="error"
for error cases.Related issue(s)
Motivation and context
This was causing a long dialog title being wrongly formatted, as the original issue above describes.
How has this been tested?
I've added a new story to cover this case.
Screenshots
Before:
After:
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.