-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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: Add invalid tag name warning #11324
Conversation
Narrator doesn't read the text but I'm not sure how to solve it |
There is a setting to read it but I think it's okay as long as the text property is it. |
@heftymouse the tag settings were moved to a separate page |
Sure, I can do that
…On Fri, Feb 17, 2023, 11:03 PM Yair ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In src/Files.App/Views/SettingsPages/Tags.xaml
<#11324 (comment)>
:
> @@ -106,6 +106,40 @@
HorizontalAlignment="Right"
Orientation="Horizontal"
Spacing="12">
+ <!-- Invalid Name Warning -->
+ <Grid
I'll find the resource for it, can you switch to it?
—
Reply to this email directly, view it on GitHub
<#11324 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOJEU7RLPJGBR4A7MF5LLLDWX6Y77ANCNFSM6AAAAAAU6DDIMY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
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.
Can you solve the UX issue?
Good idea, I'll do that |
Which resource was it? |
I had to retemplate the control to centre align its content |
I was hoping we could do it with a single resource, if we have to restyle the whole control, it makes me wonder if the original implementation with a grid was cleaner. What are your thoughts on this? |
I agree |
Can you fix the merge conflicts? |
Can you share a screenshot? |
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.
LGTM
@heftymouse can you fix the merge conflict? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
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.
LGTM
Resolved / Related Issues
Items resolved / related issues by this PR.
Validation
How did you test these changes?
Screenshots (optional)
Add screenshots here.