-
Notifications
You must be signed in to change notification settings - Fork 20
fix(docs): fix dialog markup on dialog text content and button intendation #6206
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: e98213c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Related Previews |
…es with `flexdirection: column` on dialog styles
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.
…es in Dialog stories
|
return html`<button class="btn btn-primary">OK</button><br /> | ||
<button class="btn btn-secondary">Cancel</button>`; |
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.
The code should remain the same, we do not want to change the dialog component.
The ticket is about code formatting, for a good indentation the button tags must be on two different lines:
return html`<button class="btn btn-primary">OK</button><br /> | |
<button class="btn btn-secondary">Cancel</button>`; | |
return html` | |
<button class="btn btn-primary">OK</button> | |
<button class="btn btn-secondary">Cancel</button> | |
`; |
📄 Description
<p>
-tag around dialog content in stories, required for accessibility.<button>
-tags to be on two different lines.