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

Fixed corner radius on the query button on the AutoSuggestBox control #2198

Merged
merged 8 commits into from
Apr 28, 2020
Merged

Fixed corner radius on the query button on the AutoSuggestBox control #2198

merged 8 commits into from
Apr 28, 2020

Conversation

yaira2
Copy link
Contributor

@yaira2 yaira2 commented Mar 31, 2020

Description

I fixed the query button on the AutoSuggestBox having sharp corners. See the before and after photo.

Motivation and Context

I wanted to fix an inconsistency with the design of the AutoSuggestBox control.

How Has This Been Tested?

I tested this with the MUXControlsTestApp.

Screenshots (if appropriate):

Before

image

After

image

Additional context

Sorry for the typo in the commit.

@msft-github-bot msft-github-bot added the needs-triage Issue needs to be triaged by the area owners label Mar 31, 2020
@yaira2 yaira2 changed the title Fixed corner radius for querry button on auto suggest box Fixed corner radius on the query button on AutoSuggestBox Mar 31, 2020
@yaira2 yaira2 changed the title Fixed corner radius on the query button on AutoSuggestBox Fixed corner radius on the query button on the AutoSuggestBox control Mar 31, 2020
Copy link
Contributor

@StephenLPeters StephenLPeters left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@StephenLPeters StephenLPeters added area-AutoSuggestBox area-Styling team-Controls Issue for the Controls team and removed needs-triage Issue needs to be triaged by the area owners labels Mar 31, 2020
@ranjeshj
Copy link
Contributor

ranjeshj commented Apr 1, 2020

@chigy as FYI

@ranjeshj
Copy link
Contributor

ranjeshj commented Apr 1, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ranjeshj
Copy link
Contributor

ranjeshj commented Apr 3, 2020

@yaichenbaum can you please merge with master which includes some stability fixes for the PR pipeline ?

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 3, 2020

@ranjeshj Done.

@ranjeshj
Copy link
Contributor

ranjeshj commented Apr 3, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Apr 3, 2020

Looks like there were some test failures in this run:

ApiTests.NavigationViewTests.VerifyVisualTree
ApiTests.AutoSuggestBoxTests.VerifyVisualTree

@StephenLPeters
Copy link
Contributor

@yaichenbaum Will you be able to address the visual verification test failures here?

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 3, 2020

@StephenLPeters I am not sure how I would do that, can I let a little direction on that?

@marcelwgn
Copy link
Collaborator

@yaichenbaum You can find instructions on how to update the Visual Tree Verification files here:
https://github.com/microsoft/microsoft-ui-xaml/blob/master/docs/developer_guide.md#visual-tree-verification-tests

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 3, 2020

@chingucoding Thank you for the link, I will try to get to it over the next few days.

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 7, 2020

@StephenLPeters I added the new files, can you run the tests again?

@kmahone
Copy link
Member

kmahone commented Apr 7, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@StephenLPeters
Copy link
Contributor

@yaichenbaum there are two more visual tree verification masters that need updating AppBarButton-5.xml and AppBarToggleButton-5.xml. @ranjeshj or @kmahone I don't think I would expect this change to be affecting AppBarButton visuals... thoughts?

@@ -26,7 +26,7 @@
FocusVisualPrimaryThickness=2,2,2,2
FocusVisualPrimaryBrush=#FF000000
Visibility=Visible
RenderSize=68,56
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

68,56 [](start = 17, length = 5)

Its possible this file just needs to be reverted. I don't think your change would have caused appBarTOggleButton to be changed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am happy to revert the file, just let me know if that is what I should do.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please revert this, then i'll rerun

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reverted the changes to this file, should I do that for any other files as well?

@StephenLPeters
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ranjeshj
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 22, 2020

Why is the test still failing?

@ranjeshj
Copy link
Contributor

@yaichenbaum Can you please merge in master and I can kick off a new run ? There have been a handful of changes with NavigationView in the past couple of weeks. Thanks!

@yaira2
Copy link
Contributor Author

yaira2 commented Apr 22, 2020

@ranjeshj Sure.

@ranjeshj
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Apr 24, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Apr 24, 2020

The test failures on RS4 and RS3 were the result of xml master comparison. NavigationViewTopPaneContent-5.xml and NavigationViewTopPaneContent-6.xml needed to be updated to account for CornerRadius. I've pushed fixes and re-run the build.

@StephenLPeters StephenLPeters merged commit 55e15de into microsoft:master Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants