You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 1, 2024. It is now read-only.
Hi everyone! Apologies for the late update - in case you missed it, this was fixed earlier this summer by #14089. All the awesome fixes @PureWeen made in this PR are set up behind an Accessibility_Experimental flag, which is available in XF 5.0.0.2083 and later versions.
Furthermore, be sure to check out the new SemanticEffects properties in XCT which also circumvents the AutomationID issue. These can also be applied to your XF projects, and reflect the properties that will be brought into .NET MAUI as well.
Hope this helps, and let us know if you have more questions! :)
Hi everyone! Apologies for the late update - in case you missed it, this was fixed earlier this summer by #14089. All the awesome fixes @PureWeen made in this PR are set up behind an
Accessibility_Experimental
flag, which is available in XF 5.0.0.2083 and later versions.If you aren't familiar with experimental flags, you can read more about them here: https://docs.microsoft.com/en-us/xamarin/xamarin-forms/internals/experimental-flags. But in short, after updating XF, enable the flag by adding the following to your code-behind, after the InitializeComponent and before setting the MainPage:
Furthermore, be sure to check out the new
SemanticEffects
properties in XCT which also circumvents the AutomationID issue. These can also be applied to your XF projects, and reflect the properties that will be brought into .NET MAUI as well.Hope this helps, and let us know if you have more questions! :)
Originally posted by @rachelkang in #1529 (comment)
The text was updated successfully, but these errors were encountered: