Skip to content

Conversation

@NickGerleman
Copy link
Contributor

@NickGerleman NickGerleman commented Apr 28, 2021

Fixes #7130

Should lead to test stability when the window is resized.

Microsoft Reviewers: Open in CodeFlow

Fixes microsoft#7130

Should lead to test stability when the window is resized.
@NickGerleman NickGerleman requested a review from a team as a code owner April 28, 2021 13:41
x:Name="myRootView"
ComponentName="ReactUWPTestApp"
Background="{ThemeResource ApplicationPageBackgroundThemeBrush}"
Width="800"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure if this is the default width, but CI should tell me 🤷‍♀️

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Snapshots match, so I think this was right.

Copy link
Contributor

Choose a reason for hiding this comment

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

1074 is what we've needed so far, e.g. the display:none PR

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 looked through some snapshots and noticed that width, but also a lot of 800 width outer views.

IIRC my guess was that some views may overflow or be horizontally scrollable?

I previously verified changing root view height affect tree dumps, so my assumption would be that width should have a similar effect. I didn't validate that a template uwp app has an 800x600 window size, but that number would make sense, and seems to lead to consistent snapshots.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Confirmed 800x600 in code

ApplicationView.GetForCurrentView().TryResizeView(new Size(800, 600));

Copy link
Contributor Author

@NickGerleman NickGerleman Apr 29, 2021

Choose a reason for hiding this comment

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

Though that does make me wonder if she issue Agne was seeing in #7589 is the same as the issue this solves. It looks like we already resize every app launch. Might be good to confirm.

@NickGerleman NickGerleman added the AutoMerge Causes a PR to be automatically merged once all requirements are passed (label drives bot activity) label Apr 28, 2021
@ghost
Copy link

ghost commented Apr 28, 2021

Hello @NickGerleman!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 10 hours, a condition that will be fulfilled in about 8 hours 20 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Test Infrastructure AutoMerge Causes a PR to be automatically merged once all requirements are passed (label drives bot activity)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set fixed e2e root view width

4 participants