-
Notifications
You must be signed in to change notification settings - Fork 324
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
Make Close buttons consistent #1329
Conversation
VerticalAlignment="Top" | ||
BorderThickness="0" | ||
Background="Transparent" | ||
Padding="10"> |
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.
We will need to add a localized AutomationProperties.Name to this control later, as the narrator will read it as "Button" and nothing else.
Can the common close button view be used in the setuptool project? That has a close button. |
@dhoehna Can you point me to where you're talking about? Searching I see there's two other places where glyph E711 are referenced, but since they're in their own control, I wasn't sure I should mess with them.
|
@dhoehna I updated SummaryView to use it. I tried it out myself and it looked good, but you may want to double check it. (The Padding is a little bigger in my control, but only by 5 pixels) |
Summary of the pull request
We use a Close button ("X" button") in a few places in Dev Home. This change creates a CloseButton control so that styling (Margin, Padding, Alignment, Text) will be consistent throughout. Also remove FontIconSource and FontIconClose from SetupToolStyles.xaml, which are not used anywhere.
References and relevant issues
#916
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist