Agne Lukoseviciute
Agne Lukoseviciute
## Description This PR adds UIA events when accessibilityValue has changed which will ensure that accessibility clients like Narrator can announce these types of changes to the user. In addition,...
Building on top of https://github.com/microsoft/react-native-windows/issues/9599, this issue tracks the set of sub-issues that are required before RNW support for WinAppSDK is said to be in _Experimental_. Overall, the goal here...
## Description backport: https://github.com/microsoft/react-native-windows/pull/10192 ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Internal Request ## Testing Added example from original PR, and confirmed...
## Description backport: https://github.com/microsoft/react-native-windows/pull/10192 ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Internal Request ## Testing Added example from original PR, and confirmed...
When navigating to a new page using react-navigation, the components of a previously opened page remain in the tabindex. I think this is also related to some tabbing issues we're...
Changing the value of accessibilityValue is not triggering Narrator to read out the new state. Similar to: https://github.com/microsoft/react-native-windows/issues/8491, needs calls to peer.RaisePropertyChangedEvent when value changes.
### Suggestion The page currently[*](https://github.com/microsoft/react-native-windows-samples/pull/611) titled "API Parity" is the only page that really discusses the components/APIs we support & how we're working to stay up to date with RN...
### Problem Description from: https://github.com/microsoft/react-native-windows/issues/8781 Disabled TouchableHighlight still receives keyboard focus if onPress is defined. ### Steps To Reproduce 1. Set `disabled={true}` and define an onPress handler for a TouchableHighlight...
## Summary of the pull request With this PR, if you win+R: `ms-devhome:add-apps-to-cart?URIs="x-ms-winget://winget/Git.Git","x-ms-winget://winget/Microsoft.VisualStudioCode", "x-ms-winget://winget/Microsoft.PowerToys"` You will be taken to this view of Dev Home: ![image](https://github.com/microsoft/devhome/assets/41223743/ee683634-d0f5-4cf7-90e9-e30bf1b5da70) This also adds a message...
As @manodasanW figured out, the use of version-specific RIDs and the associated workaround will no longer be needed once there's a new version of the Dev Home SDK and the...