Skip to content

Main #10602

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

Open
wants to merge 357 commits into
base: marb2000-patch-1
Choose a base branch
from
Open

Main #10602

wants to merge 357 commits into from

Conversation

cwdsingular
Copy link

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

marcelwgn and others added 30 commits March 9, 2022 10:27
…nd up in faulty rendering of pane toggle button (microsoft#6780)

* Add test ui

* Fix issue with margin not updating correctly
* test code

* delay load chevron

* fix delay load chevron

* delay load NVI MenuItemsHost

* added visual verification test

* updated visual verification files

* updated chevron delay load

* delete test code

* added generated visual verification files

* addressed comments
…w. (microsoft#6797)

* Attempt to fix issue with exception being thrown during cleanup.

* Add test

* Add a comment explaining the need for the try catch block
* Update WinUI roadmap as feature overview

* Comment fixes

* More comment fixes
…allow for customizations of the glyph in both places seperately. (microsoft#6831)

Expose the chevron margin as a resource to enable cusomtization.

Apply chevron foreground color in pointer VSM.
…ransient mode (microsoft#6844)

CommandBarFlyout was changed to unconditionally give keyboard focus to the first focusable command when it opens. This breaks the assumption when opening in transient mode that the flyout won't take keyboard focus in that mode. We should only give keyboard focus when opening in standard mode.

Also added a test to make sure that this doesn't regress in the future.
* Add space on automation properties name

* Add missing L on string
* add micabasealt fallback brushes

* update brush names

* changes from comments
)

SplitButtonAutomationPeer's Invoke implementation currently just directly calls the Click event handler, which misses the fact that we also have the option of assigning a command to execute.  Instead of that, I've made it so we just forward the Invoke implementation to the primary button's automation peer, which will ensure that we do everything a button should do in this case.

I also edited the test case using the SplitButton with a command to use Invoke() to test that case as well.
…6897)

* sets close and action buttons automation property name

* Add test and address comments

* Address comments

* Add spaces
…ScrollView` (microsoft#6889)

* Ensure BringIntoView request is not skipped for direct content of ScrollView

* Test for BringIntoView for direct content

* Move test to correct location and rename
Following microsoft@664933b we ran into the issue that we now have two different visual state groups targeting the same property (SubItemChevron.Margin), which can cause problems in that one can pave over the other.  I've fixed things by duplicating the SubItemChevron so the states for buttons in the primary and secondary items can be managed separately from each other, and toggled visibility of the two based on where the button is located.

Also added an automated API test that reproduces the issue without the fix.
…indeterminate. (microsoft#6941)

ProgressRing should not report the RangeValue pattern when it's indeterminate, as in that case it has no value to report.
Left nav currently has faulty logic to calculate the position in set and size of set, relating to the way in which we count what element we're iterating on. The top nav scenario has the correct logic, and there isn't anything remaining that differentiates the left and top nav here anymore, so I've consolidated both to the same logic. I've added a test scenario to ensure that those are now calculated correctly, as well.
…crosoft#6835)

* update test page with cursor positioned menu flyout

* changes from comments
"Value" wasn't used as the UIA name associated with HSV since the concern was that "value" could be considered confusing by low-vision accessible users since without the broader context, it wasn't clear it meant the V in HSV rather than just any old value, so we used the equivalent "Brightness" instead. However, UIA names need to contain the full string of any attached label, so I've updated things to read "Value (Brightness)" instead. Also, in cases where there's the context of hue and saturation being present as well, I updated things to just read "Value", for consistency.
…ft#6964)

* Fixes narrator now reading which item was grabbed on drag

* Add comment
* Fixes Bug 36685596: [WinUI3] [Notepad] Users is unable to navigate to 'Zoom' sub-menu using 'Right' arrow key.

* Fixes Bug 36629906: [WinUI2] [Notepad]Focus is not visible on 'View' menu-item, upon activating 'Status bar' & 'Word wrap' present in 'View' menu item.

* Fixes Bug 38190286: [WinUI2] [Notepad>Home]: Keyboard focus is not moving in cycle among the 'File', 'Edit' & 'View' menu-items, while navigating via 'Left/Right' arrow keys.

* Add comment

* Add tests

* update handled of key press
reunion-maestro-bot and others added 28 commits September 5, 2024 02:19
* titlebar spec initial

* Update specs/TitleBar/titlebar-functional-spec.md

Co-authored-by: whiskhub <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titleBar-dev-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titlebar-functional-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titlebar-functional-spec.md

Co-authored-by: Jay <[email protected]>

* Update specs/TitleBar/titlebar-functional-spec.md

Co-authored-by: Jay <[email protected]>

* formatting changes from comments

* update images

* add height explanation

* address more comments

* add notes on header footer naming

* contentBefore and contentAfter

---------

Co-authored-by: whiskhub <[email protected]>
Co-authored-by: Jay <[email protected]>
* Updating icons

* Remove source code links
Co-authored-by: Mike Crider <[email protected]>
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Jun 4, 2025
Copy link
Contributor

@cwdsingular please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue needs to be triaged by the area owners
Projects
None yet
Development

Successfully merging this pull request may close these issues.