Skip to content

Switch WinUI to the Windows 11 styles - #12241

Merged
4 commits merged into
mainfrom
dev/pabhoj/xaml_version_2
Jan 27, 2022
Merged

4 commits merged into
mainfrom
dev/pabhoj/xaml_version_2

Conversation

@PankajBhojwani

@PankajBhojwani PankajBhojwani commented Jan 24, 2022 •

Copy link
Copy Markdown
Contributor

No description provided.

@zadjii-msft

Mike Griese (zadjii-msft) commented Jan 24, 2022 •

Copy link
Copy Markdown
Member
  • How are we lanning on dealing with the numerous TabView quirks in v2? Just ship it as-is and fix in post? Or manually adjust the styling now?
    • EX the close button hover is weirdly wide
    • the tab text is bold
  • Icons throughout the app are still on the Segoe MDL2, not Segoe Fluent
  • Tab color picker looks fine
  • Tab renamer looks fine (if maybe needs a little padding...)
  • Window Renamer / ID toast looks fine
  • About looks... Fine? The links aren't underlined anymore, but that might just be how WinUI works these days
  • InfoBars look totally insane transparent
    image

@zadjii-msft Mike Griese (zadjii-msft) added the Needs-Discussion Something that requires a team discussion before we can proceed label Jan 24, 2022
@DHowett

Copy link
Copy Markdown
Member

How does it look overall? Should we merge and test in post?

@PankajBhojwani

Copy link
Copy Markdown
Contributor Author

Should we merge and test in post?

I like this idea, the visual issues we've found so far have been fixed getting it in will help us find more (if any) faster

@DHowett Dustin L. Howett (DHowett) changed the title Change our xaml controls resources version to version 2 Switch WinUI to the Windows 11 styles Jan 26, 2022
@DHowett

Copy link
Copy Markdown
Member

image

renamed the PR!

@DHowett

Copy link
Copy Markdown
Member
  • How are we lanning on dealing with the numerous TabView quirks in v2? Just ship it as-is and fix in post? Or manually adjust the styling now?

    • EX the close button hover is weirdly wide
    • the tab text is bold

Ship, file, fix. :)

@DHowett Dustin L. Howett (DHowett) added the AutoMerge Marked for automatic merge by the bot when requirements are met label Jan 26, 2022
@ghost

Copy link
Copy Markdown

Hello Dustin L. Howett (@DHowett)!

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.

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.

@ghost
ghost merged commit a13b207 into main Jan 27, 2022
@ghost
ghost deleted the dev/pabhoj/xaml_version_2 branch January 27, 2022 13:26
ghost pushed a commit that referenced this pull request Jan 27, 2022
Turns out, this bug only repros in Controls version 2. I'm not sure why, but it didn't repro only on main. So this fix does nothing until #11720 merges.

This PR prevents us from setting properties on the paste warning dialog unless we actually need to paste. 5f9c551 proves that settings these properties is what would cause the bug in the first place. 

I went a step further and cleaned this up a bit. This was always a little weird, having to get the `BracketedPasteEnabled` for the active control on the UI thread before we actually display the warning. In the post-#5000 future where going back to the control like this would be a x-proc hop, I figured I should just skip that entirely and plumb the `BracketedPaste` state out in the initial request. 

* [x] Closes #12202
* [x] I work here
* [x] No tests, but there's not a great place for a test like this
* [x] Doesn't affect docs

See also: #12241 which would introduce #12202 on its own.
@zadjii-msft Mike Griese (zadjii-msft) removed the Needs-Discussion Something that requires a team discussion before we can proceed label Jan 31, 2022
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge Marked for automatic merge by the bot when requirements are met

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants