## Description
### Type of Change
_Erase all that don't apply._
- Bug fix (non-breaking change which fixes an issue)
### Why
We are seeing crashes on quit when the blur command is called roughly around the same time that the React instance is being shut down. It's likely because the result of tryGetXamlRoot is null.
### What
This change falls back on the GetFocusedElement() overload without any parameters if the XamlRoot is null, as supplying a null parameter will result in a NPE.
## Testing
It's a tricky race condition to repro, but I did validate that passing a null XamlRoot value to `FocusManager::GetFocusedElement(XamlRoot)` will throw an exception.
## Changelog
Should this change be included in the release notes: _yes_
Fix for NPE when blur command is received while React instance is shutting down.
* Render background color on Text
Applies a fill rect to the composition visual
Fixes#11763
* Change files
* Protect color conversions from empty values
* Apply scale factor to fill rect
* Remove unneded ViewProps alias
* Render background color on Text
Applies a fill rect to the composition visual
Fixes#11763
* Change files
* Protect color conversions from empty values
* Apply scale factor to fill rect
* Remove unneded ViewProps alias
* Use isColorMeaningful
* Add VisitAllPages Test
* Fix: Hold Tests Until Metro Loads Bundle
* Fix: Disable API Tests
* Migrate to Release
* Alter Path
* Adjust Commands
* Test Single Case
* Fire Warning if WebDriverIO loses focus
* Adjuist
* Add API
* Fix File
* Add Additional Workaround
* Add Backspace
* Remove Border Example
* Remove Unneeded Workaround
* Remove Faulty Test
* Disable API
* Fix Lint
## Description
While trying to integrate the latest RN code (see PR #11970) the `RNTesterIntegrationTests` in `React.Windows.Desktop.IntegrationTests` kept hanging and timing out.
The root issue (TBD) was a `JSError` being thrown by Chakra when the test bundle (ex. `DummyTest`) was loaded from Metro. However the bundle was loaded asynchronously, which caused that error to be swallowed and never reported. Furthermore, not knowing that the bundle load had failed, the test continued onward and attempted to start loading the app with `AppRegistry.runApplication()` (which also failed silently) and finally proceeded to wait indefinitely for the JS component to render and fire the `TestModule.markTestPassed(true)`.
To address this, this PR changes the tests to set a reasonable 30s timeout for waiting for the app to "render" (it usually completes in 2-3s).
### Type of Change
- Bug fix (non-breaking change which fixes an issue)
### Why
To better detect failures in `RNTesterIntegrationTests`.
### What
Changes the tests to set a reasonable 30s timeout for waiting for the app to "render" (it usually completes in 2-3s).
## Screenshots
N/A
## Testing
Re-ran the tests and verified if the bundle load fails the test fails.
## Changelog
Should this change be included in the release notes: No
## Description
There are three tests in `Desktop.Integration`'s `HttpResourceIntegrationTests` which verify that requests against a server that requires a `User-Agent` will succeed with the header present and fail when it's missing.
To do this we're using a standard unauthenticated GitHub API endpoint.
However, we can also hit rate limiting on this endpoint, causing the tests to fail. This PR improves the stability of those tests by instead hitting an API with the same Header requirement, but without rate limiting.
### Type of Change
- Bug fix (non-breaking change which fixes an issue)
### Why
Stop good PRs from failing due to rate limiting causing tests to fail sporadically.
### What
Instead of hitting random GitHub API endpoints (and getting caught in unauthenticated rate limiting), instead change to calling the `/rate_limit` API, which has no rate limit itself.
## Screenshots
N/A
## Testing
Ran integration tests.
## Changelog
Should this change be included in the release notes: No
Fabric Text components use their text value as the accessibility name by default
* Components can provide a default accessible name
* Text component falls back to the content if accessibleLabel isn't set
* Update accessibilityRole logic to match style
* Enable App Launch and Close in Testing
* Save State
* Save State
* Save State
* Add Package Provider
* Save State
* Save State: Working AutomationClient
* Code Cleanup
* Format
* Format
* Fix Build
* Update CI
* Fix Path
* Enable App Launch and Close in Testing
* Save State
* Save State
* Save State
* Add Package Provider
* Save State
* Save State: Working AutomationClient
* Code Cleanup
* Format
* Format
* Fix Build
* Update CI
* Fix Path
## Description
This PR specifies that all projects should set the msbuild property `RestorePackagesWithLockFile` to `true` by default, not just the C# ones.
This way we can ensure that PR/CI will build reliably because every locked version should be available in the react-native-public ADO feed. Changes to NuGet dependencies in PRs should now explicilty fail if the new package version is not in the ADO feed, and therefore require us to manually approve the addition to the feed (as required by compliance).
Closes#11998
### Type of Change
- Bug fix (non-breaking change which fixes an issue)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
### Why
This way we can ensure that PR/CI will build reliably because every locked version should be available in the react-native-public ADO feed. Changes to NuGet dependencies in PRs should now explicilty fail if the new package version is not in the ADO feed, and therefore require us to manually approve the addition to the feed (as required by compliance).
Closes#11998
### What
This PR specifies that all projects should set the msbuild property `RestorePackagesWithLockFile` to `true` by default, not just the C# ones.
## Screenshots
N/A
## Testing
N/A
## Changelog
Should this change be included in the release notes: no
React-Native-Windows Bot
Andrew Coates
dependabot[bot]
Eric Rozell
Tatiana Kapos
Yajur Grover
Chris Glein
Chiara Mooney
Jon Thysell
Krystal Kramer
Zihan Chen (MSFT)